The correct events are missing if the concurrent undo cycle end not come in the log #299
logesh-encipherhealth
started this conversation in
General
Replies: 2 comments 1 reply
-
The end of gc log event should flush the queues.. and if it doesn't, then this would be a bug. And it might be the case that it doesn't because missing a data point here or there isn't likely to make that much of a difference in the overall analysis but yeah, lets check that to make sure it's doing the right thing |
Beta Was this translation helpful? Give feedback.
1 reply
-
other tools parsing the above log |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The event will be published after the concurrent undo cycle come. If the concurrent undo cycle does not come, the event won't be published. So we can't get the correct parsed data what are the steps to get the correct output for that log? I will share one log for reference https://drive.google.com/file/d/1ZvmgAa0vzXzOEb6LqFDDGvP9mYIDECyF/view?usp=sharing
Beta Was this translation helpful? Give feedback.
All reactions