[ https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204801#comment-16204801 ]
Hudson commented on HBASE-18966: -------------------------------- FAILURE: Integrated in Jenkins build HBase-2.0 #686 (See [https://builds.apache.org/job/HBase-2.0/686/]) HBASE-18966 Use non-sync TimeRangeTracker as a replacement for TimeRange (chia7712: rev a63d79837d2c47c2b226bd5d777f7beaedf95a8d) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MutableSegment.java * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ImmutableSegment.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/TimeRangeTracker.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompositeImmutableSegment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHStore.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Segment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactingToCellFlatMapMemStore.java > Use non-sync TimeRangeTracker as a replacement for TimeRange in > ImmutableSegment > -------------------------------------------------------------------------------- > > Key: HBASE-18966 > URL: https://issues.apache.org/jira/browse/HBASE-18966 > Project: HBase > Issue Type: Sub-task > Reporter: Chia-Ping Tsai > Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18966.v0.patch, HBASE-18966.v1.patch, > HBASE-18966.v2.patch, HBASE-18966.v2.patch, HBASE-18966.v3.patch > > > The in-memory compaction/merge updates only the {{TimeRangeTracker}} when > creating new {{ImmutableSegment}}, but the time information used to do time > filter is the {{TimeRange}} rather than {{TimeRangeTracker}}. It don't cause > any bugs currently because the {{TimeRange}} is used for store-level ts > filter only and the default {{TimeRange}} of {{ImmutableSegment}} created by > in-memory compaction/merge has the maximum ts range. > The {{TimeRange}} was used to be a snapshot of {{TimeRangeTracker}} for > avoiding the sync operation happening in {{TimeRangeTracker}}. We can use > non-sync trt introduced by HBASE-18753 to replace the {{TimeRange}}. -- This message was sent by Atlassian JIRA (v6.4.14#64029)