[
https://issues.apache.org/jira/browse/GOBBLIN-1947?focusedWorklogId=891009&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-891009
]
ASF GitHub Bot logged work on GOBBLIN-1947:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/23 19:44
Start Date: 16/Nov/23 19:44
Worklog Time Spent: 10m
Work Description: hanghangliu opened a new pull request, #3832:
URL: https://github.com/apache/gobblin/pull/3832
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-1947] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1947
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
When YarnAutoScalingManager detect helix task consistently fail, give an
option to send WorkUnitChangeEvent to let GobblinHelixJobLauncher handle the
event and split the work unit during runtime. This can help resolving
consistent failing containers issue(like OOM) during runtime instead of relying
on replaner to restart the whole pipeline
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Updated test cases and tested in cluster
### 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: 891009)
Remaining Estimate: 0h
Time Spent: 10m
> Send WorkUnitChangeEvent when helix task consistently fail
> -----------------------------------------------------------
>
> Key: GOBBLIN-1947
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1947
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-cluster
> Reporter: Hanghang Liu
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When YarnAutoScalingManager detect helix task consistently fail, give an
> option to send WorkUnitChangeEvent to let GobblinHelixJobLauncher handle the
> event and split the work unit during runtime. This can help resolving
> consistent failing containers issue(like OOM) during runtime instead of
> relying on replaner to restart the whole pipeline
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
