-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shifting bootstrap function inside retry logic for the connector #30
Shifting bootstrap function inside retry logic for the connector #30
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we bootstrapping when there is a failure in case of getchanges? Do we need that?
@@ -321,6 +318,12 @@ private void getChanges2(ChangeEventSourceContext context, | |||
short retryCount = 0; | |||
while (retryCount <= connectorConfig.maxConnectorRetries()) { | |||
try { | |||
// Iterate over all the tablets to bootstrap them |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we bootstrapping in case of failure in getchanges?
@@ -318,6 +315,34 @@ private void getChanges2(ChangeEventSourceContext context, | |||
final Metronome pollIntervalMetronome = Metronome.parker(Duration.ofMillis(connectorConfig.cdcPollIntervalms()), Clock.SYSTEM); | |||
final Metronome retryMetronome = Metronome.parker(Duration.ofMillis(connectorConfig.connectorRetryDelayMs()), Clock.SYSTEM); | |||
|
|||
short retryCountForBootstrapping = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a different function
This PR aims to make the following amendment: