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

wal should unlock hanged locks #21

Merged
merged 1 commit into from
May 20, 2019
Merged

wal should unlock hanged locks #21

merged 1 commit into from
May 20, 2019

Conversation

kptfh
Copy link
Collaborator

@kptfh kptfh commented May 20, 2019

No description provided.

@kptfh kptfh merged commit fb0a86a into develop May 20, 2019
deleteWalTransaction(transactionId);
}

void releaseLocks(Set<Key> keysLocked) throws BackendException {
Copy link

Choose a reason for hiding this comment

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

you can inline the method

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it's overridden in test implementation: FlakingAerospikeStoreManager

logger.info("Failed to complete transaction id={}",
transaction.transactionId, be);
catch (PermanentLockingException be) {
logger.info("Failed to complete transaction id={} as it's already completed", transaction.transactionId, be);
Copy link

Choose a reason for hiding this comment

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

if this is ok case why do we need to log that on info level? debug should be enough then

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes. It's expected but quite rare corner case. So want to log it with info level to know the frequency of this cases.

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