[ https://issues.apache.org/jira/browse/HBASE-15672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249234#comment-15249234 ]
Anoop Sam John commented on HBASE-15672: ---------------------------------------- Thanks for committing this Stack. Ya at least in this case of VC, there is no need to add Cell with -ve timestamp. > hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes fails > ---------------------------------------------------------------------- > > Key: HBASE-15672 > URL: https://issues.apache.org/jira/browse/HBASE-15672 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 0.99.0, 0.98.4 > Reporter: Vladimir Rodionov > Assignee: Anoop Sam John > Fix For: 2.0.0 > > Attachments: HBASE-15672.patch, HBASE-15672.patch > > > 016-04-18 15:02:50,632 WARN [member: '10.22.11.177,55156,1461016964801' > subprocedure-pool5-thread-1] > flush.RegionServerFlushTableProcedureManager$FlushTableSubprocedurePool(275): > Got Exception in FlushSubprocedurePool > 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:188) > 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:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > 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:262) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) -- This message was sent by Atlassian JIRA (v6.3.4#6332)