[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12569: -- Fix Version/s: (was: 0.98.9) Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12569: -- Resolution: Fixed Release Note: Adds new HEAP_SETTINGS environment variable to ./bin/hbase. Set java on and offheap with this one variable. It equates as follows HEAP_SETTINGS=$JAVA_HEAP_MAX $JAVA_OFFHEAP_MAX Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-1+ Thanks for the patch [~patrickwhite] Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12569: -- Release Note: Adds new JAVA_OFFHEAP_MAX environment variable to ./bin/hbase. Set the max offheap memory java will request with this one variable. It combines with JAVA_HEAP_MAX as follows HEAP_SETTINGS=$JAVA_HEAP_MAX $JAVA_OFFHEAP_MAX (was: Adds new HEAP_SETTINGS environment variable to ./bin/hbase. Set java on and offheap with this one variable. It equates as follows HEAP_SETTINGS=$JAVA_HEAP_MAX $JAVA_OFFHEAP_MAX) Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12569: -- Release Note: Adds new HBASE_OFFHEAPSIZE environment variable to ./bin/hbase. Set the max offheap memory java will request with this one variable. It combines with HBASE_SIZE to determine the max amount of ram that the JVM can request. (was: Adds new JAVA_OFFHEAP_MAX environment variable to ./bin/hbase. Set the max offheap memory java will request with this one variable. It combines with JAVA_HEAP_MAX as follows HEAP_SETTINGS=$JAVA_HEAP_MAX $JAVA_OFFHEAP_MAX) Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12569: -- Release Note: Adds new HBASE_OFFHEAPSIZE environment variable to ./bin/hbase. Set the max offheap memory java will request with this one variable. It combines with HBASE_HEAPSIZE to determine the max amount of ram that the JVM can request. (was: Adds new HBASE_OFFHEAPSIZE environment variable to ./bin/hbase. Set the max offheap memory java will request with this one variable. It combines with HBASE_SIZE to determine the max amount of ram that the JVM can request.) Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick White updated HBASE-12569: -- Status: Patch Available (was: Open) Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick White updated HBASE-12569: -- Attachment: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12569) Control MaxDirectMemorySize in the same manner as heap size
[ https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12569: -- Attachment: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch Retry. Test fail seems unrelated Control MaxDirectMemorySize in the same manner as heap size --- Key: HBASE-12569 URL: https://issues.apache.org/jira/browse/HBASE-12569 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.98.7 Environment: CentOS 6 Reporter: Patrick White Assignee: Patrick White Priority: Minor Fix For: 2.0.0, 0.98.9, 0.99.2 Attachments: 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch, 0001-HBASE-12569-Update-scripts-to-control-MaxDirectMemor.patch It would make it much easier on us if we could manage MaxDirectMemorySize in the same way as heap. This patch allows that to happen. Note: I have not tested the *.cmd modifications as I don't have a Windows box (at the moment, can test at home) but look like they should work (famous last words). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
