You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Ivan Bella (JIRA)" <ji...@apache.org> on 2016/10/24 17:48:58 UTC
[jira] [Created] (ACCUMULO-4502) Called next when there is no top
Ivan Bella created ACCUMULO-4502:
------------------------------------
Summary: Called next when there is no top
Key: ACCUMULO-4502
URL: https://issues.apache.org/jira/browse/ACCUMULO-4502
Project: Accumulo
Issue Type: Bug
Components: core, tserver
Affects Versions: 1.6.6
Reporter: Ivan Bella
This happens very rarely but we have seen the following exception (pulled from a server running 1.6.4). Looking at the code I believe this condition can still happen in 1.8.0:
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Called next() when there is no top
...
Caused by: java.lang.IllegalStateException: Called next() when there is no top
HeapIterator.next(HeapIterator.java: 77)
WrappingIterator.next(WrappingIterator.java: 96)
MemKeyConversionIterator.next(InMemoryMap.java:162)
SourceSwitchingIterator.readNext(SourceSwitchingIterator.java: 139)
SourceSwitchingIterator.next(SourceSwitchingIterator.java: 123)
PartialMutationSkippingIterator.consume(InMemoryMap.java:108)
SkippingIterator.seek(SkippingIterator.java:43)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)