You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@spark.apache.org by sunday2000 <23...@qq.com> on 2016/05/17 01:54:07 UTC
Why spark 1.6.1 master can not monitor and start a auto stop worker?
Hi,
A client woker stoppped, and has this error message, do u know why this happen?
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:21 ERROR Worker: Worker registration failed: Duplicate worker ID
回复： Why spark 1.6.1 master can not monitor and start a auto stop worker?
Posted by sunday2000 <23...@qq.com>.
I Use $SPARK_HOME/sbin/start-slave.sh client10, get this error:
org.apache.spark.deploy.worker.Worker running as process 5490. Stop it first.
------------------ 原始邮件 ------------------
发件人: "Ted Yu";<yu...@gmail.com>;
发送时间: 2016年5月17日(星期二) 上午10:22
收件人: "sunday2000"<23...@qq.com>;
抄送: "user"<us...@spark.apache.org>;
主题: Re: Why spark 1.6.1 master can not monitor and start a auto stop worker?
I guess 2.0 would be released before Spark Summit.
On Mon, May 16, 2016 at 7:19 PM, sunday2000 <23...@qq.com> wrote:
Hi,
I found the bug status is : Solved, then when will release the solved version?
------------------ 原始邮件 ------------------
发件人: "Ted Yu";<yu...@gmail.com>;
发送时间: 2016年5月17日(星期二) 上午9:58
收件人: "sunday2000"<23...@qq.com>;
抄送: "user"<us...@spark.apache.org>;
主题: Re: Why spark 1.6.1 master can not monitor and start a auto stop worker?
Please take a look at this JIRA:
[SPARK-13604][CORE] Sync worker's state after registering with master
On Mon, May 16, 2016 at 6:54 PM, sunday2000 <23...@qq.com> wrote:
Hi,
A client woker stoppped, and has this error message, do u know why this happen?
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:21 ERROR Worker: Worker registration failed: Duplicate worker ID
Re: Why spark 1.6.1 master can not monitor and start a auto stop worker?
Posted by Ted Yu <yu...@gmail.com>.
I guess 2.0 would be released before Spark Summit.
On Mon, May 16, 2016 at 7:19 PM, sunday2000 <23...@qq.com> wrote:
> Hi,
> I found the bug status is : Solved, then when will release the solved
> version?
>
>
> ------------------ 原始邮件 ------------------
> *发件人:* "Ted Yu";<yu...@gmail.com>;
> *发送时间:* 2016年5月17日(星期二) 上午9:58
> *收件人:* "sunday2000"<23...@qq.com>;
> *抄送:* "user"<us...@spark.apache.org>;
> *主题:* Re: Why spark 1.6.1 master can not monitor and start a auto stop
> worker?
>
> Please take a look at this JIRA:
>
> [SPARK-13604][CORE] Sync worker's state after registering with master
>
> On Mon, May 16, 2016 at 6:54 PM, sunday2000 <23...@qq.com> wrote:
>
>> Hi,
>>
>> A client woker stoppped, and has this error message, do u know why this
>> happen?
>>
>> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
>> with the master, since there is an attempt scheduled already.
>> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
>> requested this worker to reconnect.
>> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
>> with the master, since there is an attempt scheduled already.
>> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
>> requested this worker to reconnect.
>> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
>> with the master, since there is an attempt scheduled already.
>> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
>> requested this worker to reconnect.
>> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
>> with the master, since there is an attempt scheduled already.
>> 16/05/17 03:42:21 ERROR Worker: Worker registration failed: Duplicate
>> worker ID
>>
>
>
回复： Why spark 1.6.1 master can not monitor and start a auto stop worker?
Posted by sunday2000 <23...@qq.com>.
Hi,
I found the bug status is : Solved, then when will release the solved version?
------------------ 原始邮件 ------------------
发件人: "Ted Yu";<yu...@gmail.com>;
发送时间: 2016年5月17日(星期二) 上午9:58
收件人: "sunday2000"<23...@qq.com>;
抄送: "user"<us...@spark.apache.org>;
主题: Re: Why spark 1.6.1 master can not monitor and start a auto stop worker?
Please take a look at this JIRA:
[SPARK-13604][CORE] Sync worker's state after registering with master
On Mon, May 16, 2016 at 6:54 PM, sunday2000 <23...@qq.com> wrote:
Hi,
A client woker stoppped, and has this error message, do u know why this happen?
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077 requested this worker to reconnect.
16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register with the master, since there is an attempt scheduled already.
16/05/17 03:42:21 ERROR Worker: Worker registration failed: Duplicate worker ID
Re: Why spark 1.6.1 master can not monitor and start a auto stop worker?
Posted by Ted Yu <yu...@gmail.com>.
Please take a look at this JIRA:
[SPARK-13604][CORE] Sync worker's state after registering with master
On Mon, May 16, 2016 at 6:54 PM, sunday2000 <23...@qq.com> wrote:
> Hi,
>
> A client woker stoppped, and has this error message, do u know why this
> happen?
>
> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
> with the master, since there is an attempt scheduled already.
> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
> requested this worker to reconnect.
> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
> with the master, since there is an attempt scheduled already.
> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
> requested this worker to reconnect.
> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
> with the master, since there is an attempt scheduled already.
> 16/05/17 03:42:20 INFO Worker: Master with url spark://master:7077
> requested this worker to reconnect.
> 16/05/17 03:42:20 INFO Worker: Not spawning another attempt to register
> with the master, since there is an attempt scheduled already.
> 16/05/17 03:42:21 ERROR Worker: Worker registration failed: Duplicate
> worker ID
>