Question

启动维修服务后，它会显示一个百分比，说明当前的维修流程。修复整个群集后，它会再次关闭。

我认为它正在顺利地修复整个群集，永远一次又一次地开始，但似乎＆＃34;完成＆＃34; ...这不是我的期望

我错过了什么吗？

OpsCenter 5.2.0
DSE 4.6.7

编辑：

日志：

2015-09-02 08:33:34+0000 [XX]  INFO: Detected a topology change. The Repair Service will stop now and check the cluster topology every 5 minutes. If the cluster is stable, the Repair Service will start again.
2015-09-02 08:33:34+0000 [XX]  INFO: Stopping Repair Service
2015-09-02 08:48:34+0000 []  INFO: Unhandled error in Deferred:
2015-09-02 08:48:34+0000 [] Unhandled Error
    Traceback (most recent call last):
      File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 361, in callback
        self._startRunCallbacks(result)
      File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 455, in _startRunCallbacks
        self._runCallbacks()
      File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 542, in _runCallbacks
        current.result = callback(current.result, *args, **kw)
      File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 1076, in gotResult
        _inlineCallbacks(r, g, deferred)
    --- <exception caught here> ---
      File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 1020, in _inlineCallbacks
        result = g.send(result)
      File "/usr/lib/python2.7/dist-packages/opscenterd/cluster/Repair.py", line 909, in startRepairService

    opscenterd.cluster.Repair.RepairServiceAlreadyRunning: The Repair Service is already running.

在拓扑更改（添加节点）后，OpsCenter似乎无法再次启动修复服务

Answer 1

您没有遇到维护服务的预期行为，详见文档：

http://docs.datastax.com/en/opscenter/5.2//opsc/online_help/services/repairService.html

我使用opscenter 5.2.0和DSE 4.7.3测试了修复服务，并且它确实表现得很好。完成维修服务后，立即开始新的维修服务。这可以在服务屏幕上的opscenter中看到（在活动中不可见）。

如评论中所述，您应该查看日志并查看您可以找到的“面包屑”。

Cassandra OpsCenter维修服务停止

1 个答案: