Monitoring can retrieve port information from zookeeper. I'm not familiar with k8s, so don't know whether there's problem
------------------ 原始邮件 ------------------ 发件人: "Hemin Wen"<[email protected]>; 发送时间: 2020年5月19日(星期二) 上午10:55 收件人: "dev"<[email protected]>; 主题: 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 温合民 [email protected] -------------------- GabryWu <[email protected]> 于2020年5月19日周二 上午7:20写道： > random port is better，I think > > > > ---Original--- > From: "lidong dai"<[email protected]&gt; > Date: Mon, May 18, 2020 22:50 PM > To: "dev"<[email protected]&gt;; > Cc: "我的QQ邮箱"<[email protected]&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 代立冬 > [email protected] > --------------- > > > > > > > GabryWu <[email protected]&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?
