SOLVED: Turns out that the InterruptedException that was being thrown from
the system shut down was being caught in the code and swallowed. All I did
was add a throw RuntimeException and that seemed to give the right signal to
Ignite to compute the failed process on the first node.
New code looks like this.
// Iterate through all words in the sentence and create
jobs.
for (final String word : "Print words using
runnable".split(" ")) {
// Execute runnable on some node.
exec.submit(new IgniteRunnable() {
public void run() {
System.out.println(">>> ABOUT TO
PRINT SOMETHING");
try {
Thread.sleep(10000);
} catch (InterruptedException e) {
*throw new
RuntimeException(e);*
}
System.out.println(">>> Printing '"
+ word
+ "' on this node
from grid job.");
}
});
}
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Computations-not-fault-tolerant-tp833p856.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
