-
Notifications
You must be signed in to change notification settings - Fork 749
[GOBBLIN-2171] Streamline log messages for easier debugging of GaaS multi-active DAG processing #4074
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
Merged
Conversation
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
…AttemptStatus::getConsensusDagAction`
Contributor
|
Can you please add the log snippet for a test flow execution before & after the change in testing section |
Contributor
Author
here are some excerpts: and and |
khandelwal-prateek
approved these changes
Nov 13, 2024
7 tasks
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.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
Description
Some logs from GaaS flow/DAG processing, e.g. by the
MysqlMultiActiveLeaseArbiter, theFlowLaunchHandler, theDagProcessingEngine, etc., are challenging to skim, especially when only the first characters on the line are shown (as the remaining content of long lines flows beyond view).Improve consistency, brevity, and the placement of the most-vital info. Also contextualize when it's not otherwise clear where in the processing a message originates (e.g. which
MultiActiveLeaseArbiterinstance).Tests
existing tests still pass
Commits