Re: discuss why we have to replace hostname to ip in the cluster module

+1 from me (stumbled across this while setup of cluster mode in k8s) i think we could leave the resolution or dns caching to the underlying os. Julian Holen Sie sich Outlook für Android From: Xiangdong Huang Sent: Friday, August 27, 2021

Re: discuss why we have to replace hostname to ip in the cluster module

yes, my viewpoint is the same, hostname or IP has no difference for IoTDB. The core is, we need to use node identifiers to distinguish nodes. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Houliang Qi 于2021年8月27日周五 下午1:23写道：

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, Xiangdong > I do not think we will abandon using IP. Either using IP or hostname depends > on users. If they are sure they have a good DNS, they can use DNS; If they > like IP or the nodes do not set the DNS, they can use IP. If they like, they > can also mix-use the hostname and IP

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, > DNS request is an additional cost in nodes communication. I do not think we will abandon using IP. Either using IP or hostname depends on users. If they are sure they have a good DNS, they can use DNS; If they like IP or the nodes do not set the DNS, they can use IP. If they like, they can

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, Xiangdong, Supporting hostname is really a good feature! However, we should consider these cons carefully: 1. DNS request is an additional cost in nodes communication. In cloud environment, the latency may be as large as hundreds of milliseconds(e.g. across available regions), and local

??????discuss why we have to replace hostname to ip in the cluster module

hostname +1 CloudWiseluke.miao ---- ??: "dev"

Re: discuss why we have to replace hostname to ip in the cluster module

hostname +1 HW-Chao Wang <576749...@qq.com.invalid> 于2021年8月26日周四 下午12:12写道： > hostname +1 > > > > ---Original--- > From: "Jialin Qiao" Date: Thu, Aug 26, 2021 09:34 AM > To: "dev" Subject: Re: discuss why we have to replace hostname to ip in the cluster > module > > > Hi, > > hostname +1 > > It

Re: discuss why we have to replace hostname to ip in the cluster module

hostname +1 ---Original--- From: "Jialin Qiao"

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, +1 for hostname. This makes it easier to migrate the data from the failed node and start it at another one. And I don't think it makes much sense to allow users to intermix hostname and IP in seed_nodes in current implementation. Best — Xinyu Tan > 在 2021年8月26日，上午9:34，Jialin Qiao

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, hostname +1 It makes node migration easy. Thanks, — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 Xiangdong Huang 于2021年8月25日周三 下午11:15写道： > Hi, > > Today Julian and I discussed some logic of the cluster module. > Both of us feel it strange that we

discuss why we have to replace hostname to ip in the cluster module

Hi, Today Julian and I discussed some logic of the cluster module. Both of us feel it strange that we replace the hostname to IP before a cluster node starts up. I think it is not a very common way. hostname sometimes is very very helpful. For example, in K8S environment, a node's hostname never