[
https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated HBASE-19320:
--
Labels: Replication (was: )
> document the mysterious direct memory leak in hbase
>
[
https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-19320:
--
Priority: Critical (was: Major)
> document the mysterious direct memory leak in hbase
>
[
https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-19320:
-
Attachment: HBASE-19320-master-v001.patch
After applying the jvm flag, our cluster is running
[
https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-19320:
-
Attachment: Screen Shot 2017-11-21 at 4.43.36 PM.png
Screen Shot 2017-11-21 at
[
https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-19320:
-
Affects Version/s: 1.2.6
> document the mysterious direct memory leak in hbase
>