You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by GabryWu <wu...@qq.com> on 2020/05/19 03:37:18 UTC
回复: bind to random port for master & worker
Monitoring can retrieve port information from zookeeper.
I'm not familiar with k8s, so don't know whether there's problem
------------------ 原始邮件 ------------------
发件人: "Hemin Wen"<wenhemin@apache.org>;
发送时间: 2020年5月19日(星期二) 上午10:55
收件人: "dev"<dev@dolphinscheduler.apache.org>;
主题: Re: bind to random port for master & worker
IF random port, Monitoring configuration or k8s configuration may be a
problem.
--------------------
Apache DolphinScheduler Commtter
Hemin Wen 温合民
wenhemin@apache.org
--------------------
GabryWu <wu_shao_jie@qq.com> 于2020年5月19日周二 上午7:20写道:
> random port is better,I think
>
>
>
> ---Original---
> From: "lidong dai"<dailidong66@gmail.com&gt;
> Date: Mon, May 18, 2020 22:50 PM
> To: "dev"<dev@dolphinscheduler.apache.org&gt;;
> Cc: "我的QQ邮箱"<wu_shao_jie@qq.com&gt;;
> Subject: Re: bind to random port for master &amp; worker
>
>
> I think we can choose to use another port when current port has already
> been in use by other program. how do you think?
>
>
>
>
> &nbsp;&nbsp;
> Best Regards
> ---------------
> DolphinScheduler(Incubator) PPMC
> Lidong Dai 代立冬
> dailidong66@gmail.com
> ---------------
>
>
>
>
>
>
> GabryWu <wu_shao_jie@qq.com&gt; 于2020年5月13日周三 上午10:24写道:
>
> hi ,all ,for now the workers and masters will bing to a fixed port .
> I think we need to replace it with random port, and store the current
> port number&amp;nbsp;
> to zookeeper through heartbeat report.
> Do you have any suggestions?
Re: bind to random port for master & worker
Posted by Hemin Wen <we...@apache.org>.
Services in the container need to provide services externally through port
mapping.
Random port, Can't be configured.
--------------------
DolphinScheduler(Incubator) Commtter
Hemin Wen 温合民
wenhemin@apache.org
--------------------
GabryWu <wu...@qq.com> 于2020年5月19日周二 上午11:37写道:
> Monitoring can retrieve port information from zookeeper.
> I'm not familiar with k8s, so don't know whether there's problem
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "Hemin Wen"<wenhemin@apache.org>;
> 发送时间: 2020年5月19日(星期二) 上午10:55
> 收件人: "dev"<dev@dolphinscheduler.apache.org>;
>
> 主题: Re: bind to random port for master & worker
>
>
>
> IF random port, Monitoring configuration or k8s configuration may be a
> problem.
>
>
> --------------------
> Apache DolphinScheduler Commtter
> Hemin Wen 温合民
> wenhemin@apache.org
> --------------------
>
>
> GabryWu <wu_shao_jie@qq.com> 于2020年5月19日周二 上午7:20写道:
>
> > random port is better,I think
> >
> >
> >
> > ---Original---
> > From: "lidong dai"<dailidong66@gmail.com&gt;
> > Date: Mon, May 18, 2020 22:50 PM
> > To: "dev"<dev@dolphinscheduler.apache.org&gt;;
> > Cc: "我的QQ邮箱"<wu_shao_jie@qq.com&gt;;
> > Subject: Re: bind to random port for master &amp; worker
> >
> >
> > I think we can choose to use another port when current port has
> already
> > been in use by other program. how do you think?
> >
> >
> >
> >
> > &nbsp;&nbsp;
> > Best Regards
> > ---------------
> > DolphinScheduler(Incubator) PPMC
> > Lidong Dai 代立冬
> > dailidong66@gmail.com
> > ---------------
> >
> >
> >
> >
> >
> >
> > GabryWu <wu_shao_jie@qq.com&gt; 于2020年5月13日周三 上午10:24写道:
> >
> > hi ,all ,for now the workers and masters will bing to a fixed port .
> > I think we need to replace it with random port, and store the
> current
> > port number&amp;nbsp;
> > to zookeeper through heartbeat report.
> > Do you have any suggestions?