[jira] [Created] (YARN-3756) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

skrho created YARN-3756: --- Summary: The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container Key: YARN-3756 URL: https://issues.apache.org/jira/browse/YARN-3756 Project: Hadoo

[jira] [Created] (YARN-3757) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

skrho created YARN-3757: --- Summary: The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container Key: YARN-3757 URL: https://issues.apache.org/jira/browse/YARN-3757 Project: Hadoo

[jira] [Created] (YARN-3758) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

skrho created YARN-3758: --- Summary: The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container Key: YARN-3758 URL: https://issues.apache.org/jira/browse/YARN-3758 Project: Hadoo

[jira] [Updated] (YARN-3758) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

[ https://issues.apache.org/jira/browse/YARN-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] skrho updated YARN-3758: Description: Hello there~~ I have 2 clusters First cluster is 5 node , default 1 application queue, 8G Physical me

[jira] [Updated] (YARN-3758) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

[ https://issues.apache.org/jira/browse/YARN-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] skrho updated YARN-3758: Description: Hello there~~ I have 2 clusters First cluster is 5 node , default 1 application queue, Capacity sched

[jira] [Resolved] (YARN-3756) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

[ https://issues.apache.org/jira/browse/YARN-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] skrho resolved YARN-3756. - Resolution: Duplicate > The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not > working in conta

[jira] [Resolved] (YARN-3757) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container

[ https://issues.apache.org/jira/browse/YARN-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] skrho resolved YARN-3757. - Resolution: Duplicate > The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not > working in conta

[jira] [Created] (YARN-2775) There is no close method in NMWebServices#getLogs()

skrho created YARN-2775: --- Summary: There is no close method in NMWebServices#getLogs() Key: YARN-2775 URL: https://issues.apache.org/jira/browse/YARN-2775 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-2775) There is no close method in NMWebServices#getLogs()

[ https://issues.apache.org/jira/browse/YARN-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] skrho updated YARN-2775: Attachment: YARN-2775_001.patch I added close method.. so fileInputStream object is not accumulated in memory.. How a

[jira] [Commented] (YARN-2775) There is no close method in NMWebServices#getLogs()

[ https://issues.apache.org/jira/browse/YARN-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194239#comment-14194239 ] skrho commented on YARN-2775: - In oracle document.. Closes this file input stream and releases