Repository navigation
Fix fate tx details - #6586
Merged
Merged
Fix fate tx details#6586
Conversation
dlmarion
approved these changes
Oct 15, 2026
Amemeda
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #6566
This fixes a bug/race where while the monitor was reading a FATE transaction's info, the transaction could finish and be deleted. This caused issues in the corresponding monitor page where the transaction was listed but with no Operation and with an age of 56 years.
This PR changes things to now skip transactions whos status comes back
UNKNOWNwhich is what is returned for the status when a transaction is gone. I also saw a case where the status wasSUCCESSFUL, it had a properopbut the time was the 56 years value. I think this happens when the transaction goes away after part of the info is read so I added this case to the skip check.Used a helper script that polls the
/rest-v2/fateendpoint every couple seconds and looks for anyUNKNOWNstatus or created time of 0. Before these changes I was seeing about 5 per minute while running the new test from apache/accumulo-testing#322. After these changes I do not see any of those.