[
https://issues.jboss.org/browse/ISPN-3767?page=com.atlassian.jira.plugin....
]
Romain Pelisse commented on ISPN-3767:
--------------------------------------
Hi Adrian,
I think I created a bit too many test cases, as end up numeroting them :)
Cool to hear that the fix are on the way (no idea what you meant by PR, but sounds good
anyway :p). At this point, I just need one thing from you, that you double check the
project I published on github and called
[
ISPN-3767|https://github.com/rpelisse/ISPN-3767], and confirm to me if such set up *can
work* with ISPN 5.2.6 or not.
As you mentioned above, adding more than 2 nodes to the grid allowed the Mass Indexer to
works properly, and the query to work also (ie not "index corruption" or
"invalid state"). I've built this project in order to test that, and I still
run into the same issue (import is quick, mass indexing runs smoothly also, but any query
fails afterwards, returning always zero).
If there is no chance to have that working in ISPN 5.2.6 - which I find weird, because the
unit test seems to work, I'll switch to 6.0.0. Otherwise, I'll be happy to find
out what is wrong in my setup.
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
Fix For: 6.1.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-wi...
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-load...
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