[jira] [Commented] (HADOOP-15696) KMS performance regression due to too many open file descriptors after Jetty migration

2018-08-30 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598091#comment-16598091 ] Misha Dmitriev commented on HADOOP-15696: - [~xiaochen] I agree that any work on connection

[jira] [Commented] (HADOOP-15696) KMS performance regression due to too many open file descriptors after Jetty migration

2018-08-28 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595865#comment-16595865 ] Misha Dmitriev commented on HADOOP-15696: - I think the KMS client can be improved as follows.

[jira] [Commented] (HADOOP-15696) KMS performance regression due to too many open file descriptors after Jetty migration

2018-08-27 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594364#comment-16594364 ] Misha Dmitriev commented on HADOOP-15696: - Answering my own question: yes, it looks like indeed

[jira] [Commented] (HADOOP-15696) KMS performance regression due to too many open file descriptors after Jetty migration

2018-08-27 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594339#comment-16594339 ] Misha Dmitriev commented on HADOOP-15696: - To be precise, the suggested measure, that had such

[jira] [Commented] (HADOOP-15538) Possible RPC deadlock in Client

2018-07-10 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538911#comment-16538911 ] Misha Dmitriev commented on HADOOP-15538: - So, as far as I understand, we have two threads that

[jira] [Updated] (HADOOP-15067) GC time percentage reported in JvmMetrics should be a gauge, not counter

2017-11-22 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-15067: Status: Patch Available (was: In Progress) > GC time percentage reported in JvmMetrics

[jira] [Work started] (HADOOP-15067) GC time percentage reported in JvmMetrics should be a gauge, not counter

2017-11-22 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-15067 started by Misha Dmitriev. --- > GC time percentage reported in JvmMetrics should be a gauge, not

[jira] [Updated] (HADOOP-15067) GC time percentage reported in JvmMetrics should be a gauge, not counter

2017-11-22 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-15067: Attachment: HADOOP-15067.01.patch > GC time percentage reported in JvmMetrics should be a

[jira] [Commented] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-22 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263222#comment-16263222 ] Misha Dmitriev commented on HADOOP-14960: - Created

[jira] [Assigned] (HADOOP-15067) GC time percentage reported in JvmMetrics should be a gauge, not counter

2017-11-22 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev reassigned HADOOP-15067: --- Assignee: Misha Dmitriev > GC time percentage reported in JvmMetrics should be a

[jira] [Created] (HADOOP-15067) GC time percentage reported in JvmMetrics should be a gauge, not counter

2017-11-22 Thread Misha Dmitriev (JIRA)
Misha Dmitriev created HADOOP-15067: --- Summary: GC time percentage reported in JvmMetrics should be a gauge, not counter Key: HADOOP-15067 URL: https://issues.apache.org/jira/browse/HADOOP-15067

[jira] [Commented] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-21 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261861#comment-16261861 ] Misha Dmitriev commented on HADOOP-14960: - [~xkrogen] indeed, the GC time percentage is likely

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Attachment: HADOOP-14960.04.patch > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: In Progress (was: Patch Available) > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: Patch Available (was: In Progress) Addressed the latest Xiao's comments. > Add

[jira] [Commented] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-06 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241399#comment-16241399 ] Misha Dmitriev commented on HADOOP-14960: - Test failures above seem totally unrelated.

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-03 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: Patch Available (was: In Progress) > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-03 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Attachment: HADOOP-14960.03.patch > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-11-03 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: In Progress (was: Patch Available) > Add GC time percentage monitor/alerter >

[jira] [Commented] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-31 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16229368#comment-16229368 ] Misha Dmitriev commented on HADOOP-14960: - Thank you for the review, [~xiaochen]. See my

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-31 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: Patch Available (was: In Progress) > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-31 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Attachment: HADOOP-14960.02.patch > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-31 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: In Progress (was: Patch Available) > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-26 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Status: Patch Available (was: In Progress) > Add GC time percentage monitor/alerter >

[jira] [Updated] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-26 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14960: Attachment: HADOOP-14960.01.patch > Add GC time percentage monitor/alerter >

[jira] [Work started] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-26 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-14960 started by Misha Dmitriev. --- > Add GC time percentage monitor/alerter >

[jira] [Created] (HADOOP-14960) Add GC time percentage monitor/alerter

