[
https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-1829:
Description:
CapacityScheduler will validate new configuration to make sure all existing
queues are still p
[
https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-1829:
Description:
CapacityScheduler will validate new configuration to make sure all existing
queues are still p
[
https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-1829:
Description:
CapacityScheduler will validate new configuration to make sure all existing
queues are still p
PengZhang created YARN-1829:
---
Summary: CapacityScheduler can't schedule job after
misconfiguration
Key: YARN-1829
URL: https://issues.apache.org/jira/browse/YARN-1829
Project: Hadoop YARN
Issue Ty
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Attachment: YARN-876.patch
> Node resource is added twice when node comes back from unhealthy to healthy
>
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Attachment: (was: YARN-876.patch)
> Node resource is added twice when node comes back from unhealthy to
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Attachment: YARN-876.patch
patch for trunk
> Node resource is added twice when node comes back
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Description:
When an unhealthy restarts, its resource maybe added twice in scheduler.
First time is at node's r
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Description:
When an unhealthy restarts, its resource maybe added twice in scheduler.
First time is at node's r
[
https://issues.apache.org/jira/browse/YARN-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-876:
---
Description:
When an unhealthy restarts, its resource maybe added twice in scheduler.
First time is at node's r
PengZhang created YARN-876:
--
Summary: Node resource is added twice when node comes back from
unhealthy to healthy
Key: YARN-876
URL: https://issues.apache.org/jira/browse/YARN-876
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677857#comment-13677857
]
PengZhang commented on YARN-768:
Thanks [~tgraves], I'll watch that issue.
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677852#comment-13677852
]
PengZhang commented on YARN-721:
I checked YARN-370 and YARN-382，I think it's the same probl
[
https://issues.apache.org/jira/browse/YARN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-768:
---
Attachment: YARN-768_v1.patch
> RM crashes due to DNS issue
> ---
>
>
[
https://issues.apache.org/jira/browse/YARN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-768:
---
Attachment: (was: YARN-768.patch)
> RM crashes due to DNS issue
> ---
>
>
[
https://issues.apache.org/jira/browse/YARN-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-768:
---
Attachment: YARN-768.patch
simple patch for trunk
> RM crashes due to DNS issue
>
PengZhang created YARN-768:
--
Summary: RM crashes due to DNS issue
Key: YARN-768
URL: https://issues.apache.org/jira/browse/YARN-768
Project: Hadoop YARN
Issue Type: Bug
Reporter: PengZha
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672507#comment-13672507
]
PengZhang commented on YARN-721:
Anyone encountered this problem while using secured yarn (>
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665942#comment-13665942
]
PengZhang commented on YARN-721:
Yes. If security is not enabled, authorizeRequest() will do
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665030#comment-13665030
]
PengZhang commented on YARN-721:
Changes for this function in YARN-2 is shown below:
- pub
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-721:
---
Attachment: YARN-721.patch
simple patch for trunk
> ContainerManagerImpl failed to authorizeRe
[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PengZhang updated YARN-721:
---
Description:
When security is enabled, resource check will be failed. AM master cannot be
launched.
It reports
PengZhang created YARN-721:
--
Summary: ContainerManagerImpl failed to authorizeRequest
Key: YARN-721
URL: https://issues.apache.org/jira/browse/YARN-721
Project: Hadoop YARN
Issue Type: Bug
Affec
23 matches
Mail list logo
