blocks|key|2890571|text|不知道这是否回答了您所有的问题，但是不断增长的集群和您对客户端ip的知识并不相关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2890572|我有一个5节点集群，但是客户机只知道两个ip地址:种子。因为集群中的每台机器都知道种子(每个cassandra.yaml包含种子ip地址)，如果要添加新机器，客户端将“免费”提供有关新机器的信息。|2890573|想象一个5个节点集群，其中包含以下ips|2890574|192.168.1.1|2890575|192.168.1.2+(种子)|2890576|192.168.1.3|2890577|192.168.1.4+(种子)|2890578|192.168.1.5|2890579|节点.5引导--它将与种子(节点2和节点4)联系，并收到有关整个集群的信息。如果添加一个新的192.168.1.6，它的行为将与.5完全一样，并将指向种子来了解集群情况。在客户端，您不必更改任何内容:您将只知道现在您有6个端点而不是5个端点。|2890580|ps:您不一定要连接到种子，您只需连接到任何节点，因为在接触种子之后，每个节点都知道整个集群拓扑结构。|2890581|pps:您可以选择在您的“客户端已知主机”中放置多少个节点，您也可以将所有5个节点都放入其中，但这不会改变这样一个事实:如果要添加一个节点，则无需在客户端执行任何操作|2890582|你好，卡洛|2890583|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Y|$]]

Don't know if this answer all your questions but the growing cluster and your knowledge of clients ip are not related.

I have a 5 node cluster but the client(s) only knows 2 ip addresses: the seeds. Since each machine of the cluster knows about the seeds (each cassandra.yaml contains the seeds ip address) if new machine will be added information about new one will come "for free" on the client side.

Imagine a 5 nodes cluster with following ips

192.168.1.1

192.168.1.2 (seed)

192.168.1.3

192.168.1.4 (seed)

192.168.1.5

eg: the node .5 boot -- it will contact the seeds (node 2 and 4) and receive back information about the whole cluster. If you add a new 192.168.1.6 will behave exactly like the .5 and will point to the seeds to know the cluster situation. On the client side you don't have to change anything: you will just know that now you have 6 endpoints instead of 5.

ps: you don't have necessarily to connect to the seeds you can just connect to any node of since after having contacted the seeds each node knows the whole cluster topology

pps: it's your choice how many nodes to put in you "client known hosts", you can also put all 5 but this won't change the fact that if one node will be added you don't need to do anything on the client side

Regards,
Carlo

blocks|key|2890598|text|让客户端跟踪每个节点的状态将更容易。智能客户端将通过gos耗散信息跟踪端点状态，后者在新节点出现在集群中时传递它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2890599|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You will have an easier time letting the client track the state of each node. Smart clients will track endpoint state via the gossipinfo, which passes on new nodes as they appear in the cluster.

I've been looking to find how to configure a client to connect to a Cassandra cluster.

Independent of clients like Pelops, Hector, etc, what is the best way to connect to a multi-node Cassandra cluster?

Sending the string IP values works fine, but what about growing number cluster nodes in the future? Is maintaining synchronically ALL IP cluster nodes on client part?

Cassandra big cluster configure the client connection

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我一直在寻找如何配置客户端连接到Cassandra集群。与Pelops、Hector等客户端无关，连接到多节点Cassandra集群的最佳方式是什么？发送字符串IP值可以正常工作，但是将来会有越来越多的集群节点吗？是否同步维护客户端上的所有IP集群节点？

问Cassandra大集群配置客户端连接
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Cassandra大集群配置客户端连接EN