[jira] [Commented] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535626#comment-16535626 ] tangshangwen commented on YARN-8496: I'll update a patch later > The capacity sched

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Component/s: (was: resourcemanager) capacity scheduler > The capacity scheduler u

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Description:  In my cluster, I used label scheduling, and I found that it caused the vcore of the clu

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Attachment: (was: image-2018-07-05-18-29-32-697.png) > The capacity scheduler uses label to cause

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Description:  In my cluster, I used label scheduling, and I found that it caused the vcore of the clu

[jira] [Commented] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533497#comment-16533497 ] tangshangwen commented on YARN-8496:   I think it's important to check that the resou

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Attachment: image-2018-07-05-18-29-32-697.png > The capacity scheduler uses label to cause vcore to be

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Description:  In my cluster, I used tag scheduling, and I found that it caused the vcore of the clust

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Attachment: (was: image-2018-07-05-18-16-10-851.png) > The capacity scheduler uses label to cause

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Attachment: yarn-bug.png Description:  In my cluster, I used tag scheduling, and I found that it

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Description:  In my cluster, I used tag scheduling, and I found that it caused the vcore of the clust

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Attachment: image-2018-07-05-18-16-10-851.png > The capacity scheduler uses label to cause vcore to be

[jira] [Updated] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-8496: --- Description:     I n my cluster, I used tag scheduling, and I found that it caused the vcore of th

[jira] [Created] (YARN-8496) The capacity scheduler uses label to cause vcore to be incorrect

2018-07-05 Thread tangshangwen (JIRA)
tangshangwen created YARN-8496: -- Summary: The capacity scheduler uses label to cause vcore to be incorrect Key: YARN-8496 URL: https://issues.apache.org/jira/browse/YARN-8496 Project: Hadoop YARN

[jira] [Commented] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-11-11 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657056#comment-15657056 ] tangshangwen commented on YARN-5795: Hi [~templedf], would you like to review the patch

[jira] [Updated] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-28 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5795: --- Attachment: 0001-YARN-5795.patch > FairScheduler set AppMaster vcores didn't work > ---

[jira] [Commented] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-28 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614804#comment-15614804 ] tangshangwen commented on YARN-5795: hi [~kasha], i think the DefaultResourceCalculator

[jira] [Commented] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-27 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614196#comment-15614196 ] tangshangwen commented on YARN-5795: I think allocate method using DOMINANT RESOURCE CA

