[jira] [Updated] (YARN-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Attachment: (was: 屏幕快照 2019-02-20 下午2.24.26.png)
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Affects Version/s: 3.1.0
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: fengyongshe
>Priority: Major
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Description:
The Queue Info is configured in fair-scheduler.xml like below
{color:#ff}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#ff}{color}
1024mb,1vcores
2048mb,2vcores
The Queue {color:#ff}root.deva{color} configured last will override
existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
like the {color}attachment
root.deva
||Used Resources:||
||Min Resources:|. => should be <3072mb,3vcore>|
||Max Resources:|. => should be<4096mb,4vcores>|
||Reserved Resources:||
||Steady Fair Share:||
||Instantaneous Fair Share:||
root.deva.sample
||Min Resources:||
||Max Resources:||
||Reserved Resources:||
||Steady Fair Share:||
was:
The Queue Info is configured in fair-scheduler.xml like below
{color:#FF}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#FF}{color}
1024mb,1vcores
2048mb,2vcores
The Queue {color:#FF}root.deva{color} configured last will override
existing{color:#FF}{color:#d04437} root.deva{color} {color:#33}in
root.deva.sample, like this{color}{color}
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: 屏幕快照 2019-02-20 下午2.24.26.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Description:
The Queue Info is configured in fair-scheduler.xml like below
{color:#ff}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#ff}{color}
1024mb,1vcores
2048mb,2vcores
{color:#33}The Queue root.deva configured last will override existing
root.deva{color}{color:#33} in root.deva.sample, like the {color}attachment
root.deva
||Used Resources:||
||Min Resources:|. => should be <3072mb,3vcores>|
||Max Resources:|. => should be <4096mb,4vcores>|
||Reserved Resources:||
||Steady Fair Share:||
||Instantaneous Fair Share:||
root.deva.sample
||Min Resources:||
||Max Resources:||
||Reserved Resources:||
||Steady Fair Share:||
was:
The Queue Info is configured in fair-scheduler.xml like below
{color:#ff}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#ff}{color}
1024mb,1vcores
2048mb,2vcores
{color:#33}The Queue root.deva configured last will override existing
root.deva{color}{color:#33} {color:#33}in root.deva.sample, like the
{color}attachment {color}
root.deva
||Used Resources:||
||Min Resources:|. {color:#d04437} => should be
<3072mb,3vcore>{color}|
||Max Resources:|. {color:#d04437}=> should
be<4096mb,4vcores>{color}|
||Reserved Resources:||
||Steady Fair Share:||
||Instantaneous Fair Share:||
root.deva.sample
||Min Resources:||
||Max Resources:||
||Reserved Resources:||
||Steady Fair Share:||
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: fengyongshe
>Priority: Major
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> {color:#33}The Queue root.deva configured last will override existing
> root.deva{color}{color:#33} in root.deva.sample, like the
> {color}attachment
>
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcores>|
> ||Max Resources:|. => should be <4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
>
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Attachment: (was: 屏幕快照 2019-02-20 下午2.24.26.png)
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Fix For: 3.1.2
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#FF}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#FF}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#FF}root.deva{color} configured last will override
> existing{color:#FF}{color:#d04437} root.deva{color} {color:#33}in
> root.deva.sample, like this{color}{color}
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Description:
The Queue Info is configured in fair-scheduler.xml like below
{color:#ff}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#ff}{color}
1024mb,1vcores
2048mb,2vcores
{color:#33}The Queue root.deva configured last will override existing
root.deva{color}{color:#33} {color:#33}in root.deva.sample, like the
{color}attachment {color}
root.deva
||Used Resources:||
||Min Resources:|. {color:#d04437} => should be
<3072mb,3vcore>{color}|
||Max Resources:|. {color:#d04437}=> should
be<4096mb,4vcores>{color}|
||Reserved Resources:||
||Steady Fair Share:||
||Instantaneous Fair Share:||
root.deva.sample
||Min Resources:||
||Max Resources:||
||Reserved Resources:||
||Steady Fair Share:||
was:
The Queue Info is configured in fair-scheduler.xml like below
{color:#ff}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#ff}{color}
1024mb,1vcores
2048mb,2vcores
The Queue {color:#ff}root.deva{color} configured last will override
existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
like the {color}attachment
root.deva
||Used Resources:||
||Min Resources:|. => should be <3072mb,3vcore>|
||Max Resources:|. => should be<4096mb,4vcores>|
||Reserved Resources:||
||Steady Fair Share:||
||Instantaneous Fair Share:||
root.deva.sample
||Min Resources:||
||Max Resources:||
||Reserved Resources:||
||Steady Fair Share:||
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: fengyongshe
>Priority: Major
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> {color:#33}The Queue root.deva configured last will override existing
> root.deva{color}{color:#33} {color:#33}in root.deva.sample, like the
> {color}attachment {color}
> root.deva
> ||Used Resources:||
> ||Min Resources:|. {color:#d04437} => should be
> <3072mb,3vcore>{color}|
> ||Max Resources:|. {color:#d04437}=> should
> be<4096mb,4vcores>{color}|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Attachment: Fair Scheduler Mistake when configured same queue at same
level.png
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Fix Version/s: (was: 3.1.2)
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Attachments: Fair Scheduler Mistake when configured same queue at
> same level.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
[
https://issues.apache.org/jira/browse/YARN-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated YARN-9314:
--
Attachment: 屏幕快照 2019-02-20 下午2.24.26.png
> Fair Scheduler: Queue Info mistake when configured same queue name at same
> level
>
>
> Key: YARN-9314
> URL: https://issues.apache.org/jira/browse/YARN-9314
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: fengyongshe
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: 屏幕快照 2019-02-20 下午2.24.26.png
>
>
> The Queue Info is configured in fair-scheduler.xml like below
>
> {color:#ff}{color}
> 3072mb,3vcores
> 4096mb,4vcores
>
> 1024mb,1vcores
> 2048mb,2vcores
> Charlie
>
>
> {color:#ff}{color}
> 1024mb,1vcores
> 2048mb,2vcores
>
>
> The Queue {color:#ff}root.deva{color} configured last will override
> existing{color:#ff} root.deva{color} {color:#33}in root.deva.sample,
> like the {color}attachment
> root.deva
> ||Used Resources:||
> ||Min Resources:|. => should be <3072mb,3vcore>|
> ||Max Resources:|. => should be<4096mb,4vcores>|
> ||Reserved Resources:||
> ||Steady Fair Share:||
> ||Instantaneous Fair Share:||
> root.deva.sample
> ||Min Resources:||
> ||Max Resources:||
> ||Reserved Resources:||
> ||Steady Fair Share:||
>
>
--
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-9314) Fair Scheduler: Queue Info mistake when configured same queue name at same level
fengyongshe created YARN-9314:
-
Summary: Fair Scheduler: Queue Info mistake when configured same
queue name at same level
Key: YARN-9314
URL: https://issues.apache.org/jira/browse/YARN-9314
Project: Hadoop YARN
Issue Type: Bug
Reporter: fengyongshe
Fix For: 3.1.2
The Queue Info is configured in fair-scheduler.xml like below
{color:#FF}{color}
3072mb,3vcores
4096mb,4vcores
1024mb,1vcores
2048mb,2vcores
Charlie
{color:#FF}{color}
1024mb,1vcores
2048mb,2vcores
The Queue {color:#FF}root.deva{color} configured last will override
existing{color:#FF}{color:#d04437} root.deva{color} {color:#33}in
root.deva.sample, like this{color}{color}
--
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] [Resolved] (YARN-5661) transitionToActive blocks when enable work-preserving-recovery
[ https://issues.apache.org/jira/browse/YARN-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fengyongshe resolved YARN-5661. --- Resolution: Duplicate > transitionToActive blocks when enable work-preserving-recovery > -- > > Key: YARN-5661 > URL: https://issues.apache.org/jira/browse/YARN-5661 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.6.0 >Reporter: fengyongshe > > Consider scenario : Restart YARN with some application running or accepted, > when enable work-preserving-recovery, RM is failed to transition to Active > because of NullPointerException > 16-09-21 14:32:10,536 INFO fair.AllocationFileLoaderService > (AllocationFileLoaderService.java:reloadAllocations(209)) - Loading > allocation file /cmss/bch/bc1.3.1/hadoop/etc/hadoop/fair-scheduler.xml. > 2016-09-21 14:32:10,543 WARN resourcemanager.RMAuditLogger > (RMAuditLogger.java:logFailure(287)) - USER=yarn > OPERATION=transitionToActiveTARGET=RMHAProtocolService > RESULT=FAILURE DESCRIPTION=Exception transitioning to active PERMISSIONS= > 2016-09-21 14:32:10,543 WARN ha.ActiveStandbyElector > (ActiveStandbyElector.java:becomeActive(808)) - Exception handling the > winning of election > org.apache.hadoop.ha.ServiceFailedException: RM could not transition to Active > at > org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:124) > at > org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:804) > at > org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:415) > at > org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:599) > 2016-09-21 14:32:10,534 INFO util.HostsFileReader > (HostsFileReader.java:refresh(129)) - Refreshing hosts (include/exclude) list > 2016-09-21 14:32:10,537 INFO fair.QueueManager > (QueueManager.java:updateAllocationConfiguration(385)) - there is queue > root.default in fair scheduer used for test > 2016-09-21 14:32:10,537 INFO fair.QueueManager > (QueueManager.java:updateAllocationConfiguration(385)) - there is queue > root in fair scheduer used for test > 2016-09-21 14:32:10,543 WARN ha.ActiveStandbyElector > (ActiveStandbyElector.java:becomeActive(808)) - Exception handling the > winning of election > org.apache.hadoop.ha.ServiceFailedException: RM could not transition to Active > at > org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:124) > at > org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:804) > at > org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:415) > at > org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:599) > at > org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) > Caused by: org.apache.hadoop.ha.ServiceFailedException: Error when > transitioning to Active mode > at > org.apache.hadoop.yarn.server.resourcemanager.AdminService.transitionToActive(AdminService.java:307) > at > org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:122) > ... 4 more > Caused by: java.lang.NullPointerException > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.addApplicationAttempt(FairScheduler.java:748) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl$AttemptRecoveredTransition.transition(RMAppAttemptImpl.java:1045) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl$AttemptRecoveredTransition.transition(RMAppAttemptImpl.java:1009) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:760) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.access$1900(RMAppImpl.java:105) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:877) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:867) > at > org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385) > at > org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:742) > at >
[jira] [Created] (YARN-5661) transitionToActive blocks when enable work-preserving-recovery
fengyongshe created YARN-5661: - Summary: transitionToActive blocks when enable work-preserving-recovery Key: YARN-5661 URL: https://issues.apache.org/jira/browse/YARN-5661 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.6.0 Reporter: fengyongshe Consider scenario : Restart YARN with some application running or accepted, when enable work-preserving-recovery, RM is failed to transition to Active because of NullPointerException 16-09-21 14:32:10,536 INFO fair.AllocationFileLoaderService (AllocationFileLoaderService.java:reloadAllocations(209)) - Loading allocation file /cmss/bch/bc1.3.1/hadoop/etc/hadoop/fair-scheduler.xml. 2016-09-21 14:32:10,543 WARN resourcemanager.RMAuditLogger (RMAuditLogger.java:logFailure(287)) - USER=yarn OPERATION=transitionToActiveTARGET=RMHAProtocolService RESULT=FAILURE DESCRIPTION=Exception transitioning to active PERMISSIONS= 2016-09-21 14:32:10,543 WARN ha.ActiveStandbyElector (ActiveStandbyElector.java:becomeActive(808)) - Exception handling the winning of election org.apache.hadoop.ha.ServiceFailedException: RM could not transition to Active at org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:124) at org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:804) at org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:415) at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:599) 2016-09-21 14:32:10,534 INFO util.HostsFileReader (HostsFileReader.java:refresh(129)) - Refreshing hosts (include/exclude) list 2016-09-21 14:32:10,537 INFO fair.QueueManager (QueueManager.java:updateAllocationConfiguration(385)) - there is queue root.default in fair scheduer used for test 2016-09-21 14:32:10,537 INFO fair.QueueManager (QueueManager.java:updateAllocationConfiguration(385)) - there is queue root in fair scheduer used for test 2016-09-21 14:32:10,543 WARN ha.ActiveStandbyElector (ActiveStandbyElector.java:becomeActive(808)) - Exception handling the winning of election org.apache.hadoop.ha.ServiceFailedException: RM could not transition to Active at org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:124) at org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:804) at org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:415) at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:599) at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) Caused by: org.apache.hadoop.ha.ServiceFailedException: Error when transitioning to Active mode at org.apache.hadoop.yarn.server.resourcemanager.AdminService.transitionToActive(AdminService.java:307) at org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:122) ... 4 more Caused by: java.lang.NullPointerException at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.addApplicationAttempt(FairScheduler.java:748) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl$AttemptRecoveredTransition.transition(RMAppAttemptImpl.java:1045) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl$AttemptRecoveredTransition.transition(RMAppAttemptImpl.java:1009) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:760) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.access$1900(RMAppImpl.java:105) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:877) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl$RMAppRecoveredTransition.transition(RMAppImpl.java:867) at org.apache.hadoop.yarn.state.StateMachineFactory$MultipleInternalArc.doTransition(StateMachineFactory.java:385) at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448) at org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:742) at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recoverApplication(RMAppManager.java:313) at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recover(RMAppManager.java:419) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.recover(ResourceManager.java:1201) at