2017-10-18 Thread Misha Dmitriev (JIRA)
Misha Dmitriev created HADOOP-14960: --- Summary: Add GC time percentage monitor/alerter Key: HADOOP-14960 URL: https://issues.apache.org/jira/browse/HADOOP-14960 Project: Hadoop Common Issue

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: In Progress (was: Patch Available) > Configuration.updatingResource map should

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206692#comment-16206692 ] Misha Dmitriev commented on HADOOP-14938: - As far as I understand, the report above says that

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Patch Available (was: In Progress) > Configuration.updatingResource map should

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206582#comment-16206582 ] Misha Dmitriev commented on HADOOP-14938: - Ok, uploaded patches for both branch-3.0 and branch-2

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Attachment: HADOOP-14938.branch-2.01.patch > Configuration.updatingResource map should be

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Attachment: HADOOP-14938.branch-3.0.01.patch > Configuration.updatingResource map should

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Patch Available (was: In Progress) > Configuration.updatingResource map should

[jira] [Work started] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-14938 started by Misha Dmitriev. --- > Configuration.updatingResource map should be initialized lazily >

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-16 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Open (was: Patch Available) > Configuration.updatingResource map should be

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203961#comment-16203961 ] Misha Dmitriev commented on HADOOP-14938: - The only problem now is one comment from checkstyle,

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-12 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Patch Available (was: In Progress) > Configuration.updatingResource map should

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-12 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202879#comment-16202879 ] Misha Dmitriev commented on HADOOP-14938: - Thank you Robert. I've fixed checkstyle. Regarding

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-12 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: In Progress (was: Patch Available) > Configuration.updatingResource map should

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-12 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Attachment: HADOOP-14938.03.patch > Configuration.updatingResource map should be

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-11 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201400#comment-16201400 ] Misha Dmitriev commented on HADOOP-14938: - This time one test failed:

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-11 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Patch Available (was: In Progress) > Configuration.updatingResource map should

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-11 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Attachment: HADOOP-14938.02.patch Addressed Daniel's comments. I've added {{volatile}}

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-11 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: In Progress (was: Patch Available) > Configuration.updatingResource map should

[jira] [Commented] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-10 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199377#comment-16199377 ] Misha Dmitriev commented on HADOOP-14938: - The test failure looks completely unrelated. I'll

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Status: Patch Available (was: In Progress) > Configuration.updatingResource map should

[jira] [Updated] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14938: Attachment: HADOOP-14938.01.patch > Configuration.updatingResource map should be

[jira] [Assigned] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev reassigned HADOOP-14938: --- Assignee: Misha Dmitriev > Configuration.updatingResource map should be

[jira] [Work started] (HADOOP-14938) Configuration.updatingResource map should be initialized lazily

2017-10-09 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-14938 started by Misha Dmitriev. --- > Configuration.updatingResource map should be initialized lazily >

[jira] [Commented] (HADOOP-14688) Intern strings in KeyVersion and EncryptedKeyVersion

2017-08-23 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139371#comment-16139371 ] Misha Dmitriev commented on HADOOP-14688: - [~daryn]: when a live heap dump is captured, as done

[jira] [Updated] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14523: Status: Patch Available (was: In Progress) > OpensslAesCtrCryptoCodec.finalize() holds

[jira] [Updated] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14523: Attachment: HADOOP-14523.02.patch Fixed checkstyle. The test that failed on the previous

[jira] [Updated] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14523: Status: In Progress (was: Patch Available) > OpensslAesCtrCryptoCodec.finalize() holds

[jira] [Updated] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14523: Status: Patch Available (was: Open) > OpensslAesCtrCryptoCodec.finalize() holds

[jira] [Updated] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-13 Thread Misha Dmitriev (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misha Dmitriev updated HADOOP-14523: Attachment: HADOOP-14523.01.patch > OpensslAesCtrCryptoCodec.finalize() holds excessive

[jira] [Created] (HADOOP-14523) OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory

2017-06-12 Thread Misha Dmitriev (JIRA)
Misha Dmitriev created HADOOP-14523: --- Summary: OpensslAesCtrCryptoCodec.finalize() holds excessive amounts of memory Key: HADOOP-14523 URL: https://issues.apache.org/jira/browse/HADOOP-14523