[
https://issues.apache.org/jira/browse/HBASE-26384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated HBASE-26384:
-----------------------------
Description:
When {{CompactingMemStore}} prepares flushing, {{CompactingMemStore.snapshot}}
uses {{CompactionPipeline#version}} to track whether the
{{CompactionPipeline#pipeline}} has
changed since it acquired {{VersionedSegmentsList}} last time before emptying
{{CompactionPipeline#pipeline}}. However, when
{{CompactingMemStore#inMemoryCompaction}} executes
{{CompactionPipeline#flattenOneSegment}}, it does not change the
{{CompactionPipeline#version}} , which could cause the
was:When Com
> Segment which already flushed to hfile may still be remained in
> CompactingMemStore
> ------------------------------------------------------------------------------------
>
> Key: HBASE-26384
> URL: https://issues.apache.org/jira/browse/HBASE-26384
> Project: HBase
> Issue Type: Bug
> Components: in-memory-compaction
> Affects Versions: 3.0.0-alpha-1, 2.4.7
> Reporter: chenglei
> Priority: Major
>
> When {{CompactingMemStore}} prepares flushing,
> {{CompactingMemStore.snapshot}} uses {{CompactionPipeline#version}} to track
> whether the {{CompactionPipeline#pipeline}} has
> changed since it acquired {{VersionedSegmentsList}} last time before
> emptying {{CompactionPipeline#pipeline}}. However, when
> {{CompactingMemStore#inMemoryCompaction}} executes
> {{CompactionPipeline#flattenOneSegment}}, it does not change the
> {{CompactionPipeline#version}} , which could cause the
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
