You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@spark.apache.org by Aseem Bansal <as...@gmail.com> on 2017/03/02 12:04:15 UTC
spark keeps on creating executors and each one fails with
"TransportClient has not yet been set."
Is there a way to find out what is it trying to connect to? I am running my
spark client from within a docker container so I opened up various ports as
per
http://stackoverflow.com/questions/27729010/how-to-configure-apache-spark-random-worker-ports-for-tight-firewalls
after adding all the properties in conf/spark-defaults.conf on my spark
cluster's installation.
In stdout of the executor I can see the following debug
17/03/02 12:01:17 DEBUG UserGroupInformation: PrivilegedActionException
as:root (auth:SIMPLE) cause:org.apache.spark.rpc.RpcTimeoutException:
Cannot receive any reply in 120 seconds. This timeout is controlled by
spark.rpc.askTimeout
What is it trying to connect to?
Re: spark keeps on creating executors and each one fails with
"TransportClient has not yet been set."
Posted by Aseem Bansal <as...@gmail.com>.
Anyone has any idea what could I enable so as to find out what it is trying
to connect to?
On Thu, Mar 2, 2017 at 5:34 PM, Aseem Bansal <as...@gmail.com> wrote:
> Is there a way to find out what is it trying to connect to? I am running
> my spark client from within a docker container so I opened up various ports
> as per http://stackoverflow.com/questions/27729010/how-to-
> configure-apache-spark-random-worker-ports-for-tight-firewalls after
> adding all the properties in conf/spark-defaults.conf on my spark cluster's
> installation.
>
> In stdout of the executor I can see the following debug
>
> 17/03/02 12:01:17 DEBUG UserGroupInformation: PrivilegedActionException
> as:root (auth:SIMPLE) cause:org.apache.spark.rpc.RpcTimeoutException:
> Cannot receive any reply in 120 seconds. This timeout is controlled by
> spark.rpc.askTimeout
>
> What is it trying to connect to?
>