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

fix: remark region as inactive on leader changed #2446

Conversation

fengjiachun
Copy link
Collaborator

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

If the meta leader node dies during the execution of the procedure, the new leader node needs to remark the failed region as "inactive" to prevent it from renewing the lease.

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

Close #2332

@codecov
Copy link

codecov bot commented Sep 19, 2023

Codecov Report

Merging #2446 (37d18fb) into develop (0f79cca) will decrease coverage by 0.10%.
Report is 1 commits behind head on develop.
The diff coverage is 35.71%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2446      +/-   ##
===========================================
- Coverage    77.59%   77.49%   -0.10%     
===========================================
  Files          717      717              
  Lines       112419   112490      +71     
===========================================
- Hits         87234    87179      -55     
- Misses       25185    25311     +126     

@fengjiachun
Copy link
Collaborator Author

@MichaelScofield PTAL

@MichaelScofield MichaelScofield added this pull request to the merge queue Sep 20, 2023
Merged via the queue into GreptimeTeam:develop with commit ca50ba5 Sep 20, 2023
11 checks passed
paomian pushed a commit to paomian/greptimedb that referenced this pull request Oct 19, 2023
* fix: remark reigon as inactive on leader changed

* chore: by comment
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.

region failover procedure on metasrv leader changed
3 participants