[jira] [Updated] (YARN-11567) Aggregate container launch debug artifacts automatically in case of error
[
https://issues.apache.org/jira/browse/YARN-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-11567:
--
Target Version/s: 3.4.0
Affects Version/s: 3.4.0
> Aggregate container launch debug artifacts automatically in case of error
> -
>
> Key: YARN-11567
> URL: https://issues.apache.org/jira/browse/YARN-11567
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 3.4.0
>Reporter: Bence Kosztolnik
>Assignee: Bence Kosztolnik
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> In cases where a container fails to launch without writing to a log file, we
> often would want to see the artifacts captured by
> {{yarn.nodemanager.log-container-debug-info.enabled}} in order to better
> understand the cause of the exit code. To enable this feature for every
> container maybe over kill, so we need a feature flag to capture these
> artifacts in case of errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11567) Aggregate container launch debug artifacts automatically in case of error
[
https://issues.apache.org/jira/browse/YARN-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Teke updated YARN-11567:
-
Fix Version/s: 3.4.0
> Aggregate container launch debug artifacts automatically in case of error
> -
>
> Key: YARN-11567
> URL: https://issues.apache.org/jira/browse/YARN-11567
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
>Reporter: Bence Kosztolnik
>Assignee: Bence Kosztolnik
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> In cases where a container fails to launch without writing to a log file, we
> often would want to see the artifacts captured by
> {{yarn.nodemanager.log-container-debug-info.enabled}} in order to better
> understand the cause of the exit code. To enable this feature for every
> container maybe over kill, so we need a feature flag to capture these
> artifacts in case of errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11567) Aggregate container launch debug artifacts automatically in case of error
[
https://issues.apache.org/jira/browse/YARN-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated YARN-11567:
--
Labels: pull-request-available (was: )
> Aggregate container launch debug artifacts automatically in case of error
> -
>
> Key: YARN-11567
> URL: https://issues.apache.org/jira/browse/YARN-11567
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
>Reporter: Bence Kosztolnik
>Assignee: Bence Kosztolnik
>Priority: Minor
> Labels: pull-request-available
>
> In cases where a container fails to launch without writing to a log file, we
> often would want to see the artifacts captured by
> {{yarn.nodemanager.log-container-debug-info.enabled}} in order to better
> understand the cause of the exit code. To enable this feature for every
> container maybe over kill, so we need a feature flag to capture these
> artifacts in case of errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
