您的Cassandra群集无法部署。副本状态已更改为PERMANENTLY_FAILING。副本不健康连续2次 [英] Your Cassandra cluster failed to deploy. Replica State changed to PERMANENTLY_FAILING. Replica was unhealthy 2 consecutive times

问题描述

我尝试使用Google Compute Engine部署Cassandra丛集，但没有成功。我尝试过几次，错误总是相同的：

I tried to deploy a Cassandra Cluster using Google Compute Engine, no success. I tried several times, the error was always the same:

module: DEPLOYMENT_FAILED
Replica module-1234 failed with status PERMANENTLY_FAILING: Replica State
changed to PERMANENTLY_FAILING. Replica was unhealthy 2 consecutive times.

按照此简短疑难解答指南： https://cloud.google.com/solutions/cassandra/click-to-deploy#troubleshooting ，日志如下：

After following this short troubleshooting guidelines: https://cloud.google.com/solutions/cassandra/click-to-deploy#troubleshooting, the log is the following:

antoniogallo88_gmail_com@cassandra-coord-v8ip:/gagent/metaOutput$ tail $(ls -1tr /gagent/metaOutput/stderr.*.txt | 
tail -n 1)
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
Still waiting for resourceview cassandranode-4da4e to have 3 members ...
[ERROR] resourceview cassandranode-4da4e does not have 3 members after 60 attempts.

你有任何想法如何解决这个问题吗？

Do you have any idea how to fix this?

感谢。

Antonio

推荐答案

您选择的实例类型（以＃为核心），集群成员数超过您正在使用的项目的cpu配额？

Can you check that the instance type you've chosen (in # of cores) and the number of cluster members exceed the cpu quota for the project you're using? Also check the disk capacity value and your overall disk quota.

您可以在Compute Engine> Quotas下的控制台中检查最大允许的磁盘和CPU配额。

You can check max allowable disk and CPU quota in the console under Compute Engine > Quotas.

这个听起来像配额问题，即使控制台没有出现配额错误。

This sounds like a quota issue even though the console is not surfacing a quota error.

另一件你可以做的是创建另一个部署，然后快速切换到实例列表页面，并查找名为Cassandra-coord-foo的实例，该实例是管理磁盘创建的短期实例。如果在部署期间ssh进入该节点并运行以下命令，您可能会看到磁盘或CPU配额警告：

Another thing you can do is create another deployment, then quickly switch over to the instance list page and look for an instance called "Cassandra-coord-foo" which is a short-lived instance that manages disk creation. If you ssh into that node during deployment and run the following command, you may see a disk or CPU quota warning:

tail -f /gagent/metaOutput/*

Chris

这篇关于您的Cassandra群集无法部署。副本状态已更改为PERMANENTLY_FAILING。副本不健康连续2次的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！