[ https://issues.apache.org/jira/browse/HBASE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355209#comment-16355209 ]
Anastasia Braginsky commented on HBASE-18294: --------------------------------------------- Hi All, Just want to add my 2 cents here. I believe that surely we should have an answer to OOME that is possible when working with majority of memory off-heap and some little on-heap. That can be answered with two on/off-heap-limit-flush-size counters as Eshcar suggested or something calculated as Eddie suggested. But we must give an answer to this problem. [~anoop.hbase], [~ram_krish] if you do not want MemStoreOffHeapFlushSize to be part of the description, then how do you suggest to resolve OOME having only one MemStoreFlushSize? We didn't hear from you for a while, please tell us what is your current opinion. Secondly, [~chancelq], where can I read more about self-managed memory Memstore? I am not aware about that. If you can explain it shortly, it will be very appreciated! Thanks, Anastasia > Reduce global heap pressure: flush based on heap occupancy > ---------------------------------------------------------- > > Key: HBASE-18294 > URL: https://issues.apache.org/jira/browse/HBASE-18294 > Project: HBase > Issue Type: Improvement > Affects Versions: 3.0.0 > Reporter: Eshcar Hillel > Assignee: Eshcar Hillel > Priority: Major > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-18294.01.patch, HBASE-18294.01.patch, > HBASE-18294.01.patch, HBASE-18294.01.patch, HBASE-18294.02.patch, > HBASE-18294.03.patch, HBASE-18294.04.patch, HBASE-18294.05.patch, > HBASE-18294.06.patch, HBASE-18294.07.patch, HBASE-18294.07.patch, > HBASE-18294.08.patch, HBASE-18294.09.patch, HBASE-18294.10.patch, > HBASE-18294.11.patch, HBASE-18294.11.patch, HBASE-18294.12.patch, > HBASE-18294.13.patch, HBASE-18294.15.patch, HBASE-18294.16.patch, > HBASE-18294.master.01.patch > > > A region is flushed if its memory component exceed a threshold (default size > is 128MB). > A flush policy decides whether to flush a store by comparing the size of the > store to another threshold (that can be configured with > hbase.hregion.percolumnfamilyflush.size.lower.bound). > Currently the implementation (in both cases) compares the data size > (key-value only) to the threshold where it should compare the heap size > (which includes index size, and metadata). -- This message was sent by Atlassian JIRA (v7.6.3#76005)