[
https://issues.apache.org/jira/browse/HBASE-15650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245481#comment-15245481
]
Duo Zhang commented on HBASE-15650:
-----------------------------------
[~stack]
{{TestVisibilityLabelsWithDeletes.testDeleteColumnWithLatestTimeStampWhenNoVersionMatches}}
fails with this exception
{noformat}
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException:
Timestamp cannot be negative. minStamp:-9223372036854775808, maxStamp:128
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.hadoop.hbase.procedure.flush.RegionServerFlushTableProcedureManager$FlushTableSubprocedurePool.waitForOutstandingTasks(RegionServerFlushTableProcedureManager.java:251)
at
org.apache.hadoop.hbase.procedure.flush.FlushTableSubprocedure.flushRegions(FlushTableSubprocedure.java:102)
at
org.apache.hadoop.hbase.procedure.flush.FlushTableSubprocedure.acquireBarrier(FlushTableSubprocedure.java:113)
at
org.apache.hadoop.hbase.procedure.Subprocedure.call(Subprocedure.java:166)
at
org.apache.hadoop.hbase.procedure.Subprocedure.call(Subprocedure.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Timestamp cannot be negative.
minStamp:-9223372036854775808, maxStamp:128
at org.apache.hadoop.hbase.io.TimeRange.<init>(TimeRange.java:81)
at
org.apache.hadoop.hbase.regionserver.TimeRangeTracker.toTimeRange(TimeRangeTracker.java:204)
at
org.apache.hadoop.hbase.regionserver.ImmutableSegment.<init>(ImmutableSegment.java:44)
at
org.apache.hadoop.hbase.regionserver.SegmentFactory.createImmutableSegment(SegmentFactory.java:57)
at
org.apache.hadoop.hbase.regionserver.DefaultMemStore.snapshot(DefaultMemStore.java:93)
at
org.apache.hadoop.hbase.regionserver.HStore$StoreFlusherImpl.prepare(HStore.java:2151)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2324)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2192)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2163)
at
org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:2054)
at org.apache.hadoop.hbase.regionserver.HRegion.flush(HRegion.java:1980)
at
org.apache.hadoop.hbase.procedure.flush.FlushTableSubprocedure$RegionFlushTask.call(FlushTableSubprocedure.java:68)
at
org.apache.hadoop.hbase.procedure.flush.FlushTableSubprocedure$RegionFlushTask.call(FlushTableSubprocedure.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
... 4 more
{noformat}
Seems caused by this patch?
Thanks.
> Remove TimeRangeTracker as point of contention when many threads reading a
> StoreFile
> ------------------------------------------------------------------------------------
>
> Key: HBASE-15650
> URL: https://issues.apache.org/jira/browse/HBASE-15650
> Project: HBase
> Issue Type: Bug
> Components: Performance
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: 15650.branch-1.patch, 15650.branch-1.patch, 15650.patch,
> 15650.patch, 15650v2.branch-1.patch, 15650v2.patch, 15650v3.patch,
> 15650v4.patch, 15650v5.patch, 15650v6.patch,
> Point-of-contention-on-random-read.png
>
>
> HBASE-12148 is about "Remove TimeRangeTracker as point of contention when
> many threads writing a Store". It is also a point of contention when reading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
