Cassandra clustername不匹配 [英] Cassandra clustername mismatch

问题描述

我正在尝试向名为ClusterA的现有集群添加单个节点。
在引导此节点之前，它运行单个节点cassandra集群称为测试与旧版本0.7.4。 ClusterA正在运行0.7.5，我已经升级了要添加到0.7.5的节点。我正确配置yaml，但当我运行Cassandra我被垃圾邮件与以下：

  INFO 20：04：24,262日志初始化
 INFO 20：04：24,275堆大小：5156896768/5156896768 
信息20：04：24,276未找到JNA。本机方法将被禁用。 
 INFO 20：04：24,284从文件加载设置：/usr/local/bin/apache-cassandra-0.7.5/conf/cassandra.yaml 
信息20：04：24,380 DiskAccessMode'auto'确定为mmap，indexAccessMode为mmap 
 INFO 20：04：24,511创建新的commitlog段/var/lib/cassandra/commitlog/CommitLog-1306267464511.log 
信息20：04：24,525无法检测到任何本地存储中的模式定义。 
 INFO 20：04：24,525在数据目录中找到表数据。考虑使用JMX调用org.apache.cassandra.service.StorageService.loadSchemaFromYaml（）。 
 INFO 20：04：24,535找不到commitlog文件;跳过重放
信息20：04：24,553升级到0.7。清除提示如果有任何。旧提示将被创建快照。 
 INFO 20：04：24,556 Cassandra版本：0.7.5 
信息20：04：24,556 Thrift API版本：19.4.0 
信息20：04：24,556加载持久性环状态
 INFO 20：04：24,558启动服务器gossip 
 INFO 20：04：24,588排队Memtable-LocationInfo @ 1048095360（233字节，4操作）的刷新
信息20：04：24,589写Memtable- @ 1048095360（233字节，4个操作）
 INFO 20：04：24,794完成刷新/var/lib/cassandra/data/system/LocationInfo-f-1-Data.db（341字节）
 INFO 20：04：24,822加入：获​​取负载信息
 INFO 20：04：24,823睡眠90000 ms等待负载信息... 
 WARN 20：04：24,885 ClusterName与/10.44.2.58不匹配测试！ = ClusterA 
 WARN 20：04：24,886 ClusterName与/10.44.2.58不匹配Test！= ClusterA 
 WARN 20：04：24,886 ClusterName与/10.44.2.58不匹配Test！= ClusterA 
 WARN 20 ：04：24,886 ClusterName与/10.44.2.58不匹配Test！= ClusterA 
 WARN 20：04：24,887 ClusterName与/10.44.2.58不匹配Test！= ClusterA 
  

这个IP在新的yaml中不存在。这是我之前尝试实现的一个旧配置，但我不试图集群与这个ip在所有。
我试图删除所有的存储，db文件和旧的配置，但它仍然检测到一个旧的种子IP不知何故。

我发现很奇怪，

在数据目录中找到表格数据...

任何人都可以告诉我在启动过程中还有什么问题吗？我需要更改/删除/删除此IP才能离开？

感谢。

解决方案

请参阅 http://wiki.apache.org/cassandra/FAQ #clustername_mismatch ，其中包含：

为了防止操作错误，Cassandra
存储集群的名称它的
系统表如果你需要重命名一个
集群为某种原因，它是安全的
删除system / LocationInfo *后
强制压缩所有
如果你在配置文件中指定了节点的
标记，或者如果
不关心保存节点的
标记例如在单节点
集群中。）

I'm trying to add a single node to an already existing cluster called ClusterA. Prior to bootstrapping this node, it was running a single node cassandra cluster called "Test" with an older version 0.7.4. ClusterA is running 0.7.5 and I've upgraded the node to be added to 0.7.5 as well. I configured the yaml properly, but when I run Cassandra I get spammed with the following:

INFO 20:04:24,262 Logging initialized
 INFO 20:04:24,275 Heap size: 5156896768/5156896768
 INFO 20:04:24,276 JNA not found. Native methods will be disabled.
 INFO 20:04:24,284 Loading settings from file:/usr/local/bin/apache-cassandra-0.7.5/conf/cassandra.yaml
 INFO 20:04:24,380 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
 INFO 20:04:24,511 Creating new commitlog segment /var/lib/cassandra/commitlog/CommitLog-1306267464511.log
 INFO 20:04:24,525 Couldn't detect any schema definitions in local storage.
 INFO 20:04:24,525 Found table data in data directories. Consider using JMX to call org.apache.cassandra.service.StorageService.loadSchemaFromYaml().
 INFO 20:04:24,535 No commitlog files found; skipping replay
 INFO 20:04:24,553 Upgrading to 0.7. Purging hints if there are any. Old hints will be snapshotted.
 INFO 20:04:24,556 Cassandra version: 0.7.5
 INFO 20:04:24,556 Thrift API version: 19.4.0
 INFO 20:04:24,556 Loading persisted ring state
 INFO 20:04:24,558 Starting up server gossip
 INFO 20:04:24,588 Enqueuing flush of Memtable-LocationInfo@1048095360(233 bytes, 4 operations)
 INFO 20:04:24,589 Writing Memtable-LocationInfo@1048095360(233 bytes, 4 operations)
 INFO 20:04:24,794 Completed flushing /var/lib/cassandra/data/system/LocationInfo-f-1-Data.db (341 bytes)
 INFO 20:04:24,822 Joining: getting load information
 INFO 20:04:24,823 Sleeping 90000 ms to wait for load information...
 WARN 20:04:24,885 ClusterName mismatch from /10.44.2.58 Test !=ClusterA
 WARN 20:04:24,886 ClusterName mismatch from /10.44.2.58 Test !=ClusterA
 WARN 20:04:24,886 ClusterName mismatch from /10.44.2.58 Test !=ClusterA
 WARN 20:04:24,886 ClusterName mismatch from /10.44.2.58 Test !=ClusterA
 WARN 20:04:24,887 ClusterName mismatch from /10.44.2.58 Test !=ClusterA

This IP does not exist anywhere in the new yaml. It's an old config I tried implementing some time ago, but I'm not trying to cluster with this ip at all. I tried deleting all the storage, db files, and old configs, but it still detects an old seed IP somehow.

I find it weird that this gets logged when I confirmed that the data directory is empty.

Found table data in data directories...

Can anyone tell me how this is still coming up during start up? What do I need to change/remove/delete for this IP to go away?

Thanks.

解决方案

See http://wiki.apache.org/cassandra/FAQ#clustername_mismatch , which says:

"To prevent operator errors, Cassandra stores the name of the cluster in its system table. If you need to rename a cluster for some reason, it is safe to remove system/LocationInfo* after forcing a compaction on all ColumnFamilies (with the old cluster name) if you've specified the node's token in the config file, or if you don't care about preserving the node's token (for instance in single node clusters.) "

这篇关于Cassandra clustername不匹配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！