Did you go through the executor logs completely? Futures timed out
exception can occur mostly when one of the task/job spend way too much time
and fails to respond, this happens when there's a GC pause or memory
overhead.
Thanks
Best Regards
On Tue, Dec 1, 2015 at 12:09 AM, Spark Newbie
Hi Spark users,
I have been seeing this issue where receivers enter a "stuck" state after
it encounters a the following exception "Error in block pushing thread -
java.util.concurrent.TimeoutException: Futures timed out".
I am running the application on spark-1.4.1 and using kinesis-asl-1.4.
