Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0317A200BAA for ; Thu, 27 Oct 2016 21:32:01 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 01CFD160AF6; Thu, 27 Oct 2016 19:32:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 48655160B05 for ; Thu, 27 Oct 2016 21:32:00 +0200 (CEST) Received: (qmail 76552 invoked by uid 500); 27 Oct 2016 19:31:59 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 76122 invoked by uid 99); 27 Oct 2016 19:31:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2016 19:31:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id F33D92C2A67 for ; Thu, 27 Oct 2016 19:31:58 +0000 (UTC) Date: Thu, 27 Oct 2016 19:31:58 +0000 (UTC) From: "Ivan Bella (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-4502) Called next when there is no top MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 27 Oct 2016 19:32:01 -0000 [ https://issues.apache.org/jira/browse/ACCUMULO-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612927#comment-15612927 ] Ivan Bella commented on ACCUMULO-4502: -------------------------------------- The SourceSwitchingIterator logic seems to be sound. The only thing I can now come up with is that somehow the seek executed post switching the underlying data source somehow did not find a key that it originally found in the previous source iterator. That is actually a scary proposition so I hope it is wrong. > 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 > Assignee: Ivan Bella > Fix For: 1.7.3, 1.8.1, 2.0.0 > > > 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)