[jira] [Issue Comment Deleted] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-27 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5795: --- Comment: was deleted (was: I think if we replace RESOURCE_CALCULATOR with DOMINANT_RESOURCE_CALCULATOR

[jira] [Commented] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-27 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614149#comment-15614149 ] tangshangwen commented on YARN-5795: I think if we replace RESOURCE_CALCULATOR with DOM

[jira] [Created] (YARN-5795) FairScheduler set AppMaster vcores didn't work

2016-10-27 Thread tangshangwen (JIRA)
tangshangwen created YARN-5795: -- Summary: FairScheduler set AppMaster vcores didn't work Key: YARN-5795 URL: https://issues.apache.org/jira/browse/YARN-5795 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-5136) Error in handling event type APP_ATTEMPT_REMOVED to the scheduler

2016-09-29 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5136: --- Assignee: Wilfred Spiegelenburg (was: tangshangwen) > Error in handling event type APP_ATTEMPT_REMOVED

[jira] [Commented] (YARN-5136) Error in handling event type APP_ATTEMPT_REMOVED to the scheduler

2016-09-29 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532199#comment-15532199 ] tangshangwen commented on YARN-5136: [~wilfreds]ok > Error in handling event type APP_

[jira] [Commented] (YARN-5535) Remove RMDelegationToken make resourcemanager recovery very slow

2016-08-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426631#comment-15426631 ] tangshangwen commented on YARN-5535: I'm sorry, it is after recovery , and i found eve

[jira] [Commented] (YARN-5535) Remove RMDelegationToken make resourcemanager recovery very slow

2016-08-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426107#comment-15426107 ] tangshangwen commented on YARN-5535: Thanks [~sunilg] for the comments. I think Removi

[jira] [Updated] (YARN-5535) Remove RMDelegationToken make resourcemanager recovery very slow

2016-08-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5535: --- Description: In our cluster, I found that when restart RM, RM recovery is very slow, this is my log {n

[jira] [Updated] (YARN-5535) Remove RMDelegationToken make resourcemanager recovery very slow

2016-08-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5535: --- Description: In our cluster, I found that when restart RM, RM recovery is very slow, this is my log {n

[jira] [Created] (YARN-5535) Remove RMDelegationToken make resourcemanager recovery very slow

2016-08-18 Thread tangshangwen (JIRA)
tangshangwen created YARN-5535: -- Summary: Remove RMDelegationToken make resourcemanager recovery very slow Key: YARN-5535 URL: https://issues.apache.org/jira/browse/YARN-5535 Project: Hadoop YARN

[jira] [Resolved] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-08 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-5482. Resolution: Duplicate > ContainerMetric Lead to memory leaks > >

[jira] [Reopened] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-08 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen reopened YARN-5482: > ContainerMetric Lead to memory leaks > > > Key: YA

[jira] [Resolved] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-08 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-5482. Resolution: Fixed > ContainerMetric Lead to memory leaks > > >

[jira] [Commented] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-08 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411603#comment-15411603 ] tangshangwen commented on YARN-5482: Thanks [~bibinchundatt] > ContainerMetric Lead to

[jira] [Updated] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-07 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5482: --- Attachment: oom2.png oom1.png > ContainerMetric Lead to memory leaks >

[jira] [Created] (YARN-5482) ContainerMetric Lead to memory leaks

2016-08-07 Thread tangshangwen (JIRA)
tangshangwen created YARN-5482: -- Summary: ContainerMetric Lead to memory leaks Key: YARN-5482 URL: https://issues.apache.org/jira/browse/YARN-5482 Project: Hadoop YARN Issue Type: Bug Affect

[jira] [Created] (YARN-5187) when the preempt reduce happen, map resources priority should be higher

2016-05-31 Thread tangshangwen (JIRA)
tangshangwen created YARN-5187: -- Summary: when the preempt reduce happen, map resources priority should be higher Key: YARN-5187 URL: https://issues.apache.org/jira/browse/YARN-5187 Project: Hadoop YARN

[jira] [Created] (YARN-5136) Error in handling event type APP_ATTEMPT_REMOVED to the scheduler

2016-05-24 Thread tangshangwen (JIRA)
tangshangwen created YARN-5136: -- Summary: Error in handling event type APP_ATTEMPT_REMOVED to the scheduler Key: YARN-5136 URL: https://issues.apache.org/jira/browse/YARN-5136 Project: Hadoop YARN

[jira] [Created] (YARN-5134) Can't handle this event at current state Invalid event: FINISHED_CONTAINERS_PULLED_BY_AM at NEW

2016-05-24 Thread tangshangwen (JIRA)
tangshangwen created YARN-5134: -- Summary: Can't handle this event at current state Invalid event: FINISHED_CONTAINERS_PULLED_BY_AM at NEW Key: YARN-5134 URL: https://issues.apache.org/jira/browse/YARN-5134

[jira] [Created] (YARN-5133) Can't handle this event at current state Invalid event: FINISHED_CONTAINERS_PULLED_BY_AM at NEW

2016-05-24 Thread tangshangwen (JIRA)
tangshangwen created YARN-5133: -- Summary: Can't handle this event at current state Invalid event: FINISHED_CONTAINERS_PULLED_BY_AM at NEW Key: YARN-5133 URL: https://issues.apache.org/jira/browse/YARN-5133

[jira] [Commented] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-11 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279855#comment-15279855 ] tangshangwen commented on YARN-5051: yes, thanks [~kshukla] > The RM can't update the

[jira] [Commented] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273834#comment-15273834 ] tangshangwen commented on YARN-5051: I think should add NEW events in updateMetricsForR

[jira] [Commented] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273825#comment-15273825 ] tangshangwen commented on YARN-5051: when the nodemanager start will trigger the AddNod

[jira] [Commented] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273819#comment-15273819 ] tangshangwen commented on YARN-5051: The include hosts file not empty also have the sam

[jira] [Commented] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273815#comment-15273815 ] tangshangwen commented on YARN-5051: i think we should put the decommission node in Ina

[jira] [Updated] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5051: --- Description: When the RM restart,the RM will refuse the Decommission NodeManager register, and I put t

[jira] [Updated] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5051: --- Description: When the RM restart,the RM will refuse the Decommission NodeManager register, and I put t

[jira] [Updated] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-5051: --- Attachment: rm.png > The RM can't update the Decommissioned Nodes Metric >

[jira] [Created] (YARN-5051) The RM can't update the Decommissioned Nodes Metric

2016-05-06 Thread tangshangwen (JIRA)
tangshangwen created YARN-5051: -- Summary: The RM can't update the Decommissioned Nodes Metric Key: YARN-5051 URL: https://issues.apache.org/jira/browse/YARN-5051 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-5021) -1B of 3 GB physical memory used

2016-05-01 Thread tangshangwen (JIRA)
tangshangwen created YARN-5021: -- Summary: -1B of 3 GB physical memory used Key: YARN-5021 URL: https://issues.apache.org/jira/browse/YARN-5021 Project: Hadoop YARN Issue Type: Bug Re

[jira] [Updated] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

2016-01-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4598: --- Attachment: YARN-4598.1.patch I submitted a patch > Invalid event: RESOURCE_FAILED at CONTAINER_CLEANE

[jira] [Commented] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

2016-01-18 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105369#comment-15105369 ] tangshangwen commented on YARN-4598: I think we should add a transition , have any Sugg

[jira] [Created] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

2016-01-14 Thread tangshangwen (JIRA)
tangshangwen created YARN-4598: -- Summary: Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL Key: YARN-4598 URL: https://issues.apache.org/jira/browse/YARN-4598 Project: Hadoop YARN

[jira] [Reopened] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen reopened YARN-4539: > CommonNodeLabelsManager throw NullPointerException when the fairScheduler > init failed >

[jira] [Resolved] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-4539. Resolution: Duplicate > CommonNodeLabelsManager throw NullPointerException when the fairScheduler >

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084576#comment-15084576 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsMan

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084575#comment-15084575 ] tangshangwen commented on YARN-4539: OK, Thanks [~bibinchundatt] > CommonNodeLabelsMan

[jira] [Resolved] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-05 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen resolved YARN-4539. Resolution: Fixed > CommonNodeLabelsManager throw NullPointerException when the fairScheduler > init

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081522#comment-15081522 ] tangshangwen commented on YARN-4539: Yes, Thank you for your comment!!:D > CommonNodeL

[jira] [Updated] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4539: --- Description: When the scheduler initialization failed and RM stop compositeService cause the CommonNod

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081301#comment-15081301 ] tangshangwen commented on YARN-4539: I submitted a patch. > CommonNodeLabelsManager th

[jira] [Updated] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4539: --- Attachment: YARN-4539.1.patch > CommonNodeLabelsManager throw NullPointerException when the fairSchedul

[jira] [Commented] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081292#comment-15081292 ] tangshangwen commented on YARN-4539: I think asyncDispatcher should check whether the n

[jira] [Created] (YARN-4539) CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed

2016-01-04 Thread tangshangwen (JIRA)
tangshangwen created YARN-4539: -- Summary: CommonNodeLabelsManager throw NullPointerException when the fairScheduler init failed Key: YARN-4539 URL: https://issues.apache.org/jira/browse/YARN-4539 Project

[jira] [Commented] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2016-01-03 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080424#comment-15080424 ] tangshangwen commented on YARN-4530: Hi [~rohithsharma] , I need to write a test case ?

[jira] [Commented] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-31 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075855#comment-15075855 ] tangshangwen commented on YARN-4530: Hi [Rohith Sharma K S | https://issues.apache.org

[jira] [Updated] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-30 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4530: --- Attachment: YARN-4530.1.patch I found 2.7.1 have the same problem,I submitted a patch. > LocalizedReso

[jira] [Updated] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-30 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4530: --- Affects Version/s: 2.7.1 > LocalizedResource trigger a NPE Cause the NodeManager exit > ---

[jira] [Commented] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-30 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075711#comment-15075711 ] tangshangwen commented on YARN-4530: I think I can fix it > LocalizedResource trigger

[jira] [Commented] (YARN-4506) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-30 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075140#comment-15075140 ] tangshangwen commented on YARN-4506: Ok, I'll try to fix it > Application was killed b

[jira] [Commented] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-30 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075106#comment-15075106 ] tangshangwen commented on YARN-4530: when the assoc is null and the completed.get() thr

[jira] [Created] (YARN-4530) LocalizedResource trigger a NPE Cause the NodeManager exit

2015-12-30 Thread tangshangwen (JIRA)
tangshangwen created YARN-4530: -- Summary: LocalizedResource trigger a NPE Cause the NodeManager exit Key: YARN-4530 URL: https://issues.apache.org/jira/browse/YARN-4530 Project: Hadoop YARN Issu

[jira] [Commented] (YARN-4506) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071325#comment-15071325 ] tangshangwen commented on YARN-4506: I found when the MRAppMaster received a signal, th

[jira] [Commented] (YARN-4506) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071119#comment-15071119 ] tangshangwen commented on YARN-4506: I'm sure it happened in 2.2,because i fond AM was

[jira] [Updated] (YARN-4506) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4506: --- Attachment: am.rar i update my am.log > Application was killed by a resourcemanager, In the JobHistory

[jira] [Updated] (YARN-4507) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4507: --- Description: when the AppMaster was killed by RM, we can't see the job detail in jobhistory,this is my

[jira] [Created] (YARN-4507) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
tangshangwen created YARN-4507: -- Summary: Application was killed by a resourcemanager, In the JobHistory Can't see the job detail Key: YARN-4507 URL: https://issues.apache.org/jira/browse/YARN-4507 Proje

[jira] [Created] (YARN-4506) Application was killed by a resourcemanager, In the JobHistory Can't see the job detail

2015-12-24 Thread tangshangwen (JIRA)
tangshangwen created YARN-4506: -- Summary: Application was killed by a resourcemanager, In the JobHistory Can't see the job detail Key: YARN-4506 URL: https://issues.apache.org/jira/browse/YARN-4506 Proje

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-22 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: (was: am105361log.tar.gz) > AM hang more than 10 min was kill by RM > -

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-22 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: am105361log.tar.gz I update other AM Log > AM hang more than 10 min was kill by RM > -

[jira] [Commented] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-21 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066331#comment-15066331 ] tangshangwen commented on YARN-4324: i found this message in the jstack,is a JDK epoll

[jira] [Commented] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-15 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057690#comment-15057690 ] tangshangwen commented on YARN-4324: I found the RMContainerAllocator last contact RM i

[jira] [Commented] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-15 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057601#comment-15057601 ] tangshangwen commented on YARN-4324: Thank you for your attention,I have already upload

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-14 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: logs.rar I upload the new jstack and am logs > AM hang more than 10 min was kill by RM > -

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-14 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Attachment: yarn-nodemanager-dumpam.log > AM hang more than 10 min was kill by RM > ---

[jira] [Commented] (YARN-4324) AM hang more than 10 min was kill by RM

2015-12-14 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057380#comment-15057380 ] tangshangwen commented on YARN-4324: Because the job failure is random, i dump the am j

[jira] [Updated] (YARN-4324) AM hang more than 10 min was kill by RM

2015-11-01 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated YARN-4324: --- Description: this is my logs 2015-11-02 01:14:54,175 INFO [AsyncDispatcher event handler] org.apache.h

[jira] [Created] (YARN-4324) AM hang more than 10 min was kill by RM

2015-11-01 Thread tangshangwen (JIRA)
tangshangwen created YARN-4324: -- Summary: AM hang more than 10 min was kill by RM Key: YARN-4324 URL: https://issues.apache.org/jira/browse/YARN-4324 Project: Hadoop YARN Issue Type: Bug Aff

[jira] [Commented] (YARN-4099) Container LocalizedResource more than 10min was kill

2015-09-01 Thread tangshangwen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724949#comment-14724949 ] tangshangwen commented on YARN-4099: 2015-08-28 15:10:37,434 INFO org.apache.hadoop.ya

[jira] [Created] (YARN-4099) Container LocalizedResource more than 10min was kill

2015-09-01 Thread tangshangwen (JIRA)
tangshangwen created YARN-4099: -- Summary: Container LocalizedResource more than 10min was kill Key: YARN-4099 URL: https://issues.apache.org/jira/browse/YARN-4099 Project: Hadoop YARN Issue Type