Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: ivakegg <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-179-accumulo@git.apache.org>
In-Reply-To: <git-pr-179-accumulo@git.apache.org>
Subject: [GitHub] accumulo issue #179: ACCUMULO-4502 Added volative to some class members to m...
Content-Type: text/plain
Message-Id: <20161104191417.5651FE04EE@git1-us-west.apache.org>
Date: Fri,  4 Nov 2016 19:14:17 +0000 (UTC)
archived-at: Fri, 04 Nov 2016 19:14:19 -0000

Github user ivakegg commented on the issue:

    https://github.com/apache/accumulo/pull/179
  
    After an exhaustive search through this code, the only reason I can come up with is an issue with a member reference in the underlying HeapIterator.  The scenario would be as follows:
    
    thread 1: calls hasTop() which is invoked on then in memory data source
    thread 2: calls switchSource which sets up the new datasource and calls seek which results in topIdx being set
    thread1: calls next() which gets a value of null for topIdx
    
    So if topIdx is marked as volatile then this should not happen.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---