Skip to content
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

Handling node disconnections and shard movement #23

Merged
merged 2 commits into from
Jun 24, 2021

Conversation

tbhanu-amzn
Copy link
Contributor

Description

Handling node disconnections and shard movement

Issues Resolved

Handling node disconnections and shard movement

  1. NodeNotConnected exception has to be retried infinitely with a new discovery node.
  2. Shard failures shall use the standard retry mechanism of backoff and max retries.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

naveenpajjuri
naveenpajjuri previously approved these changes Jun 23, 2021
Copy link
Contributor

@naveenpajjuri naveenpajjuri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

val node = primaryShardNode()

// TODO: Acquire retention lease prior to initiating remote recovery
retentionLeaseHelper.addRetentionLease(remoteShardId, seqNo, followerShardId)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was an incorrect merge from last automerge

@tbhanu-amzn tbhanu-amzn merged commit 8843df6 into main Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants