You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could the txeh library be changed so it would split the hostnames into multiple lines, once it reaches 9 hostnames per address (for windows only)?
Or do you think this is for some reason undesirable?
I could dive in and see if I can create a PR - but please confirm this is something you see as a benefit.
https://superuser.com/questions/932112/is-there-a-maximum-number-of-hostname-aliases-per-line-in-a-windows-hosts-file
Kubefwd generate too many aliases hostname in one line as below.
you will get this error when you run ping hadoop-hadoop-yarn-nm-2.nodemanager
Ping request could not find host hadoop-hadoop-yarn-nm-2.nodemanager. Please check the name and try again.
127.1.27.5 hadoop-hadoop-yarn-nm-2.nodemanager hadoop-hadoop-yarn-nm-2-nodemanager hadoop-hadoop-yarn-nm-2.nodemanager.backoffice hadoop-hadoop-yarn-nm-2-nodemanager-backoffice hadoop-hadoop-yarn-nm-2.nodemanager.backoffice.svc hadoop-hadoop-yarn-nm-2-nodemanager-backoffice-svc hadoop-hadoop-yarn-nm-2.nodemanager.backoffice.svc.cluster.local hadoop-hadoop-yarn-nm-2-nodemanager-backoffice-svc-cluster-local hadoop-hadoop-yarn-nm-2.nodemanager.backoffice.arn:aws:eks:us-east-1:882490700787:cluster/ubix-backoffice-cluster hadoop-hadoop-yarn-nm-2-nodemanager-backoffice-arn-aws-eks-us-east-1-882490700787-cluster-ubix-backoffice-cluster hadoop-hadoop-yarn-nm-2.nodemanager.backoffice.svc.arn:aws:eks:us-east-1:882490700787:cluster/ubix-backoffice-cluster hadoop-hadoop-yarn-nm-2-nodemanager-backoffice-svc-arn-aws-eks-us-east-1-882490700787-cluster-ubix-backoffice-cluster hadoop-hadoop-yarn-nm-2.nodemanager.backoffice.svc.cluster.arn:aws:eks:us-east-1:882490700787:cluster/ubix-backoffice-cluster hadoop-hadoop-yarn-nm-2-nodemanager-backoffice-svc-cluster-arn-aws-eks-us-east-1-882490700787-cluster-ubix-backoffice-cluster
The text was updated successfully, but these errors were encountered: