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

Halt TabletServer on minc failure and no TabletServer lock #5169

Open
wants to merge 1 commit into
base: 2.1
Choose a base branch
from

Conversation

dlmarion
Copy link
Contributor

Related to #5137

@dlmarion dlmarion added this to the 2.1.4 milestone Dec 12, 2024
@dlmarion dlmarion self-assigned this Dec 12, 2024
} else {
throw e;
}
}

// log.debug(String.format("MinC %,d recs in | %,d recs out | %,d recs/sec | %6.3f secs |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Curious why these log messages are commented out.

try {
ret = super.call();
} catch (Exception e) {
if (tabletServer.getLock() == null || !tabletServer.getLock().verifyLockAtSource()) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a small race condition here with calling getLock() twice? I'm not sure if it's possible for the state to really change in this case between reads but I was wondering if it's better to do something like

var lock = tabletServer.getLock();
if (lock == null || !lock.verifyLockAtSource()) {

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.

Make tablet servers respond more aggressively to failed minor compaction.
2 participants