DynamoDBMasterMonitor: Don't publish MASTER_NULL on Dynamo failure #696
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We encountered an issue in which
DynamoDBMasterMonitor
would emit aMASTER_NULL
value in the event of failing to read or decode the lock from DynamoDB. This caused some minor but unncessary churn as our agents believed the master had changed when it in fact had not. This can be further exacerbated by transient failures in Dynamo or throttling when querying Dynamo.Checklist
./gradlew build
compiles code correctly./gradlew test
passes all tests