ave problems like
>>> this where we'd restart the master process, it won't be listening on 7077
>>> for some time, but the worker process is trying to connect and by the time
>>> the master is up the worker has given up...
>>>
>>>
>>&
gt;>
>>> Check whether the name can be resolved in the /etc/hosts file (or DNS)
>>> of the worker
>>>
>>>
>>>
>>> (the same btw applies for the Node where you run the driver app – all
>>> other nodes must be able to resolve its name)
DNS) of
>> the worker
>>
>>
>>
>> (the same btw applies for the Node where you run the driver app – all
>> other nodes must be able to resolve its name)
>>
>>
>>
>> *From:* Stephen Boesch [mailto:java...@gmail.com]
>> *Sent:* Wednesda
t; *Sent:* Wednesday, May 20, 2015 10:07 AM
> *To:* user
> *Subject:* Intermittent difficulties for Worker to contact Master on same
> machine in standalone
>
>
>
>
>
> What conditions would cause the following delays / failure for a
> standalone machine/cluster to h
AM
To: user
Subject: Intermittent difficulties for Worker to contact Master on same machine
in standalone
What conditions would cause the following delays / failure for a standalone
machine/cluster to have the Worker contact the Master?
15/05/20 02:02:53 INFO WorkerWebUI: Started
What conditions would cause the following delays / failure for a standalone
machine/cluster to have the Worker contact the Master?
15/05/20 02:02:53 INFO WorkerWebUI: Started WorkerWebUI at
http://10.0.0.3:8081
15/05/20 02:02:53 INFO Worker: Connecting to master
akka.tcp://sparkMaster@mellyrn.loca
