[
https://issues.apache.org/jira/browse/HBASE-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224281#comment-14224281
]
Hudson commented on HBASE-12569:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK #5816 (See
[https://builds.apache.org/job/HBase-TRUNK/5816/])
HBASE-12569 Update scripts to control MaxDirectMemorySize via env vars (stack:
rev f2be914f73d39d288d40147ff1e582ad5a7989f2)
* src/main/docbkx/book.xml
* bin/hbase.cmd
* conf/hbase-env.cmd
* conf/hbase-env.sh
* bin/hbase
> 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)
