[
https://issues.jboss.org/browse/ISPN-2835?page=com.atlassian.jira.plugin....
]
Anna Manukyan commented on ISPN-2835:
-------------------------------------
Hi Ray,
I've run your tests and look deeper into that, and found out that you are calling
createCluster(builder, 4) method. This method only initializes the EmbeddedCacheManagers
and doesn't start default caches as well as doesn't wait till the cluster is
formed.
If you'll modify the call to createCluster(builder, 4) to createClusteredCaches(4,
builder) , then the tests will work as expected by returning the value 100 for all M/R
tasks.
Regards,
Anna.
Issues w/ M/R test cases if cache are not explicitly started on all
nodes
-------------------------------------------------------------------------
Key: ISPN-2835
URL:
https://issues.jboss.org/browse/ISPN-2835
Project: Infinispan
Issue Type: Feature Request
Components: Core API, Distributed Execution and Map/Reduce
Reporter: Ray Tsang
Assignee: Galder ZamarreƱo
Fix For: 5.2.2.Final, 5.3.0.Alpha1, 5.3.0.Final
Attachments: mr-test-src.zip
I ran into some issues while using M/R. The gist of the issue I was seeing is that:
Start a cluster of Embedded Caches, like 4 nodes
Put in 100 elements
Run a simple M/R job to count the number of keys
If I run the M/R job using the node I'm inserting elements into as coordinator - the
result is 100
But if I run the M/R job using a different node as coordinator, the result is less than
100
More interestingly, I can pause for 5 seconds and run the M/R jobs again, the results are
always less than 100
This behavior doens't occur if I explicitly run cacheManager.getCache() for each of
the nodes...
--
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