[
https://issues.apache.org/jira/browse/YARN-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5222:
--
Attachment: YARN-5222.patch
> DockerContainerExecutor dosn't set work directory
>
zhengchenyu created YARN-5222:
-
Summary: DockerContainerExecutor：DockerContainerExecutor dosn't
set work directory
Key: YARN-5222
URL: https://issues.apache.org/jira/browse/YARN-5222
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5222:
--
Summary: DockerContainerExecutor dosn't set work directory (was:
[
https://issues.apache.org/jira/browse/YARN-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5222:
--
Attachment: (was: YARN-5222.patch)
> DockerContainerExecutor dosn't set work directory
>
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu resolved YARN-5846.
---
Resolution: Duplicate
Fix Version/s: 2.7.1
Release Note: please pay attention to YARN-5139
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829221#comment-15829221
]
zhengchenyu commented on YARN-5846:
---
please pay attention to YARN-5139
> Improve the fairscheduler
[
https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6091:
--
Affects Version/s: (was: 2.8.0)
2.8.1
> the AppMaster register failed when
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5846:
--
Priority: Critical (was: Minor)
> Improve the fairscheduler attemptScheduler
>
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5846:
--
Comment: was deleted
(was: Yeah! I thinks my suggestion may be a new scheduler. And YARN-5139 is
indeed
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646635#comment-15646635
]
zhengchenyu commented on YARN-5846:
---
Yeah! I thinks my suggestion may be a new scheduler. And YARN-5139
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646638#comment-15646638
]
zhengchenyu commented on YARN-5846:
---
Yeah! I thinks my suggestion may be a new scheduler. And YARN-5139
[
https://issues.apache.org/jira/browse/YARN-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646638#comment-15646638
]
zhengchenyu edited comment on YARN-5846 at 11/8/16 6:41 AM:
Yeah! I thinks my
zhengchenyu created YARN-5846:
-
Summary: Improve the fairscheduler attemptScheduler
Key: YARN-5846
URL: https://issues.apache.org/jira/browse/YARN-5846
Project: Hadoop YARN
Issue Type:
[
https://issues.apache.org/jira/browse/YARN-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15697478#comment-15697478
]
zhengchenyu commented on YARN-5188:
---
the dead lock is same with Yarn-4090. getQueueUserAcls got the
[
https://issues.apache.org/jira/browse/YARN-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15697477#comment-15697477
]
zhengchenyu commented on YARN-5188:
---
the dead lock is same with Yarn-4090. getQueueUserAcls got the
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/26/16 6:30 AM:
-
here we see a
[
https://issues.apache.org/jira/browse/YARN-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5188:
--
Comment: was deleted
(was: the dead lock is same with Yarn-4090. getQueueUserAcls got the object
lock
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Description:
When using LinuxContainer, the setting that
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Description:
When using LinuxContainer, the setting that
zhengchenyu created YARN-5936:
-
Summary: when cpu strict mode is closed, yarn couldn't assure
scheduling fairness between containers
Key: YARN-5936
URL: https://issues.apache.org/jira/browse/YARN-5936
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Description:
When using LinuxContainer, the setting that
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Description:
When using LinuxContainer, the setting that
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Description:
When using LinuxContainer, the setting that
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695579#comment-15695579
]
zhengchenyu commented on YARN-4090:
---
here we see a dead block:
"IPC Server handler 98 on 8032" is
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu commented on YARN-4090:
---
here we see a dead block:
"IPC Server handler 98 on 8032" is
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-4090:
--
Comment: was deleted
(was: here we see a dead block:
"IPC Server handler 98 on 8032" is waiting for
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 11:01 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 11:25 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 10:59 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 11:04 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 11:26 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695578#comment-15695578
]
zhengchenyu edited comment on YARN-4090 at 11/25/16 11:26 AM:
--
here we see a
[
https://issues.apache.org/jira/browse/YARN-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15680979#comment-15680979
]
zhengchenyu commented on YARN-5827:
---
Thanks! I tried Yarn-4553! I think that's a reasonable way to solve
zhengchenyu created YARN-5919:
-
Summary: FairSharePolicy is not reasonable when sorting the
application
Key: YARN-5919
URL: https://issues.apache.org/jira/browse/YARN-5919
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15683593#comment-15683593
]
zhengchenyu commented on YARN-5827:
---
Oh, my god! I found "/usr/lib/systemd/system/docker.service" has
[
https://issues.apache.org/jira/browse/YARN-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682331#comment-15682331
]
zhengchenyu commented on YARN-5827:
---
Sorry, I reconfigurated and restarted docker by your way. still
zhengchenyu created YARN-5827:
-
Summary: DockerLinuxContainer can't limit the cpu usage
Key: YARN-5827
URL: https://issues.apache.org/jira/browse/YARN-5827
Project: Hadoop YARN
Issue Type: Bug
zhengchenyu created YARN-6091:
-
Summary: the AppMaster register failed when use Docker on
LinuxContainer
Key: YARN-6091
URL: https://issues.apache.org/jira/browse/YARN-6091
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821472#comment-15821472
]
zhengchenyu commented on YARN-6091:
---
Here is the sever where appliation is running normally
{code}
[right
zhengchenyu created YARN-5964:
-
Summary: fairscheduler use too many object lock, leads to low
performance
Key: YARN-5964
URL: https://issues.apache.org/jira/browse/YARN-5964
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721247#comment-15721247
]
zhengchenyu commented on YARN-5936:
---
I think two reason both affect the performance, but I can't evaluate
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721341#comment-15721341
]
zhengchenyu commented on YARN-5936:
---
You didn't catch my meaning! In fact, I knew the reason of the
[
https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811409#comment-15811409
]
zhengchenyu commented on YARN-4090:
---
Take attention to the YARN-5188 which has better performance. Our
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763042#comment-15763042
]
zhengchenyu commented on YARN-5936:
---
I don't care the performance loss of cpu bandwith, because I know it
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763020#comment-15763020
]
zhengchenyu commented on YARN-5936:
---
But your "time" command is only related to it's own program, every
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763023#comment-15763023
]
zhengchenyu commented on YARN-5936:
---
But your "time" command is only related to it's own program, every
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15763021#comment-15763021
]
zhengchenyu commented on YARN-5936:
---
But your "time" command is only related to it's own program, every
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Comment: was deleted
(was: But your "time" command is only related to it's own program, every
program
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-5936:
--
Comment: was deleted
(was: But your "time" command is only related to it's own program, every
program
[
https://issues.apache.org/jira/browse/YARN-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu resolved YARN-5964.
---
Resolution: Duplicate
Release Note: This issue is duplicated. Please pay attention to YARN-3091
[
https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760010#comment-15760010
]
zhengchenyu commented on YARN-5936:
---
Because your program is a single-thread.
> when cpu strict mode is
[
https://issues.apache.org/jira/browse/YARN-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15759968#comment-15759968
]
zhengchenyu commented on YARN-5964:
---
Please pay attention to YARN-3091
> Lower the granularity of locks
[
https://issues.apache.org/jira/browse/YARN-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760615#comment-15760615
]
zhengchenyu commented on YARN-3091:
---
Sorry, although this issue is completed, I still wanna ask for
[
https://issues.apache.org/jira/browse/YARN-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760613#comment-15760613
]
zhengchenyu commented on YARN-3091:
---
Sorry, although this issue is completed, I still wanna ask for
[
https://issues.apache.org/jira/browse/YARN-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-3091:
--
Comment: was deleted
(was: Sorry, although this issue is completed, I still wanna ask for advice.
I
[
https://issues.apache.org/jira/browse/YARN-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730808#comment-15730808
]
zhengchenyu commented on YARN-5964:
---
When I found this problem, the continuous scheduling turned off. In
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948731#comment-15948731
]
zhengchenyu commented on YARN-6407:
---
[~yufeigu] [~ka...@cloudera.com]
We can't true off continuous
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948731#comment-15948731
]
zhengchenyu edited comment on YARN-6407 at 3/30/17 10:26 AM:
-
[~yufeigu]
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948731#comment-15948731
]
zhengchenyu edited comment on YARN-6407 at 3/30/17 10:26 AM:
-
[~yufeigu]
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948718#comment-15948718
]
zhengchenyu commented on YARN-6407:
---
[~dan...@cloudera.com]
Yes, I think so. Though this work is hard, I
zhengchenyu created YARN-6407:
-
Summary: Improve and fix locks of RM scheduler
Key: YARN-6407
URL: https://issues.apache.org/jira/browse/YARN-6407
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946630#comment-15946630
]
zhengchenyu edited comment on YARN-6407 at 3/29/17 6:53 AM:
[~vinodkv]
Can you
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946630#comment-15946630
]
zhengchenyu commented on YARN-6407:
---
[~vinodkv]
> Improve and fix locks of RM scheduler
>
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950187#comment-15950187
]
zhengchenyu commented on YARN-6407:
---
[~ka...@cloudera.com]
We have used delay scheduling to raise the
[
https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958176#comment-15958176
]
zhengchenyu commented on YARN-6091:
---
I just changed the judging condition of pclose's return code, then
[
https://issues.apache.org/jira/browse/YARN-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958524#comment-15958524
]
zhengchenyu commented on YARN-6407:
---
For exmaple, addNode and removeNode can't happen at the same time
[
https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073156#comment-16073156
]
zhengchenyu commented on YARN-2694:
---
[~naganarasimha...@apache.org] Thanks for your explaination, I know
[
https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073156#comment-16073156
]
zhengchenyu edited comment on YARN-2694 at 7/4/17 5:59 AM:
---
[
https://issues.apache.org/jira/browse/YARN-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071869#comment-16071869
]
zhengchenyu edited comment on YARN-6396 at 7/3/17 2:58 AM:
---
The invocation
[
https://issues.apache.org/jira/browse/YARN-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071998#comment-16071998
]
zhengchenyu commented on YARN-6299:
---
In FSAppAttempt, getMinShare return Resources.none(). So demand
[
https://issues.apache.org/jira/browse/YARN-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071869#comment-16071869
]
zhengchenyu commented on YARN-6396:
---
The invocation 'createAppDir' in initAppAggregator will also visit
[
https://issues.apache.org/jira/browse/YARN-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074232#comment-16074232
]
zhengchenyu commented on YARN-5188:
---
[~chenfolin] we use read-write lock to solve this problem!
>
[
https://issues.apache.org/jira/browse/YARN-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004604#comment-16004604
]
zhengchenyu commented on YARN-6568:
---
I solve this problem, when I set the timeout for queue.
In my first
[
https://issues.apache.org/jira/browse/YARN-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002155#comment-16002155
]
zhengchenyu commented on YARN-6568:
---
[~yufeigu]
First, in FairSharePolicy.FairShareComparator.compare,
[
https://issues.apache.org/jira/browse/YARN-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003908#comment-16003908
]
zhengchenyu edited comment on YARN-6568 at 5/10/17 1:57 AM:
[~yufeigu]
Sorry, I
[
https://issues.apache.org/jira/browse/YARN-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003908#comment-16003908
]
zhengchenyu commented on YARN-6568:
---
[~yufeigu]
Sorry, I didn't express definitely!
I said that the
[
https://issues.apache.org/jira/browse/YARN-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003908#comment-16003908
]
zhengchenyu edited comment on YARN-6568 at 5/10/17 1:56 AM:
[~yufeigu]
Sorry, I
zhengchenyu created YARN-6728:
-
Summary: Job will run slow when the performance of defaultFs
degrades and the log-aggregation is enable.
Key: YARN-6728
URL: https://issues.apache.org/jira/browse/YARN-6728
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6728:
--
Description:
In our cluster, I found many map keep "NEW" state for several minutes. Here I
got the
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6728:
--
Description:
In our cluster, I found many map keep "NEW" state for several minutes. Here I
got the
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6728:
--
Description:
In our cluster, I found many map keep "NEW" state for several minutes. Here I
got the
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16059056#comment-16059056
]
zhengchenyu commented on YARN-6728:
---
Our partner [~maobaolong] advice to remove
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6728:
--
Description:
In our cluster, I found many map keep "NEW" state for several minutes. Here I
got the
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-6728:
--
Attachment: YARN-6728.patch.00_branch-2.7
> Job will run slow when the performance of defaultFs degrades
[
https://issues.apache.org/jira/browse/YARN-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16059056#comment-16059056
]
zhengchenyu edited comment on YARN-6728 at 6/23/17 7:00 AM:
Our partner
[
https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053411#comment-16053411
]
zhengchenyu commented on YARN-2694:
---
I don't know why disabled the function of supporting multi-nodelabel
[
https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053411#comment-16053411
]
zhengchenyu edited comment on YARN-2694 at 6/19/17 2:21 AM:
I don't know why
zhengchenyu created YARN-6568:
-
Summary: A queue which runs a long time job couldn't acquire any
container for long time.
Key: YARN-6568
URL: https://issues.apache.org/jira/browse/YARN-6568
Project:
[
https://issues.apache.org/jira/browse/YARN-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7278:
--
Affects Version/s: (was: 2.7.1)
2.8.0
> LinuxContainer in docker mode will be
[
https://issues.apache.org/jira/browse/YARN-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189158#comment-16189158
]
zhengchenyu commented on YARN-7278:
---
[~ebadger]
Yes, you are right. I changed affects versions to 2.8.0.
[
https://issues.apache.org/jira/browse/YARN-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178812#comment-16178812
]
zhengchenyu commented on YARN-6223:
---
I thinks NM recovery for gpu doesn't take effect. Becuase
zhengchenyu created YARN-7278:
-
Summary: LinuxContainer in docker mode will be failed when
nodemanager restart, because timeout for docker is too slow.
Key: YARN-7278
URL:
[
https://issues.apache.org/jira/browse/YARN-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7278:
--
Description:
In our cluster, nodemanagere recovery is turn on, and we use LinuxConainer with
docker
[
https://issues.apache.org/jira/browse/YARN-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178761#comment-16178761
]
zhengchenyu commented on YARN-6223:
---
I think there is a bug in below code.
{code}
try {
[
https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265918#comment-16265918
]
zhengchenyu commented on YARN-7560:
---
[~yufeigu]
the sum of all queue's minRes is over int.max
>
zhengchenyu created YARN-7560:
-
Summary: Resourcemanager hangs when
resourceUsedWithWeightToResourceRatio return a overflow value
Key: YARN-7560
URL: https://issues.apache.org/jira/browse/YARN-7560
[
https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7560:
--
Attachment: YARN-7560.patch.00
> Resourcemanager hangs when resourceUsedWithWeightToResourceRatio
[
https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7560:
--
Description:
In our cluster, we changed the configuration, then refreshQueues, we found the
[
https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7560:
--
Attachment: YARN-7560.000.patch
> Resourcemanager hangs when resourceUsedWithWeightToResourceRatio
[
https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhengchenyu updated YARN-7560:
--
Fix Version/s: (was: 2.7.5)
3.0.0
> Resourcemanager hangs when
1 - 100 of 253 matches
Mail list logo
