[ https://issues.apache.org/jira/browse/HBASE-21041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589622#comment-16589622 ]
Hudson commented on HBASE-21041: -------------------------------- Results for branch branch-2.1 [build #226 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/226/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/226//General_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/226//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/226//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > Memstore's heap size will be decreased to minus zero after flush > ---------------------------------------------------------------- > > Key: HBASE-21041 > URL: https://issues.apache.org/jira/browse/HBASE-21041 > Project: HBase > Issue Type: Bug > Affects Versions: 2.1.0, 2.0.1 > Reporter: Allan Yang > Assignee: Allan Yang > Priority: Major > Fix For: 3.0.0, 2.1.1, 2.0.2 > > Attachments: HBASE-21041.branch-2.0.001.patch, > HBASE-21041.branch-2.0.002.patch > > > When creating an active mutable segment (MutableSegment) in memstore, > MutableSegment's deep overheap (208 bytes) was added to its heap size, but > not to the region's memstore's heap size. And so was the immutable > segment(CSLMImmutableSegment) which the mutable segment turned into > (additional 8 bytes ) later. So after one flush, the memstore's heapsize will > be decreased to -216 bytes, The minus number will accumulate after every > flush. > CompactingMemstore has this problem too. > We need to record the overhead for CSLMImmutableSegment and MutableSegment to > the corresponding region's memstore size. > For CellArrayImmutableSegment, CellChunkImmutableSegment and > CompositeImmutableSegment , it is not necessary to do so, because inside > CompactingMemstore, the overheads are already be taken care of when transfer > a CSLMImmutableSegment into them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)