-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
kvserver: log when acquiring lease as a draining node #79296
kvserver: log when acquiring lease as a draining node #79296
Conversation
61fd234
to
690295e
Compare
), | ||
) | ||
} | ||
log.VEventf( |
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.
This won't usually end up in the logs. Do we want to promote it to log.Info
so that it will?
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.
Done.
Generally, draining nodes are not allowed to acquire leases. Additionally, replicas that are not Raft leaders are not allowed to acquire leases. This means that draining nodes have to be permitted to acquire leases for replicas that they are the Raft leaders for. This commit adds a verbose log event when a draining store acquires a lease because it is the Raft leader. Release note: none
690295e
to
5ffaa9e
Compare
TFTR bors r+ |
Build succeeded: |
blathers backport 21.2 22.1 |
Generally, draining nodes are not allowed to acquire leases. Additionally,
replicas that are not Raft leaders are not allowed to acquire leases. This
means that draining nodes have to be permitted to acquire leases for replicas
that they are the Raft leaders for (otherwise, we risk a deadlock since no
replicas will be allowed to acquire the lease).
This commit adds a verbose log event when a draining store acquires a lease
because it is the Raft leader.
Release note: none
Jira issue: CRDB-14751