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

DynamoDBMasterMonitor: Don't publish MASTER_NULL on Dynamo failure #696

Conversation

crioux-stripe
Copy link
Collaborator

Context

We encountered an issue in which DynamoDBMasterMonitor would emit a MASTER_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
  • Added new tests where applicable
  • ./gradlew test passes all tests
  • Extended README or added javadocs where applicable

Copy link

github-actions bot commented Jul 29, 2024

Test Results

535 tests  ±0   529 ✅ ±0   7m 51s ⏱️ +8s
139 suites ±0     6 💤 ±0 
139 files   ±0     0 ❌ ±0 

Results for commit b3bba8c. ± Comparison against base commit a61cf1d.

♻️ This comment has been updated with latest results.

@crioux-stripe
Copy link
Collaborator Author

Just realized I have a commented out test here. Working on a fix.

@crioux-stripe
Copy link
Collaborator Author

Fixed.

@crioux-stripe crioux-stripe merged commit d265bfb into Netflix:master Jul 30, 2024
4 of 5 checks passed
@crioux-stripe crioux-stripe deleted the crioux-stripe/fix-dynamo-lock-master-monitor-null-on-failure branch July 30, 2024 17:57
@crioux-stripe crioux-stripe had a problem deploying to Integrate Pull Request August 29, 2024 16:30 — with GitHub Actions Failure
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.

2 participants