[jira] [Updated] (YARN-9429) A status code error in RssourceManager REST api doc
[
https://issues.apache.org/jira/browse/YARN-9429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-9429:
Attachment: YARN-9429.001.patch
> A status code error in RssourceManager REST api doc
> ---
>
> Key: YARN-9429
> URL: https://issues.apache.org/jira/browse/YARN-9429
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-9429.001.patch
>
>
> A status code error in ResourceManager api docs.
> In section "Cluster Application State API",the unauthorized error response
> header is described blow
> {code}
> Response Header:
> HTTP/1.1 403 Unauthorized
> Server: Jetty(6.1.26)
> {code}
> As commonly known, the unauthorized status code should be *401*.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9429) A status code error in RssourceManager REST api doc
Jinjiang Ling created YARN-9429:
---
Summary: A status code error in RssourceManager REST api doc
Key: YARN-9429
URL: https://issues.apache.org/jira/browse/YARN-9429
Project: Hadoop YARN
Issue Type: Bug
Components: documentation
Reporter: Jinjiang Ling
Assignee: Jinjiang Ling
A status code error in ResourceManager api docs.
In section "Cluster Application State API",the unauthorized error response
header is described blow
{code}
Response Header:
HTTP/1.1 403 Unauthorized
Server: Jetty(6.1.26)
{code}
As commonly known, the unauthorized status code should be *401*.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618876#comment-16618876 ] Jinjiang Ling commented on YARN-8653: - Hi [~haibochen], could you help to review this ? > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, YARN-8653.001.patch, > wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618768#comment-16618768 ] Jinjiang Ling commented on YARN-8653: - Hi [~cheersyang], could you help to review this ? > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, YARN-8653.001.patch, > wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580623#comment-16580623 ] Jinjiang Ling commented on YARN-8653: - Hi [~sunilg], could you help to review this ? > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, YARN-8653.001.patch, > wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-8653: Attachment: YARN-8653.001.patch > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-8653: Attachment: (was: YARN-8653.001.patch) > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-8653: Affects Version/s: 3.2.0 > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.2.0 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
[ https://issues.apache.org/jira/browse/YARN-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-8653: Attachment: YARN-8653.001.patch > Wrong display of resources when cluster resources are less than min resources > - > > Key: YARN-8653 > URL: https://issues.apache.org/jira/browse/YARN-8653 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Major > Attachments: YARN-8653.001.patch, wrong_resource_in_fairscheduler.JPG > > > If the cluster resources are less the min resources of Fair Scheduler, a > display error will happened like this. > > !wrong_resource_in_fairscheduler.JPG! > In this case, I config my queue with max resource to 48 vcores, 49152 MB and > min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 > vcores and 24576 MB. Then the max resource are fixed to the cluster > resources, but the min resources and steady fair share are still the config > value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-8653) Wrong display of resources when cluster resources are less than min resources
Jinjiang Ling created YARN-8653: --- Summary: Wrong display of resources when cluster resources are less than min resources Key: YARN-8653 URL: https://issues.apache.org/jira/browse/YARN-8653 Project: Hadoop YARN Issue Type: Bug Reporter: Jinjiang Ling Assignee: Jinjiang Ling Attachments: wrong_resource_in_fairscheduler.JPG If the cluster resources are less the min resources of Fair Scheduler, a display error will happened like this. !wrong_resource_in_fairscheduler.JPG! In this case, I config my queue with max resource to 48 vcores, 49152 MB and min resources to 36 vcores, 36864 MB. But the cluster resources are only 24 vcores and 24576 MB. Then the max resource are fixed to the cluster resources, but the min resources and steady fair share are still the config value. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7820:
Attachment: YARN-7820.003.patch
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, YARN-7820.003.patch,
> YARN-7820.003.patch, YARN-7820.003.patch, image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: YARN-7925.003.patch
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Blocker
> Attachments: DisplayError.png, YARN-7925.001.patch,
> YARN-7925.002.patch, YARN-7925.003.patch
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378388#comment-16378388
]
Jinjiang Ling commented on YARN-7925:
-
Hi [~sunilg]
I have uploaded the second patch, could you take a review ?
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Blocker
> Attachments: DisplayError.png, YARN-7925.001.patch,
> YARN-7925.002.patch
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: YARN-7925.002.patch
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Blocker
> Attachments: DisplayError.png, YARN-7925.001.patch,
> YARN-7925.002.patch
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362001#comment-16362001
]
Jinjiang Ling commented on YARN-7925:
-
Thanks for your review, [~sunilg]
I'll upload another patch later.
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Blocker
> Attachments: DisplayError.png, YARN-7925.001.patch
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: (was: YARN-7925.patch)
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: DisplayError.png
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: YARN-7925.001.patch
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: DisplayError.png, YARN-7925.001.patch
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: YARN-7925.patch
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: DisplayError.png
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Attachment: DisplayError.png
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: DisplayError.png
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !image-2018-02-13-07-57-39-128.png!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}
> ..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels
[
https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7925:
Description:
I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
when I add a new node label and append a nodemanager to it, sometimes it may
cause a display error.
!DisplayError.png|width=573,height=188!
Then I found *when there is no queues can access to the label*, this error
will happen.
After checking the log, I find some NPE errors.
{quote}..
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
..
{quote}
was:
I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
when I add a new node label and append a nodemanager to it, sometimes it may
cause a display error.
!image-2018-02-13-07-57-39-128.png!
Then I found *when there is no queues can access to the label*, this error
will happen.
After checking the log, I find some NPE errors.
{quote}
..
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
..
{quote}
> Some NPE errors caused a display errors when setting node labels
>
>
> Key: YARN-7925
> URL: https://issues.apache.org/jira/browse/YARN-7925
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: DisplayError.png
>
>
> I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
> when I add a new node label and append a nodemanager to it, sometimes it may
> cause a display error.
> !DisplayError.png|width=573,height=188!
> Then I found *when there is no queues can access to the label*, this error
> will happen.
> After checking the log, I find some NPE errors.
> {quote}..
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
> at
> org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
> ..
> {quote}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7925) Some NPE errors caused a display errors when setting node labels
Jinjiang Ling created YARN-7925:
---
Summary: Some NPE errors caused a display errors when setting node
labels
Key: YARN-7925
URL: https://issues.apache.org/jira/browse/YARN-7925
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Jinjiang Ling
Assignee: Jinjiang Ling
I'm trying to using the node label with latest hadoop (3.1.0-SNAPSHOT). But
when I add a new node label and append a nodemanager to it, sometimes it may
cause a display error.
!image-2018-02-13-07-57-39-128.png!
Then I found *when there is no queues can access to the label*, this error
will happen.
After checking the log, I find some NPE errors.
{quote}
..
Caused by: java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo.toString(ResourceInfo.java:73)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.CapacitySchedulerPage$LeafQueueInfoBlock.renderQueueCapacityInfo(CapacitySchedulerPage.java:160)
..
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348161#comment-16348161
]
Jinjiang Ling commented on YARN-7820:
-
Hi [~ajisakaa], could you take a review ?
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, YARN-7820.003.patch,
> YARN-7820.003.patch, image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348011#comment-16348011
]
Jinjiang Ling commented on YARN-7820:
-
The test's failure is caused by YARN-7817 and YARN-7860.
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, YARN-7820.003.patch,
> YARN-7820.003.patch, image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7820:
Attachment: YARN-7820.003.patch
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, YARN-7820.003.patch,
> YARN-7820.003.patch, image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343142#comment-16343142
]
Jinjiang Ling commented on YARN-7698:
-
Hi [~ajisakaa], could please you review it ?
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7698.001.patch, YARN-7698.002.patch,
> YARN-7698.002.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343139#comment-16343139
]
Jinjiang Ling commented on YARN-7698:
-
This patch is just changing two variables' name, so I think the failure of unit
test has no relationship with it.
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7698.001.patch, YARN-7698.002.patch,
> YARN-7698.002.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7820:
Attachment: YARN-7820.003.patch
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, YARN-7820.003.patch,
> image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7698:
Priority: Major (was: Minor)
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7698.001.patch, YARN-7698.002.patch,
> YARN-7698.002.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
[
https://issues.apache.org/jira/browse/YARN-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7820:
Attachment: YARN-7820.001.patch
> Fix the currentAppAttemptId error in AHS when an application is running
> ---
>
> Key: YARN-7820
> URL: https://issues.apache.org/jira/browse/YARN-7820
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Major
> Attachments: YARN-7820.001.patch, image-2018-01-26-14-35-09-796.png
>
>
> When I using the REST API of the AHS to get a running app's latest attempt
> id, it always returns a invalid id like
> *appattempt_1516873125047_0013_{color:#FF}-01{color}*.
> But when the app is finished, the RM will push a finished event which
> contains the latest attempt id to TimelineServer, so the id will transitive
> to a correct one in the end of the application.
> I think as the app is running, this value should be a correct one, so I add
> the latest attempt id in the other info of the app's entity when the app
> trans to RUNNING state. Then the AHS will use this value to set the
> currentAppAttemptId.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7820) Fix the currentAppAttemptId error in AHS when an application is running
Jinjiang Ling created YARN-7820:
---
Summary: Fix the currentAppAttemptId error in AHS when an
application is running
Key: YARN-7820
URL: https://issues.apache.org/jira/browse/YARN-7820
Project: Hadoop YARN
Issue Type: Bug
Components: timelineserver
Reporter: Jinjiang Ling
Assignee: Jinjiang Ling
Attachments: image-2018-01-26-14-35-09-796.png
When I using the REST API of the AHS to get a running app's latest attempt id,
it always returns a invalid id like
*appattempt_1516873125047_0013_{color:#FF}-01{color}*.
But when the app is finished, the RM will push a finished event which contains
the latest attempt id to TimelineServer, so the id will transitive to a correct
one in the end of the application.
I think as the app is running, this value should be a correct one, so I add the
latest attempt id in the other info of the app's entity when the app trans to
RUNNING state. Then the AHS will use this value to set the currentAppAttemptId.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7698:
Attachment: YARN-7698.002.patch
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Minor
> Attachments: YARN-7698.001.patch, YARN-7698.002.patch,
> YARN-7698.002.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7698:
Attachment: YARN-7698.002.patch
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Minor
> Attachments: YARN-7698.001.patch, YARN-7698.002.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
[
https://issues.apache.org/jira/browse/YARN-7698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7698:
Attachment: YARN-7698.001.patch
> A misleading variable's name in ApplicationAttemptEventDispatcher
> -
>
> Key: YARN-7698
> URL: https://issues.apache.org/jira/browse/YARN-7698
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Minor
> Attachments: YARN-7698.001.patch
>
>
> I find there are two variables named "appAttemptId" in
> ApplicationAttemptEventDispatcher.
> {code:java}
> public static final class ApplicationAttemptEventDispatcher implements
> EventHandler {
>
> public void handle(RMAppAttemptEvent event) {
> ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
> ApplicationId appAttemptId = appAttemptID.getApplicationId();
>
> }
> {code}
> The first one is named as "{color:red}appAttemptID{color}" which is the true
> attempt id.
> The other one is named as "{color:red}appAttemptId{color}", but I think it's
> currect name should be "appId".
> I'm not sure there are any reason to name the application id as
> "appAttemptId". But I think two "appAttemptId" in one function may cause some
> misleading, so it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7698) A misleading variable's name in ApplicationAttemptEventDispatcher
Jinjiang Ling created YARN-7698:
---
Summary: A misleading variable's name in
ApplicationAttemptEventDispatcher
Key: YARN-7698
URL: https://issues.apache.org/jira/browse/YARN-7698
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Reporter: Jinjiang Ling
Assignee: Jinjiang Ling
Priority: Minor
I find there are two variables named "appAttemptId" in
ApplicationAttemptEventDispatcher.
{code:java}
public static final class ApplicationAttemptEventDispatcher implements
EventHandler {
public void handle(RMAppAttemptEvent event) {
ApplicationAttemptId appAttemptID = event.getApplicationAttemptId();
ApplicationId appAttemptId = appAttemptID.getApplicationId();
}
{code}
The first one is named as "{color:red}appAttemptID{color}" which is the true
attempt id.
The other one is named as "{color:red}appAttemptId{color}", but I think it's
currect name should be "appId".
I'm not sure there are any reason to name the application id as "appAttemptId".
But I think two "appAttemptId" in one function may cause some misleading, so
it's better to fix the second one to "appId"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7128) The error message in TimelineSchemaCreator is not enough to find out the error.
[
https://issues.apache.org/jira/browse/YARN-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152650#comment-16152650
]
Jinjiang Ling commented on YARN-7128:
-
[~vrushalic], thanks for your review.
The warning in prechecks is that the patch doesn't appear to include any new or
modified tests. I think it is not necessory to update tests in it.
> The error message in TimelineSchemaCreator is not enough to find out the
> error.
> ---
>
> Key: YARN-7128
> URL: https://issues.apache.org/jira/browse/YARN-7128
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
>Affects Versions: 3.0.0-beta1
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
> Attachments: YARN-7128.patch
>
>
> When I run the schema creator tool of timeline service v2, then an error
> happened with the error message below:
> {quote}
> 17/08/30 16:04:18 INFO zookeeper.ClientCnxn: Session establishment complete
> on server zdh175/10.43.183.175:2181, sessionid = 0x15e0d065a330019,
> negotiated timeout = 18
> 17/08/30 16:04:18 WARN util.HeapMemorySizeUtil:
> hbase.regionserver.global.memstore.upperLimit is deprecated by
> hbase.regionserver.global.memstore.size
> 17/08/30 16:04:18 ERROR storage.TimelineSchemaCreator: Error in creating
> hbase tables: java.lang.reflect.InvocationTargetException
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> But I can't tell which error caused this exception with message.
> Then I find it only print the exception message in TimelineSchemaCreator
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: " + e.getMessage());
> exceptions.add(e);
> }
> {code}
> I change it like this
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: ", e);
> exceptions.add(e);
> }
> {code}
> finally, I get the detail of this error, and it's caused by a directory of
> hbase not created.
> {quote}
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
> ... 10 more
> Caused by: java.lang.RuntimeException: Failed to create local dir
> /data1/zdh/hbase/tmp/RegionServer/local/jars, DynamicClassLoader failed to
> init
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.initTempDir(DynamicClassLoader.java:110)
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:98)
> at
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:244)
> ... 15 more
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> As the exception message is not enough to find out the error, so I think
> print all the information of the exception in TimelineSchemaCreator is better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7128) The error message in TimelineSchemaCreator is not enough to find out the error.
[
https://issues.apache.org/jira/browse/YARN-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7128:
Component/s: timelineserver
> The error message in TimelineSchemaCreator is not enough to find out the
> error.
> ---
>
> Key: YARN-7128
> URL: https://issues.apache.org/jira/browse/YARN-7128
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Affects Versions: 3.0.0-beta1
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
> Attachments: YARN-7128.patch
>
>
> When I run the schema creator tool of timeline service v2, then an error
> happened with the error message below:
> {quote}
> 17/08/30 16:04:18 INFO zookeeper.ClientCnxn: Session establishment complete
> on server zdh175/10.43.183.175:2181, sessionid = 0x15e0d065a330019,
> negotiated timeout = 18
> 17/08/30 16:04:18 WARN util.HeapMemorySizeUtil:
> hbase.regionserver.global.memstore.upperLimit is deprecated by
> hbase.regionserver.global.memstore.size
> 17/08/30 16:04:18 ERROR storage.TimelineSchemaCreator: Error in creating
> hbase tables: java.lang.reflect.InvocationTargetException
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> But I can't tell which error caused this exception with message.
> Then I find it only print the exception message in TimelineSchemaCreator
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: " + e.getMessage());
> exceptions.add(e);
> }
> {code}
> I change it like this
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: ", e);
> exceptions.add(e);
> }
> {code}
> finally, I get the detail of this error, and it's caused by a directory of
> hbase not created.
> {quote}
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
> ... 10 more
> Caused by: java.lang.RuntimeException: Failed to create local dir
> /data1/zdh/hbase/tmp/RegionServer/local/jars, DynamicClassLoader failed to
> init
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.initTempDir(DynamicClassLoader.java:110)
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:98)
> at
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:244)
> ... 15 more
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> As the exception message is not enough to find out the error, so I think
> print all the information of the exception in TimelineSchemaCreator is better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7128) The error message in TimelineSchemaCreator is not enough to find out the error.
[
https://issues.apache.org/jira/browse/YARN-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-7128:
Attachment: YARN-7128.patch
> The error message in TimelineSchemaCreator is not enough to find out the
> error.
> ---
>
> Key: YARN-7128
> URL: https://issues.apache.org/jira/browse/YARN-7128
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-beta1
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
> Attachments: YARN-7128.patch
>
>
> When I run the schema creator tool of timeline service v2, then an error
> happened with the error message below:
> {quote}
> 17/08/30 16:04:18 INFO zookeeper.ClientCnxn: Session establishment complete
> on server zdh175/10.43.183.175:2181, sessionid = 0x15e0d065a330019,
> negotiated timeout = 18
> 17/08/30 16:04:18 WARN util.HeapMemorySizeUtil:
> hbase.regionserver.global.memstore.upperLimit is deprecated by
> hbase.regionserver.global.memstore.size
> 17/08/30 16:04:18 ERROR storage.TimelineSchemaCreator: Error in creating
> hbase tables: java.lang.reflect.InvocationTargetException
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:04:18 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> But I can't tell which error caused this exception with message.
> Then I find it only print the exception message in TimelineSchemaCreator
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: " + e.getMessage());
> exceptions.add(e);
> }
> {code}
> I change it like this
> {code}
> try {
> ..
> } catch (IOException e) {
> LOG.error("Error in creating hbase tables: ", e);
> exceptions.add(e);
> }
> {code}
> finally, I get the detail of this error, and it's caused by a directory of
> hbase not created.
> {quote}
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
> ... 10 more
> Caused by: java.lang.RuntimeException: Failed to create local dir
> /data1/zdh/hbase/tmp/RegionServer/local/jars, DynamicClassLoader failed to
> init
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.initTempDir(DynamicClassLoader.java:110)
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:98)
> at
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:244)
> ... 15 more
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: Schema creation
> finished with the following exceptions
> 17/08/30 16:03:42 WARN storage.TimelineSchemaCreator:
> java.lang.reflect.InvocationTargetException
> {quote}
> As the exception message is not enough to find out the error, so I think
> print all the information of the exception in TimelineSchemaCreator is better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7128) The error message in TimelineSchemaCreator is not enough to find out the error.
Jinjiang Ling created YARN-7128:
---
Summary: The error message in TimelineSchemaCreator is not enough
to find out the error.
Key: YARN-7128
URL: https://issues.apache.org/jira/browse/YARN-7128
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 3.0.0-beta1
Reporter: Jinjiang Ling
Assignee: Jinjiang Ling
When I run the schema creator tool of timeline service v2, then an error
happened with the error message below:
{quote}
17/08/30 16:04:18 INFO zookeeper.ClientCnxn: Session establishment complete on
server zdh175/10.43.183.175:2181, sessionid = 0x15e0d065a330019, negotiated
timeout = 18
17/08/30 16:04:18 WARN util.HeapMemorySizeUtil:
hbase.regionserver.global.memstore.upperLimit is deprecated by
hbase.regionserver.global.memstore.size
17/08/30 16:04:18 ERROR storage.TimelineSchemaCreator: Error in creating hbase
tables: java.lang.reflect.InvocationTargetException
17/08/30 16:04:18 WARN storage.TimelineSchemaCreator: Schema creation finished
with the following exceptions
17/08/30 16:04:18 WARN storage.TimelineSchemaCreator:
java.lang.reflect.InvocationTargetException
{quote}
But I can't tell which error caused this exception with message.
Then I find it only print the exception message in TimelineSchemaCreator
{code}
try {
..
} catch (IOException e) {
LOG.error("Error in creating hbase tables: " + e.getMessage());
exceptions.add(e);
}
{code}
I change it like this
{code}
try {
..
} catch (IOException e) {
LOG.error("Error in creating hbase tables: ", e);
exceptions.add(e);
}
{code}
finally, I get the detail of this error, and it's caused by a directory of
hbase not created.
{quote}
at
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
... 10 more
Caused by: java.lang.RuntimeException: Failed to create local dir
/data1/zdh/hbase/tmp/RegionServer/local/jars, DynamicClassLoader failed to init
at
org.apache.hadoop.hbase.util.DynamicClassLoader.initTempDir(DynamicClassLoader.java:110)
at
org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:98)
at
org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:244)
... 15 more
17/08/30 16:03:42 WARN storage.TimelineSchemaCreator: Schema creation finished
with the following exceptions
17/08/30 16:03:42 WARN storage.TimelineSchemaCreator:
java.lang.reflect.InvocationTargetException
{quote}
As the exception message is not enough to find out the error, so I think print
all the information of the exception in TimelineSchemaCreator is better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6980) The YARN_TIMELINE_HEAPSIZE does not work
[ https://issues.apache.org/jira/browse/YARN-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-6980: Attachment: YARN-6980-1.patch Thanks for your advice, [~aw]. Now I set both the Xms and Xmx in YARN_TIMELINESERVER_OPTS and it works, thank you. I update the patch and changed it in yarn-env.sh back to YARN_TIMELINESERVER_HEAPSIZE, because I think it would cause some misleading. > The YARN_TIMELINE_HEAPSIZE does not work > > > Key: YARN-6980 > URL: https://issues.apache.org/jira/browse/YARN-6980 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Minor > Attachments: YARN-6980-1.patch, YARN-6980.patch > > > As I want to set the java heap size of timeline server, I find there is a > variable named YARN_TIMELINE_HEAPSIZE in the comments of yarn-env.sh, then I > set it but does not work. > Then I find the variable is changed in > -[HADOOP-10950|https://issues.apache.org/jira/browse/HADOOP-10950]-, > but it is just changed in the comments of yarn-env.sh and don't in "yarn" and > "yarn.cmd" command. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6980) The YARN_TIMELINE_HEAPSIZE does not work
[ https://issues.apache.org/jira/browse/YARN-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-6980: Attachment: YARN-6980.patch Attach a patch, change the YARN_TIMELINESERVER_HEAPSIZE in "yarn" and "yarn.cmd" to YARN_TIMELINE_HEAPSIZE. > The YARN_TIMELINE_HEAPSIZE does not work > > > Key: YARN-6980 > URL: https://issues.apache.org/jira/browse/YARN-6980 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Jinjiang Ling >Assignee: Jinjiang Ling >Priority: Minor > Attachments: YARN-6980.patch > > > As I want to set the java heap size of timeline server, I find there is a > variable named YARN_TIMELINE_HEAPSIZE in the comments of yarn-env.sh, then I > set it but does not work. > Then I find the variable is changed in > -[HADOOP-10950|https://issues.apache.org/jira/browse/HADOOP-10950]-, > but it is just changed in the comments of yarn-env.sh and don't in "yarn" and > "yarn.cmd" command. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6980) The YARN_TIMELINE_HEAPSIZE does not work
Jinjiang Ling created YARN-6980: --- Summary: The YARN_TIMELINE_HEAPSIZE does not work Key: YARN-6980 URL: https://issues.apache.org/jira/browse/YARN-6980 Project: Hadoop YARN Issue Type: Bug Affects Versions: 3.0.0-alpha4 Reporter: Jinjiang Ling Assignee: Jinjiang Ling Priority: Minor As I want to set the java heap size of timeline server, I find there is a variable named YARN_TIMELINE_HEAPSIZE in the comments of yarn-env.sh, then I set it but does not work. Then I find the variable is changed in -[HADOOP-10950|https://issues.apache.org/jira/browse/HADOOP-10950]-, but it is just changed in the comments of yarn-env.sh and don't in "yarn" and "yarn.cmd" command. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6837) Null LocalResource visibility or resource type can crash the nodemanager
[
https://issues.apache.org/jira/browse/YARN-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095591#comment-16095591
]
Jinjiang Ling commented on YARN-6837:
-
[~jlowe], thanks for your review.
> Null LocalResource visibility or resource type can crash the nodemanager
>
>
> Key: YARN-6837
> URL: https://issues.apache.org/jira/browse/YARN-6837
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
> Fix For: 2.9.0, 3.0.0-beta1, 2.8.2
>
> Attachments: YARN-6837-1.patch, YARN-6837.patch
>
>
> When I write an yarn application, I create a LocalResource like this
> {quote}
> LocalResource resource = Records.newRecord(LocalResource.class);
> {quote}
> Because I forget to set the visibilty of it, so the job is failed when I
> submit it.
> But NodeManager shutdown one by one at the same time, and there is
> NullPointerExceptionin NodeManager's log:
> {quote}
> 2017-07-18 17:54:09,289 INFO
> org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=hadoop
> IP=10.43.156.177OPERATION=Start Container Request
> TARGET=ContainerManageImpl RESULT=SUCCESS
> APPID=application_1499221670783_0067
> CONTAINERID=container_1499221670783_0067_02_03
> 2017-07-18 17:54:09,292 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceSet.addResources(ResourceSet.java:84)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:868)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:819)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:1684)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:96)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1418)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1411)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:745)
> 2017-07-18 17:54:09,292 INFO
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
> Start request for container_1499221670783_0067_02_02 by user hadoop
> {quote}
> Then I change my code and still set the visibility to null
> {quote}
> LocalResource resource = LocalResource.newInstance(
> URL.fromURI(dst.toUri()),
> LocalResourceType.FILE,
> {color:red}null{color},
> fileStatus.getLen(),
> fileStatus.getModificationTime());
> {quote}
> This error still happen.
> At last I set the visibility to correct value, the error do not happen again.
> So I think the visibility of LocalResource is null will cause NodeManager
> shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6837) When the LocalResource's visibility is null, the NodeManager will shutdown
[
https://issues.apache.org/jira/browse/YARN-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-6837:
Attachment: YARN-6837-1.patch
[~jlowe] Thanks for your suggestion.
It seems that -[YARN-6403|https://issues.apache.org/jira/browse/YARN-6403]- is
similar to this error. I also find that the resource type is null will cause
this error, so I add resource visibility and type check after it.
Update patch.
> When the LocalResource's visibility is null, the NodeManager will shutdown
> --
>
> Key: YARN-6837
> URL: https://issues.apache.org/jira/browse/YARN-6837
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
> Attachments: YARN-6837-1.patch, YARN-6837.patch
>
>
> When I write an yarn application, I create a LocalResource like this
> {quote}
> LocalResource resource = Records.newRecord(LocalResource.class);
> {quote}
> Because I forget to set the visibilty of it, so the job is failed when I
> submit it.
> But NodeManager shutdown one by one at the same time, and there is
> NullPointerExceptionin NodeManager's log:
> {quote}
> 2017-07-18 17:54:09,289 INFO
> org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=hadoop
> IP=10.43.156.177OPERATION=Start Container Request
> TARGET=ContainerManageImpl RESULT=SUCCESS
> APPID=application_1499221670783_0067
> CONTAINERID=container_1499221670783_0067_02_03
> 2017-07-18 17:54:09,292 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceSet.addResources(ResourceSet.java:84)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:868)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:819)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:1684)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:96)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1418)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1411)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:745)
> 2017-07-18 17:54:09,292 INFO
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
> Start request for container_1499221670783_0067_02_02 by user hadoop
> {quote}
> Then I change my code and still set the visibility to null
> {quote}
> LocalResource resource = LocalResource.newInstance(
> URL.fromURI(dst.toUri()),
> LocalResourceType.FILE,
> {color:red}null{color},
> fileStatus.getLen(),
> fileStatus.getModificationTime());
> {quote}
> This error still happen.
> At last I set the visibility to correct value, the error do not happen again.
> So I think the visibility of LocalResource is null will cause NodeManager
> shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6837) When the LocalResource's visibility is null, the NodeManager will shutdown
[
https://issues.apache.org/jira/browse/YARN-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-6837:
Affects Version/s: 3.0.0-alpha4
> When the LocalResource's visibility is null, the NodeManager will shutdown
> --
>
> Key: YARN-6837
> URL: https://issues.apache.org/jira/browse/YARN-6837
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Jinjiang Ling
> Attachments: YARN-6837.patch
>
>
> When I write an yarn application, I create a LocalResource like this
> {quote}
> LocalResource resource = Records.newRecord(LocalResource.class);
> {quote}
> Because I forget to set the visibilty of it, so the job is failed when I
> submit it.
> But NodeManager shutdown one by one at the same time, and there is
> NullPointerExceptionin NodeManager's log:
> {quote}
> 2017-07-18 17:54:09,289 INFO
> org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=hadoop
> IP=10.43.156.177OPERATION=Start Container Request
> TARGET=ContainerManageImpl RESULT=SUCCESS
> APPID=application_1499221670783_0067
> CONTAINERID=container_1499221670783_0067_02_03
> 2017-07-18 17:54:09,292 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceSet.addResources(ResourceSet.java:84)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:868)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:819)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:1684)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:96)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1418)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1411)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:745)
> 2017-07-18 17:54:09,292 INFO
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
> Start request for container_1499221670783_0067_02_02 by user hadoop
> {quote}
> Then I change my code and still set the visibility to null
> {quote}
> LocalResource resource = LocalResource.newInstance(
> URL.fromURI(dst.toUri()),
> LocalResourceType.FILE,
> {color:red}null{color},
> fileStatus.getLen(),
> fileStatus.getModificationTime());
> {quote}
> This error still happen.
> At last I set the visibility to correct value, the error do not happen again.
> So I think the visibility of LocalResource is null will cause NodeManager
> shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6837) When the LocalResource's visibility is null, the NodeManager will shutdown
[
https://issues.apache.org/jira/browse/YARN-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-6837:
Attachment: YARN-6837.patch
Attach a patch to avoid this error.
> When the LocalResource's visibility is null, the NodeManager will shutdown
> --
>
> Key: YARN-6837
> URL: https://issues.apache.org/jira/browse/YARN-6837
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Jinjiang Ling
> Attachments: YARN-6837.patch
>
>
> When I write an yarn application, I create a LocalResource like this
> {quote}
> LocalResource resource = Records.newRecord(LocalResource.class);
> {quote}
> Because I forget to set the visibilty of it, so the job is failed when I
> submit it.
> But NodeManager shutdown one by one at the same time, and there is
> NullPointerExceptionin NodeManager's log:
> {quote}
> 2017-07-18 17:54:09,289 INFO
> org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=hadoop
> IP=10.43.156.177OPERATION=Start Container Request
> TARGET=ContainerManageImpl RESULT=SUCCESS
> APPID=application_1499221670783_0067
> CONTAINERID=container_1499221670783_0067_02_03
> 2017-07-18 17:54:09,292 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
> Error in dispatcher thread
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceSet.addResources(ResourceSet.java:84)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:868)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:819)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:1684)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:96)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1418)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1411)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
> at java.lang.Thread.run(Thread.java:745)
> 2017-07-18 17:54:09,292 INFO
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
> Start request for container_1499221670783_0067_02_02 by user hadoop
> {quote}
> Then I change my code and still set the visibility to null
> {quote}
> LocalResource resource = LocalResource.newInstance(
> URL.fromURI(dst.toUri()),
> LocalResourceType.FILE,
> {color:red}null{color},
> fileStatus.getLen(),
> fileStatus.getModificationTime());
> {quote}
> This error still happen.
> At last I set the visibility to correct value, the error do not happen again.
> So I think the visibility of LocalResource is null will cause NodeManager
> shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6837) When the LocalResource's visibility is null, the NodeManager will shutdown
Jinjiang Ling created YARN-6837:
---
Summary: When the LocalResource's visibility is null, the
NodeManager will shutdown
Key: YARN-6837
URL: https://issues.apache.org/jira/browse/YARN-6837
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jinjiang Ling
When I write an yarn application, I create a LocalResource like this
{quote}
LocalResource resource = Records.newRecord(LocalResource.class);
{quote}
Because I forget to set the visibilty of it, so the job is failed when I submit
it.
But NodeManager shutdown one by one at the same time, and there is
NullPointerExceptionin NodeManager's log:
{quote}
2017-07-18 17:54:09,289 INFO
org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=hadoop
IP=10.43.156.177OPERATION=Start Container Request
TARGET=ContainerManageImpl RESULT=SUCCESS
APPID=application_1499221670783_0067
CONTAINERID=container_1499221670783_0067_02_03
2017-07-18 17:54:09,292 FATAL org.apache.hadoop.yarn.event.AsyncDispatcher:
Error in dispatcher thread
java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceSet.addResources(ResourceSet.java:84)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:868)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl$RequestResourcesTransition.transition(ContainerImpl.java:819)
at
org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385)
at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
at
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:1684)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:96)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1418)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:1411)
at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:197)
at
org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:126)
at java.lang.Thread.run(Thread.java:745)
2017-07-18 17:54:09,292 INFO
org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
Start request for container_1499221670783_0067_02_02 by user hadoop
{quote}
Then I change my code and still set the visibility to null
{quote}
LocalResource resource = LocalResource.newInstance(
URL.fromURI(dst.toUri()),
LocalResourceType.FILE, {color:red}null{color},
fileStatus.getLen(),
fileStatus.getModificationTime());
{quote}
This error still happen.
At last I set the visibility to correct value, the error do not happen again.
So I think the visibility of LocalResource is null will cause NodeManager
shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6770) [Docs] A small mistake in the example of TimelineClient
[
https://issues.apache.org/jira/browse/YARN-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079760#comment-16079760
]
Jinjiang Ling commented on YARN-6770:
-
[~Naganarasimha], Thanks for your review.
> [Docs] A small mistake in the example of TimelineClient
> ---
>
> Key: YARN-6770
> URL: https://issues.apache.org/jira/browse/YARN-6770
> Project: Hadoop YARN
> Issue Type: Bug
> Components: docs
>Reporter: Jinjiang Ling
>Assignee: Jinjiang Ling
>Priority: Trivial
> Labels: newbie
> Fix For: 3.0.0-beta1, 2.8.3, 2.9
>
> Attachments: YARN-6770.patch
>
>
> I'm trying to use timeline client, then I copy the
> [example|http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/TimelineServer.html#Publishing_of_application_specific_data]
> into my application.
> But there is a small mistake here:
> {quote}
> myDomain.*_setID_*("MyDomain");
> .
> myEntity.*_setEntityID_*("MyApp1")
> {quote}
> The correct one should be
> {quote}
> myDomain.*_setId_*("MyDomain");
> .
> myEntity._*setEntityId*_("MyApp1");
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6770) [Docs] A small mistake in the example of TimelineClient
[
https://issues.apache.org/jira/browse/YARN-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjiang Ling updated YARN-6770:
Attachment: YARN-6770.patch
> [Docs] A small mistake in the example of TimelineClient
> ---
>
> Key: YARN-6770
> URL: https://issues.apache.org/jira/browse/YARN-6770
> Project: Hadoop YARN
> Issue Type: Bug
> Components: docs
>Reporter: Jinjiang Ling
>Priority: Trivial
> Attachments: YARN-6770.patch
>
>
> I'm trying to use timeline client, then I copy the
> [example|http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/TimelineServer.html#Publishing_of_application_specific_data]
> into my application.
> But there is a small mistake here:
> {quote}
> myDomain.*_setID_*("MyDomain");
> .
> myEntity.*_setEntityID_*("MyApp1")
> {quote}
> The correct one should be
> {quote}
> myDomain.*_setId_*("MyDomain");
> .
> myEntity._*setEntityId*_("MyApp1");
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6770) [Docs] A small mistake in the example of TimelineClient
Jinjiang Ling created YARN-6770:
---
Summary: [Docs] A small mistake in the example of TimelineClient
Key: YARN-6770
URL: https://issues.apache.org/jira/browse/YARN-6770
Project: Hadoop YARN
Issue Type: Bug
Components: docs
Reporter: Jinjiang Ling
Priority: Trivial
I'm trying to use timeline client, then I copy the
[example|http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/TimelineServer.html#Publishing_of_application_specific_data]
into my application.
But there is a small mistake here:
{quote}
myDomain.*_setID_*("MyDomain");
.
myEntity.*_setEntityID_*("MyApp1")
{quote}
The correct one should be
{quote}
myDomain.*_setId_*("MyDomain");
.
myEntity._*setEntityId*_("MyApp1");
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6478) Fix a spelling mistake in FileSystemTimelineWriter
[ https://issues.apache.org/jira/browse/YARN-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968468#comment-15968468 ] Jinjiang Ling commented on YARN-6478: - Hi [~Naganarasimha], I have attach a patch. Can you take a review? > Fix a spelling mistake in FileSystemTimelineWriter > -- > > Key: YARN-6478 > URL: https://issues.apache.org/jira/browse/YARN-6478 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jinjiang Ling >Priority: Trivial > Labels: newbie > Attachments: YARN-6478-0.patch > > > Find a spelling mistake in FileSystemTimelineWriter.java > the "writeSummmaryEntityLogs" should be "writeSummaryEntityLogs". -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6478) Fix a spelling mistake in FileSystemTimelineWriter
[ https://issues.apache.org/jira/browse/YARN-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-6478: Attachment: YARN-6478-0.patch > Fix a spelling mistake in FileSystemTimelineWriter > -- > > Key: YARN-6478 > URL: https://issues.apache.org/jira/browse/YARN-6478 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jinjiang Ling >Priority: Trivial > Attachments: YARN-6478-0.patch > > > Find a spelling mistake in FileSystemTimelineWriter.java > the "writeSummmaryEntityLogs" should be "writeSummaryEntityLogs". -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6478) Fix a spelling mistake in FileSystemTimelineWriter
[ https://issues.apache.org/jira/browse/YARN-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinjiang Ling updated YARN-6478: Description: Find a spelling mistake in FileSystemTimelineWriter.java the "writeSummmaryEntityLogs" should be "writeSummaryEntityLogs". was: Find a spelling mistake in FileSystemTimelineWriter.java the "write*Summmary*EntityLogs" should be "write*Summary*EntityLogs". > Fix a spelling mistake in FileSystemTimelineWriter > -- > > Key: YARN-6478 > URL: https://issues.apache.org/jira/browse/YARN-6478 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Jinjiang Ling >Priority: Trivial > > Find a spelling mistake in FileSystemTimelineWriter.java > the "writeSummmaryEntityLogs" should be "writeSummaryEntityLogs". -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6478) Fix a spelling mistake in FileSystemTimelineWriter
Jinjiang Ling created YARN-6478: --- Summary: Fix a spelling mistake in FileSystemTimelineWriter Key: YARN-6478 URL: https://issues.apache.org/jira/browse/YARN-6478 Project: Hadoop YARN Issue Type: Bug Reporter: Jinjiang Ling Priority: Trivial Find a spelling mistake in FileSystemTimelineWriter.java the "write*Summmary*EntityLogs" should be "write*Summary*EntityLogs". -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
