[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718673#comment-13718673
]
Hitesh Shah commented on YARN-389:
--
The static limit is there for a reason. No application
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718666#comment-13718666
]
Bikas Saha commented on YARN-389:
-
I dont think we can be good at predicting the future and
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718653#comment-13718653
]
Omkar Vinit Joshi commented on YARN-389:
Today this limit is static. This by default
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718643#comment-13718643
]
Zhijie Shen commented on YARN-389:
--
bq. The check that container resource > resource in the
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718571#comment-13718571
]
Bikas Saha commented on YARN-389:
-
We should check for container level requests during alloc
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718568#comment-13718568
]
Alejandro Abdelnur commented on YARN-389:
-
Wouldn't make sense to add a new status D
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718504#comment-13718504
]
Omkar Vinit Joshi commented on YARN-389:
[~zjshen] [~bikassaha] I think we should re
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611266#comment-13611266
]
Zhijie Shen commented on YARN-389:
--
@Bikas, the problem was produced by two issues:
1. The
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611037#comment-13611037
]
Bikas Saha commented on YARN-389:
-
bq. I've checked reason why the requested AM size is larg
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579562#comment-13579562
]
Zhijie Shen commented on YARN-389:
--
I've checked reason why the requested AM size is larger
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577128#comment-13577128
]
Zhijie Shen commented on YARN-389:
--
{quote}
Zhijie, what is your setting for yarn.scheduler
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574759#comment-13574759
]
Zhijie Shen commented on YARN-389:
--
Vinod, I didn't specify yarn.scheduler.maximum-allocati
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574756#comment-13574756
]
Arun C Murthy commented on YARN-389:
The way to fix this to cap yarn.scheduler.maximum-a
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574755#comment-13574755
]
Vinod Kumar Vavilapalli commented on YARN-389:
--
Zhijie, what is your setting fo
[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574753#comment-13574753
]
Vinod Kumar Vavilapalli commented on YARN-389:
--
Logs:
{code}
2013-02-07 19:05:
15 matches
Mail list logo