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 [email protected] or file a JIRA ticket
with INFRA.
---
