I have no clue why this is happening, even though we have the appropriate
future implementation -
List<Future<Void>> futures = executor.invokeAll(callables);
// Go look for exceptions here, really
for (Future<Void> future : futures) {
if (!future.isDone()) {
future.get();
}
}
I tried looking for exceptions; there aren't any in this case. For about
every 1 in 5 times, it causes this issue of quitting even when a lot threads
are still running. Any pointers?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Possible-multi-thread-issue-in-AbstractDifferenceRecommenderEvaluator-tp1571411p1571579.html
Sent from the Mahout User List mailing list archive at Nabble.com.
