Question

从Opscenter 5.x升级后> 6.0.8＆gt; 6.1.0＆gt; 6.1.1，我在opscenterd.log中看到了很多错误和警告，如下所示。我正在使用DSE 4.8.10。我打开了维修服务，这似乎按预期工作。但我在日志中看到了WARNings。这些都需要关注吗？

2017-06-27 01:00:00,356 [local] ERROR: The best practice rule 'Tombstone count' has failed. (MainThread)
2017-06-27 01:00:00,358 [local] ERROR: The best practice rule 'Wide partitions' has failed. (MainThread)
2017-06-27 01:00:00,451 [local] ERROR: The best practice rule 'Secondary indexes cardinality' has failed. (MainThread)
2017-06-27 13:10:11,672 [opscenterd]  WARN: Unknown request 54688d7f-7c5f-4bcb-bc4d-07b7a0a79c3c (running {'started': 1498569009, 'details': u'Repair session f260e7b0-5b39-11e7-87cf-612516369059 for range (1042910172352712044,1065269862139026652] finished', 'details-type': None}) (MainThread)
2017-06-27 13:12:40,885 [opscenterd]  WARN: Unknown request 341c9bc9-1c00-4771-aa64-27206ad4152a (running {'started': 1498569160, 'details': u'Repair session 4c3d5c50-5b3a-11e7-87cf-612516369059 for range (-1555782662812296764,-1538702344225528661] finished', 'details-type': None}) (MainThread)

Answer 1

OpsCenter警告Cassandra节点上无法识别的修复会话。他们可能是被挂断的会议;在Cassandra 2.1.x及更早版本中有许多与此相关的门票：

您可以尝试通过StorageSession mbean上的JMX调用forceTerminateAllRepairSessions来清理这些会话。或者，在群集上滚动重启应该可以解决问题。

无论如何，OpsCenter的维修服务将正常运行。

启动修复服务后opscenterd.log中的错误

1 个答案: