问题

在主机删除后，手动群集创建失败。

H

大家好。

再会！！

我有一个问题，需要您的帮助和建议。

1.使用10个节点，但我想配置2个带有5个节点的簇。（由RF3组成）

2.在由10个节点组成的群集中，成功完成了5个节点的去除。

3.然后，针对已删除的5个节点手动完成集群创建。

集群-s 166.103.190.123,166.103.190.124,124,166.103.190.125,166.103.190.126,166.103.190.127

4.集群配置工作中发生的错误
--- 166.103.190.125（向下）开始：似乎该零件在上下重复时没有进展。

Waiting on 166.103.190.124 (Up, ZeusLeader) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector AndPLOSConfigur
等待166.103.190.125（向下）开始：
Waiting on 166.103.190.126 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.127 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine

Waiting on 166.103.190.123 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.124 (Up, ZeusLeader) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector AndPLOSConfigur
等待166.103.190.125（向下）开始：
Waiting on 166.103.190.126 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.127 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine

5.目前，群集销毁已被执行，除“ 166.103.190.125”以外，有4个节点被销毁，但“ 166.103.190.125”并未进行以下操作。

nutanix@ntnx-j302ac65-a-cvm：166.103.190.125：〜$集群销毁
2020-11-11 17:43:43信息Zookeeper_session.py:143集群正在尝试连接到Zookeeper
2020-11-11 17:43:54错误configuration.py:157无法与host_port_list：zk1：9876，zk2：9876，zk3：9876与zookeeper连接
2020-11-11 17:43:54警告集群：2709无法从ZK读取SVM Backplane IPS
2020-11-11 17:43:54信息群集：2716在SVMS Localhost上执行动作销毁
2020-11-11 17:43:54警告Genesis_utils.py:279弃用：使用util.cluster.info.get_node_uuid（）
2020-11-11 17:44:08警告Genesis_utils.py:1218未能到达创世纪起来的节点。重试...（击中Ctrl-C以中止）
2020-11-11 17:44:09警告Genesis_utils.py:1218未能到达创世纪起来的节点。重试...（击中Ctrl-C以中止）
2020-11-11 17:44:10警告Genesis_utils.py:1218未能到达创世纪升起的节点。重试...（击中Ctrl-C以中止）
2020-11-11 17:44:11警告Genesis_utils.py:1218未能到达创世纪启动的节点。重试...（击中Ctrl-C以中止）

6.我重新启动了166.103.190.125节点，但它仍然具有相同的症状。

我不想重新安装CVM，我想手动创建群集。有什么方法可以解决吗？

Hello, All.<\/p>

Good day!!<\/p>

\u00a0<\/p>

I have an issue and need your help and advice.<\/p>

\u00a0<\/p>

1. using 10 nodes, but I want to configure 2 clusters with 5 nodes each. (Composed of RF3)<\/p>

\u00a0<\/p>

2. In a cluster consisting of 10 nodes, the removal of 5 nodes was successfully completed.<\/p>

\u00a0<\/p>

3. Then, cluster creation was done manually for 5 nodes that had been removed.<\/p>

cluster -s 166.103.190.123,166.103.190.124,166.103.190.125,166.103.190.126,166.103.190.127 --skip_discovery create --redundancy_factor=3<\/strong><\/p>

\u00a0<\/p>

4. Errors that occur during cluster configuration work
--- 166.103.190.125 (Down) to start: It seems that the part does not progress as it repeats Up and Down.<\/p>

Waiting on 166.103.190.124 (Up, ZeusLeader) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector AndPLOSConfigur
Waiting on 166.103.190.125 (Down) to start:
Waiting on 166.103.190.126 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.127 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine<\/p>

Waiting on 166.103.190.123 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.124 (Up, ZeusLeader) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector NutanixGuestTools MinervaCollector AndPLOSConfigur
Waiting on 166.103.190.125 (Down) to start:
Waiting on 166.103.190.126 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine
Waiting on 166.103.190.127 (Up) to start: Medusa DynamicRingChanger Pithos Mantle Stargate InsightsDB InsightsDataTransfer Ergon Cerebro Chronos Curator Athena Prism CIM AlertManager Arithmos Catalog Acropolis Uhura SysStatCollector NutanixGuestTools MinervaCVM ClusterConfig APLOS OrganConfig Mercury LaTrim And APLOSEngine<\/p>

5. Currently, cluster destroy has been executed, and 4 nodes except \u2018166.103.190.125\u2019 are destroyed, but \u2018166.103.190.125\u2019 is not proceeding as follows.<\/p>

nutanix@NTNX-J302AC65-A-CVM:166.103.190.125:~$ cluster destroy<\/strong>
2020-11-11 17:43:43 INFO zookeeper_session.py:143 cluster is attempting to connect to Zookeeper
2020-11-11 17:43:54 ERROR configuration.py:157 Could not get Zookeeper connection with host_port_list: zk1:9876,zk2:9876,zk3:9876
2020-11-11 17:43:54 WARNING cluster:2709 Could not read SVM backplane IPs from zk
2020-11-11 17:43:54 INFO cluster:2716 Executing action destroy on SVMs localhost
2020-11-11 17:43:54 WARNING genesis_utils.py:279 Deprecated: use util.cluster.info.get_node_uuid() instead
2020-11-11 17:44:08 WARNING genesis_utils.py:1218 Failed to reach a node where Genesis is up. Retrying... (Hit Ctrl-C to abort)
2020-11-11 17:44:09 WARNING genesis_utils.py:1218 Failed to reach a node where Genesis is up. Retrying... (Hit Ctrl-C to abort)
2020-11-11 17:44:10 WARNING genesis_utils.py:1218 Failed to reach a node where Genesis is up. Retrying... (Hit Ctrl-C to abort)
2020-11-11 17:44:11 WARNING genesis_utils.py:1218 Failed to reach a node where Genesis is up. Retrying... (Hit Ctrl-C to abort)<\/p>

6. I rebooted the 166.103.190.125 node, but it still has the same symptoms.<\/p>

\u00a0<\/p>

I don't want to reinstall cvm, I want to create cluster manually. Is there any way to fix it?<\/p>","quoteUsername":"hotae-72904","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

该主题已关闭以供评论

2个答复

s

你好，hotae

我也有同样的问题，但无法解决。

我认为这是动物园管理员问题。

如果您发生，请帮助我们。

我对每个人都看了回答。

谢谢

Hello, Hotae<\/p>

\u00a0<\/p>

i have a same issue but can not fix.\u00a0<\/p>

I think that it is zookeeper issue.<\/p>

Please help us if you occured.<\/p>

I look foward to everyone reply.<\/p>

\u00a0<\/p>

Thanks\u00a0\u00a0<\/p>","quoteUsername":"SOONJOO","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

n
秩
UserLevel 2
徽章 +2

“未能达到创世纪启动的节点”可能意味着尚未完全尚未完全配置节点。通常，如果它是未配置的，而不是群集的一部分，则只有创世纪和动物园管理器正在运行。这两个服务是稳定的，如果您输入“群集状态”，则应表明未配置群集。

因此，应该是正确不合格的问题。我们确实有一个内部KB，因此，如果您想沿着该路线走下去，打开支持案例会更容易。（KB 3436）

The \u201cFailed to reach a node where Genesis is up\u201d could mean that node is not completely unconfigured yet. Typically if it is unconfigured and not part of a cluster, only genesis and zookeeper is running. These two services are stable and if you enter \u201ccluster status\u201d, it should show that the cluster is not configured.<\/p>

So it should be a matter of properly unconfiguring it. We do have an internal KB for it, so it would be easier to open a Support case if you wanted to go down that route. (KB 3436)<\/p>

\u00a0<\/p>","quoteUsername":"nim","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu