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

Fixing set command related failures #2

Merged
merged 1 commit into from
Jan 6, 2016
Merged

Fixing set command related failures #2

merged 1 commit into from
Jan 6, 2016

Conversation

vibhaska
Copy link

@vibhaska vibhaska commented Jan 5, 2016

No description provided.

vibhaska pushed a commit that referenced this pull request Jan 6, 2016
Fixing set command related failures
@vibhaska vibhaska merged commit 580e806 into snappy/master Jan 6, 2016
@vibhaska vibhaska deleted the SNAP-344 branch January 6, 2016 09:27
@vibhaska vibhaska mentioned this pull request Oct 16, 2017
@ahshahid ahshahid mentioned this pull request Oct 11, 2018
sumwale pushed a commit that referenced this pull request Aug 7, 2021
Deploy in production with 10k tables for months, revealed a lot of orphan lock grantors
when 'DROP TABLE'; and 100% Thread CPU usage on OldEntriesCleanerThread.
This pull request fixed these:

    [Lock] Prevent unnecessary creating distributedLock when destroying a bucket region with
    zero redundancy

    [TX] OldEtriesCleanThread may run very slow due to getHostedTransactionsInProgress()
         for each OldEntry. Replaced as Batch Compare for great performance enhancement.

    [sumedh] fixed the running TX list to maintain a version and refresh if changed
    in the above change else it can keep referring to an outdated list during its run
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