Cassandra SOLR滚动升级 [英] Cassandra SOLR Rolling Upgrade
问题描述
我们有一个12个节点的集群，6个DSE-SOLR和6个DSE-Cassandra。从3.0升级到3.1时，我们注意到通过SOLR接口的请求被破坏，直到所有节点都已升级。
We have a cluster of 12 nodes, 6 DSE-SOLR and 6 DSE-Cassandra. When upgrading from 3.0 to 3.1 we noticed that requests through the SOLR interface were broken until all nodes had been upgraded.
- 从3.1升级到3.2时，此限制是否仍然存在？
- 在升级过程中，有没有注意事项？
- 在升级路径文件中，它会启用旧的gossip协议，直到所有节点
推荐答案
Russ，
在升级期间运行查询时会收到什么错误？是以下之一吗？ http://www.datastax.com/docs/datastax_enterprise3.1/upgrade/version_3_1_0 位于solr部分的预期错误？
What errors are you getting when running a query during an upgrade? Is it one of the following? http://www.datastax.com/docs/datastax_enterprise3.1/upgrade/version_3_1_0 located in the solr section of expected errors?
从3.1升级到3.2时，此限制是否仍然存在？
Is this limitation still present when upgrading from 3.1 to 3.2?
我没有一个我知道。
进行升级时是否有任何疑问？
只是这里提到的2： http://www.datastax.com/docs/datastax_enterprise3.2/upgrade/version_3_2_0#dse-upgrade-version3-2-0
- 启用旧的gossip协议
- 更改dse_system键空间以使用Everywhere复制策略
在升级路径文档中，它说要启用旧的gossip协议，直到所有节点都已升级，这是每DC还是整个集群？
In the upgrade path docs it says to enable the old gossip protocol until all nodes have been upgraded, is this per DC or for the entire cluster?
集群范围，如果您不临时启用旧的gossip协议，3.2上的新节点将无法与节点在3.1上，反之亦然，这可能导致一些节点看不到集群的其余部分。记得在升级完成后，再从所有节点的cassandra-env.sh中删除JVM_OPTS =$ JVM_OPTS -Denable-old-dse-state = true。
Cluster wide, if you do not temporarily enable the old gossip protocol, the new nodes on 3.2 will not be able to talk to the nodes on 3.1 and vice versa which can lead to some nodes not seeing the rest of the cluster. Remember to remove JVM_OPTS="$JVM_OPTS -Denable-old-dse-state=true" from your cassandra-env.sh on all your nodes once you've upgraded and do another rolling restart.
Ham
这篇关于Cassandra SOLR滚动升级的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
