[
https://issues.jboss.org/browse/ISPN-3767?page=com.atlassian.jira.plugin....
]
Romain Pelisse updated ISPN-3767:
---------------------------------
Description:
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...
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
Assignee: Alan Field (was: Romain Pelisse)
MassIndexer breaks search feature with one node cluster
-------------------------------------------------------
Key: ISPN-3767
URL:
https://issues.jboss.org/browse/ISPN-3767
Project: Infinispan
Issue Type: Bug
Reporter: Romain Pelisse
Assignee: Alan Field
Priority: Minor
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...
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