[
https://issues.jboss.org/browse/ISPN-4677?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-4677:
---------------------------------------
Hi Vladimir, welcome back!
I'd set a flag somewhere so you can differentiate the two cases; I didn't look in
depth but I guess the problem is to be just testing instanceof: you should shelf some more
context on error so that you can use it then for a better explanation.
Map/Reduce job fails with the wrong explanation on underlying
TimeoutException
------------------------------------------------------------------------------
Key: ISPN-4677
URL:
https://issues.jboss.org/browse/ISPN-4677
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Distributed Execution and Map/Reduce
Affects Versions: 7.0.0.Beta1
Reporter: Sanne Grinovero
Assignee: Vladimir Blagojevic
Fix For: 7.0.0.Beta2
I'm running a task which is throwing the following exception during the Map phase:
{noformat}
org.infinispan.util.concurrent.TimeoutException: Node main-NodeC-22183 timed
out{noformat}
The user facing error however is this very confusing message:
{noformat}org.infinispan.commons.CacheException: java.util.concurrent.ExecutionException:
Map phase executing at main-NodeA-39904 did not complete within 0 sec timeout{noformat}
I have no timeout enabled.
The problem is the instanceof operation on the cause of the error in
org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(Map<KOut,
VOut>): the check on the type only is not good enough.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)