[
https://issues.apache.org/jira/browse/GOBBLIN-2171?focusedWorklogId=942901&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-942901
]
ASF GitHub Bot logged work on GOBBLIN-2171:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/24 01:36
Start Date: 09/Nov/24 01:36
Worklog Time Spent: 10m
Work Description: phet opened a new pull request, #4074:
URL: https://github.com/apache/gobblin/pull/4074
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
- [ ] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-2171
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
Some logs from GaaS flow/DAG processing, e.g. by the
`MysqlMultiActiveLeaseArbiter`, the `FlowLaunchHandler`, the
`DagProcessingEngine`, 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 `MultiActiveLeaseArbiter` instance).
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
existing tests still pass
### Commits
- [ ] My commits all reference JIRA issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Issue Time Tracking
-------------------
Worklog Id: (was: 942901)
Remaining Estimate: 0h
Time Spent: 10m
> Streamline log messages for easier debugging of GaaS multi-active DAG
> processing
> --------------------------------------------------------------------------------
>
> Key: GOBBLIN-2171
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2171
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-service
> Reporter: Kip Kohn
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some logs from GaaS flow/DAG processing, e.g. by the
> `MysqlMultiActiveLeaseArbiter`, the `FlowLaunchHandler`, the
> `DagProcessingEngine`, 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 `MultiActiveLeaseArbiter` instance).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
