[jira] [Created] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
Youquan Lin created YARN-10313: -- Summary: Add hadoop process id to the suffix of hadoop-unjar directory Key: YARN-10313 URL: https://issues.apache.org/jira/browse/YARN-10313 Project: Hadoop YARN Issue Type: Improvement Components: client Affects Versions: 3.1.3 Reporter: Youquan Lin We used azkaban to submit many yarn jobs, and the /tmp directory will have many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the azkaban machine takes up a lot of space, but we do not know which process generated this directory. In order to solve this problem, we add the hadoop process id to the suffix of the hadoop-unjar directory -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[ https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134306#comment-17134306 ] Youquan Lin commented on YARN-10313: my patch: [https://github.com/apache/hadoop/pull/2071] > Add hadoop process id to the suffix of hadoop-unjar directory > - > > Key: YARN-10313 > URL: https://issues.apache.org/jira/browse/YARN-10313 > Project: Hadoop YARN > Issue Type: Improvement > Components: client >Affects Versions: 3.1.3 >Reporter: Youquan Lin >Priority: Major > > We used azkaban to submit many yarn jobs, and the /tmp directory will have > many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the > azkaban machine takes up a lot of space, but we do not know which process > generated this directory. In order to solve this problem, we add the hadoop > process id to the suffix of the hadoop-unjar directory -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134313#comment-17134313
]
Youquan Lin commented on YARN-10166:
Could anyone commit this please [~wangda] , [~snemeth], [~prabhujoseph],
[~sunilg]
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[ https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Youquan Lin reassigned YARN-10313: -- Assignee: Youquan Lin > Add hadoop process id to the suffix of hadoop-unjar directory > - > > Key: YARN-10313 > URL: https://issues.apache.org/jira/browse/YARN-10313 > Project: Hadoop YARN > Issue Type: Improvement > Components: client >Affects Versions: 3.1.3 >Reporter: Youquan Lin >Assignee: Youquan Lin >Priority: Major > > We used azkaban to submit many yarn jobs, and the /tmp directory will have > many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the > azkaban machine takes up a lot of space, but we do not know which process > generated this directory. In order to solve this problem, we add the hadoop > process id to the suffix of the hadoop-unjar directory -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[ https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Youquan Lin updated YARN-10313: --- Description: We used azkaban to submit many yarn jobs, and the /tmp directory will have many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the azkaban machine takes up a lot of space, but we do not know which process generated this directory. In order to solve this problem, we add the hadoop process id to the suffix of the hadoop-unjar directory. - hadoop process id ``` 10554 org.apache.hadoop.util.RunJar ``` - hadoop-unjar directory name ``` hadoop-unjar8020753511094521686-10554 ``` was:We used azkaban to submit many yarn jobs, and the /tmp directory will have many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the azkaban machine takes up a lot of space, but we do not know which process generated this directory. In order to solve this problem, we add the hadoop process id to the suffix of the hadoop-unjar directory > Add hadoop process id to the suffix of hadoop-unjar directory > - > > Key: YARN-10313 > URL: https://issues.apache.org/jira/browse/YARN-10313 > Project: Hadoop YARN > Issue Type: Improvement > Components: client >Affects Versions: 3.1.3 >Reporter: Youquan Lin >Assignee: Youquan Lin >Priority: Major > > We used azkaban to submit many yarn jobs, and the /tmp directory will have > many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the > azkaban machine takes up a lot of space, but we do not know which process > generated this directory. In order to solve this problem, we add the hadoop > process id to the suffix of the hadoop-unjar directory. > > - hadoop process id > ``` > 10554 org.apache.hadoop.util.RunJar > ``` > - hadoop-unjar directory name > ``` > hadoop-unjar8020753511094521686-10554 > ``` -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[
https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youquan Lin updated YARN-10313:
---
Description:
We used azkaban to submit many yarn jobs, and the /tmp directory will have many
hadoop-unjar directories. Sometimes the hadoop-unjar directory on the azkaban
machine takes up a lot of space, but we do not know which process generated
this directory. In order to solve this problem, we add the hadoop process id to
the suffix of the hadoop-unjar directory.
- hadoop process id
{code:java}
10554 org.apache.hadoop.util.RunJar{code}
- hadoop-unjar directory name
{code:java}
hadoop-unjar8020753511094521686-10554
{code}
was:
We used azkaban to submit many yarn jobs, and the /tmp directory will have many
hadoop-unjar directories. Sometimes the hadoop-unjar directory on the azkaban
machine takes up a lot of space, but we do not know which process generated
this directory. In order to solve this problem, we add the hadoop process id to
the suffix of the hadoop-unjar directory.
- hadoop process id
```
10554 org.apache.hadoop.util.RunJar
```
- hadoop-unjar directory name
```
hadoop-unjar8020753511094521686-10554
```
> Add hadoop process id to the suffix of hadoop-unjar directory
> -
>
> Key: YARN-10313
> URL: https://issues.apache.org/jira/browse/YARN-10313
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: client
>Affects Versions: 3.1.3
>Reporter: Youquan Lin
>Assignee: Youquan Lin
>Priority: Major
>
> We used azkaban to submit many yarn jobs, and the /tmp directory will have
> many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the
> azkaban machine takes up a lot of space, but we do not know which process
> generated this directory. In order to solve this problem, we add the hadoop
> process id to the suffix of the hadoop-unjar directory.
>
> - hadoop process id
>
> {code:java}
> 10554 org.apache.hadoop.util.RunJar{code}
>
> - hadoop-unjar directory name
>
> {code:java}
> hadoop-unjar8020753511094521686-10554
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[
https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141945#comment-17141945
]
Youquan Lin commented on YARN-10313:
Could anyone commit this please [~wangda] , [~snemeth], [~prabhujoseph],
[~sunilg]
> Add hadoop process id to the suffix of hadoop-unjar directory
> -
>
> Key: YARN-10313
> URL: https://issues.apache.org/jira/browse/YARN-10313
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: client
>Affects Versions: 3.1.3
>Reporter: Youquan Lin
>Assignee: Youquan Lin
>Priority: Major
>
> We used azkaban to submit many yarn jobs, and the /tmp directory will have
> many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the
> azkaban machine takes up a lot of space, but we do not know which process
> generated this directory. In order to solve this problem, we add the hadoop
> process id to the suffix of the hadoop-unjar directory.
>
> - hadoop process id
>
> {code:java}
> 10554 org.apache.hadoop.util.RunJar{code}
>
> - hadoop-unjar directory name
>
> {code:java}
> hadoop-unjar8020753511094521686-10554
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142908#comment-17142908
]
Youquan Lin commented on YARN-10166:
Could you please take a look? [~sunilg]
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Assignee: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148630#comment-17148630
]
Youquan Lin commented on YARN-10166:
[~sunilg] Could you please take a look?
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Assignee: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10313) Add hadoop process id to the suffix of hadoop-unjar directory
[
https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148632#comment-17148632
]
Youquan Lin commented on YARN-10313:
[~sunilg] Could you please take a look?
> Add hadoop process id to the suffix of hadoop-unjar directory
> -
>
> Key: YARN-10313
> URL: https://issues.apache.org/jira/browse/YARN-10313
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: client
>Affects Versions: 3.1.3
>Reporter: Youquan Lin
>Assignee: Youquan Lin
>Priority: Major
>
> We used azkaban to submit many yarn jobs, and the /tmp directory will have
> many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the
> azkaban machine takes up a lot of space, but we do not know which process
> generated this directory. In order to solve this problem, we add the hadoop
> process id to the suffix of the hadoop-unjar directory.
>
> - hadoop process id
>
> {code:java}
> 10554 org.apache.hadoop.util.RunJar{code}
>
> - hadoop-unjar directory name
>
> {code:java}
> hadoop-unjar8020753511094521686-10554
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
Youquan Lin created YARN-10166:
--
Summary: Add detail log for ApplicationAttemptNotFoundException
Key: YARN-10166
URL: https://issues.apache.org/jira/browse/YARN-10166
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Affects Versions: 3.1.3
Reporter: Youquan Lin
Fix For: 3.1.3
Suppose user A killed the app, then ApplicationMasterService will call
unregisterAttempt() for this app. Sometimes, app's AM continues to call the
alloate() method and reports an error as follows.
{code:java}
Application attempt appattempt_1582520281010_15271_01 doesn't exist in
ApplicationMasterService cache.
{code}
If user B has been watching the AM log, he will be confused why the attempt
is no longer in the ApplicationMasterService cache. So I think we can detail
log for ApplicationAttemptNotFoundException as follows.
{code:java}
Application attempt appattempt_1582630210671_14658_01 doesn't exist in
ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
,diagnostics: App application_1582630210671_14658 killed by userA from 127.0.0.1
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youquan Lin updated YARN-10166:
---
Description:
Suppose user A killed the app, then ApplicationMasterService will call
unregisterAttempt() for this app. Sometimes, app's AM continues to call the
alloate() method and reports an error as follows.
{code:java}
Application attempt appattempt_1582520281010_15271_01 doesn't exist in
ApplicationMasterService cache.
{code}
If user B has been watching the AM log, he will be confused why the attempt
is no longer in the ApplicationMasterService cache. So I think we can add
detail log for ApplicationAttemptNotFoundException as follows.
{code:java}
Application attempt appattempt_1582630210671_14658_01 doesn't exist in
ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
,diagnostics: App application_1582630210671_14658 killed by userA from 127.0.0.1
{code}
was:
Suppose user A killed the app, then ApplicationMasterService will call
unregisterAttempt() for this app. Sometimes, app's AM continues to call the
alloate() method and reports an error as follows.
{code:java}
Application attempt appattempt_1582520281010_15271_01 doesn't exist in
ApplicationMasterService cache.
{code}
If user B has been watching the AM log, he will be confused why the attempt
is no longer in the ApplicationMasterService cache. So I think we can detail
log for ApplicationAttemptNotFoundException as follows.
{code:java}
Application attempt appattempt_1582630210671_14658_01 doesn't exist in
ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
,diagnostics: App application_1582630210671_14658 killed by userA from 127.0.0.1
{code}
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 3.1.3
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Fix For: 3.1.3
>
> Attachments: YARN-10166-001.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youquan Lin updated YARN-10166:
---
Attachment: YARN-10166-002.patch
Fix Version/s: (was: 3.1.3)
Target Version/s: (was: 3.1.3)
Affects Version/s: (was: 3.1.3)
I submit a new patch, and compiled successfully locally.
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047204#comment-17047204
]
Youquan Lin commented on YARN-10166:
[~hadoopqa] [~adam.antal]
One test unit errors have nothing to do with my changes. Can you tell me what
to do next?
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youquan Lin updated YARN-10166:
---
Attachment: YARN-10166-003.patch
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052677#comment-17052677
]
Youquan Lin commented on YARN-10166:
Another unit test error appeared, it didn't seem to be introduced by my code.
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youquan Lin updated YARN-10166:
---
Attachment: YARN-10166-004.patch
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054597#comment-17054597
]
Youquan Lin commented on YARN-10166:
[~adam.antal] All unit tests have passed, can you help reveiw again?
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10166) Add detail log for ApplicationAttemptNotFoundException
[
https://issues.apache.org/jira/browse/YARN-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072780#comment-17072780
]
Youquan Lin commented on YARN-10166:
[~sunilg] [~adam.antal] can you take a look at this?
> Add detail log for ApplicationAttemptNotFoundException
> --
>
> Key: YARN-10166
> URL: https://issues.apache.org/jira/browse/YARN-10166
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Youquan Lin
>Priority: Minor
> Labels: patch
> Attachments: YARN-10166-001.patch, YARN-10166-002.patch,
> YARN-10166-003.patch, YARN-10166-004.patch
>
>
> Suppose user A killed the app, then ApplicationMasterService will call
> unregisterAttempt() for this app. Sometimes, app's AM continues to call the
> alloate() method and reports an error as follows.
> {code:java}
> Application attempt appattempt_1582520281010_15271_01 doesn't exist in
> ApplicationMasterService cache.
> {code}
> If user B has been watching the AM log, he will be confused why the
> attempt is no longer in the ApplicationMasterService cache. So I think we can
> add detail log for ApplicationAttemptNotFoundException as follows.
> {code:java}
> Application attempt appattempt_1582630210671_14658_01 doesn't exist in
> ApplicationMasterService cache.App state: KILLED,finalStatus: KILLED
> ,diagnostics: App application_1582630210671_14658 killed by userA from
> 127.0.0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
