Help understanding an exception that produces multiple stack traces

Hi, Below is an error I got while using Spark 1.6.1 on AWS EMR 4.5. I am trying to understand what exactly this error is telling me. I see the exception, then what I am assuming is the plan being executed the resulting stack trace, followed by two caused by stack traces, and then a driver

unsubscribe

unsubscribe