[infinispan-issues] [JBoss JIRA] (ISPN-3767) MassIndexer breaks search feature with one node cluster

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933088#comment-12933088 ] 

RH Bugzilla Integration commented on ISPN-3767:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 1038720|https://bugzilla.redhat.com/show_bug.cgi?id=1038720] from POST to ON_QA
                
> MassIndexer breaks search feature with one node cluster
> -------------------------------------------------------
>
>                 Key: ISPN-3767
>                 URL: https://issues.jboss.org/browse/ISPN-3767
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.2.4.Final
>            Reporter: Romain Pelisse
>            Assignee: Adrian Nistor
>              Labels: 620
>             Fix For: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Final
>
>
> Hi,
> Trying to cope with the extreme slowliness of put() operation with indexing [1], I've tried to use the MassIndexer, to create the index AFTER adding all the data in the grid. This actually works pretty well, but, when running in a "single node" grid, it "breaks" the search, which always returns 0 result to any kind of query.
> I've modified one of the test suite of InfiniSpan to reproduce the issue:
> https://github.com/rpelisse/infinispan/tree/mass-indexer-breaks-search-with-mono-instance 
> Once this branch is checked out, just run :
> $ cd ./query
> $  mvn clean -Dtest=org.infinispan.query.distributed.DistributedMassIndexingTest test
> Note: MassIndexer being implemented using the Map/Reduce algorithm, it requires to run within a cluster (ie several instances of ISPN).
> [1] http://stackoverflow.com/questions/10090361/infinispan-very-slow-for-loading-data-with-indexing-can-it-be-made-faster
> If run within a single node cluster, the MassIndexer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira