J
JanusGraphā€¢11mo ago
Painguin

Could not start BerkeleyJE transaction

Hey I've just encounter this issue and needed to restart the entire server for it to go away. I believe it's the issue being described here https://github.com/JanusGraph/janusgraph/issues/2120
14 Replies
Painguin
PainguinOPā€¢11mo ago
I can see that a fix has already been proposal for this: https://github.com/JanusGraph/janusgraph/pull/3990 Is there a rough estimate of when this will be available for release? we've only encountered the issue once but it is quite serious. Thank you
Florian Hockmann
Florian Hockmannā€¢11mo ago
Which version of JanusGraph are you using? Because this was released as part of 1.0.0
Painguin
PainguinOPā€¢11mo ago
hmm I'm using version 1.0.0 I think the fix was merged but then later reverted though @Boxuan Li is involved in that PR so he probably has better context šŸ«”
Bo
Boā€¢11mo ago
@Florian Hockmann As @tien mentioned, I had to revert that PR due to failure of tp-tests The author, Pavel, never reopened a PR to fix the test @tien would you be interested to take this forward?
Painguin
PainguinOPā€¢11mo ago
My knowledge over this is extremely limited, so I wouldn't be so comfortable touching something this critical & low level tbh :)) But can take a look of course to see what is involved
Florian Hockmann
Florian Hockmannā€¢11mo ago
Ah, I see, I was too quick with my reply and didn't scroll down in the PR to see the revert
Bo
Boā€¢11mo ago
@tien the workaround is you apply that fix to your own fork
Painguin
PainguinOPā€¢11mo ago
For that PR how can I reopen it n have this "tp-test" thing trigger for it?
Bo
Boā€¢11mo ago
You cannot reopen it because it's already merged. You could cherry-pick that commit again (or revert the revert), and add [tp-tests] to the commit message and PR title.
Painguin
PainguinOPā€¢10mo ago
I have cherry picked the commit from that PR to a new one here https://github.com/JanusGraph/janusgraph/pull/4413 Hey so I've created a much more simplified version here instead: https://github.com/JanusGraph/janusgraph/pull/4425 I think this shouldn't mess with any of the existing tests Hopefully you guys can assist me in getting this fixed soon, got a heart attack from the second time this had happened for our DB today lol. Again my knowledge over this is very limited so would appreciate any guidance :p The approach of that PR is to simply close the environment whenever there is an interruption happen. And that each beginTransaction will try to reopen the env if it's closed. I think I've figured it out, can you guys help me check the changes? https://github.com/JanusGraph/janusgraph/pull/4425 šŸ“@Boxuan Li @Florian Hockmann
Bo
Boā€¢10mo ago
I could do rubber stamping but I would like to see if anyone else could review. I know very little about BerkeleyDB.
Painguin
PainguinOPā€¢10mo ago
@Boxuan Li There's this CI step that seem to randomly failed to upload the test artifact, can you retry that for me? https://github.com/JanusGraph/janusgraph/actions/runs/8946071491/job/24578491586?pr=4425 Sorry for the spammy changes & CI test btw šŸ˜… Okay I've got all tests to pass Anyway this fix can be available in a patch version?
Bo
Boā€¢10mo ago
Anyway this fix can be available in a patch version
Yes
Painguin
PainguinOPā€¢10mo ago
Awesome, would definitely help me sleep sounder at night with this fix haha

Did you find this page helpful?