Repository navigation
Backport write ahead log recovery performance improvements to 2.1 #4887
Description
Write ahead log recovery is slow for some situation as outlined in #4873. The changes in #4873 and #4874 should be back-ported to 2.1 to speed up log recovery. To make these changes in 2.1 it would be good run continuous ingest from accumulo-testing with agitation on a small cluster. This would help verify log recovery is working properly.
Activity
amcdonaldccri commentedon May 22, 2026
I've got a fork/branch that passes the unit tests. 4 integration tests don't pass but then I read the accumulo developer contribution page. So If it ok with you I'll submit a PR?
ddanielr commentedon May 22, 2026
@amcdonaldccri sure! If you know what IT's aren't passing can you just list them in the PR?
That will help us troubleshoot without waiting for a full IT build.
amcdonaldccri commentedon May 26, 2026
Excellent, I made the PR yesterday and had thought that the commit messages weren't so good. I reworked the message.
amcdonaldccri commentedon May 31, 2026
@ddanielr any idea on how I can attach the PR to the issue? I tried adding closes [#issue] in the description but I'm guessing GitHub doesn't read altered descriptions.
ddanielr commentedon Jun 1, 2026
@amcdonaldccri I've linked your PR to this issue.
The closes keyword logic only works for the default branch (in this case
main). Otherwise we have to link the PR manually.Using
closesis still recommended as the issue will then have a "mentioned" action in its history.