Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> thread safety of IndexedDocIterator


Copy link to this message
-
Re: thread safety of IndexedDocIterator
On Mon, Nov 5, 2012 at 11:24 AM, Sukant Hajra <[EMAIL PROTECTED]>wrote:

> We noticed that IndexedDocIterator.java has the following private static
> fields:
>
>     private static Text indexColf = DEFAULT_INDEX_COLF;
>     private static Text docColf = DEFAULT_DOC_COLF;
>
> The init method, which sets these is synchronized.  Still, though, this
> synchronization doesn't seem enough to allow different runs of the
> iterator to
> use different values for indexColf and docColf.  One run will set the
> "Colf"
> variables one way atomically in the synchronized init method. . . and
> another
> run and immediately interleave in alternate "Colf" settings, which breaks
> the
> original iterator run.
>
> For now, we're not touching the indexColf and docColf, just leaving it as
> the
> defaults.
>
> We're not blocked by this.  We're just curious if there's a bug in this
> design.
> Also, if it's not a defect, we're interested in learning what system
> invariant
> of iterator execution makes this not a problem.
>

Sounds like a bug.  Feel free to open a ticket!

Billie

>
> Thanks,
> Sukant
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB