elasticsearch Elassandra单节点群集未启动。陷入突变阶段
我有一个单节点Elasandra集群在一个盒子上运行。 夜幕降临。以下是最后一行systemctl状态输出:elasticsearch Elassandra单节点群集未启动。陷入突变阶段,elasticsearch,cassandra,elassandra,elasticsearch,Cassandra,Elassandra,我有一个单节点Elasandra集群在一个盒子上运行。 夜幕降临。以下是最后一行systemctl状态输出: 主进程退出,code=killed,status=6/ABRT 然而,重新启动后,它陷入了突变阶段,日志(/var/log/cassandra/system.log)中反复出现类似的行: 2020-09-14 12:53:38,048 TRACE [MutationStage-31] ElasticSecondaryIndex.java:2158 readCellValue indexe
主进程退出,code=killed,status=6/ABRT
然而,重新启动后,它陷入了突变阶段,日志(/var/log/cassandra/system.log)中反复出现类似的行:
2020-09-14 12:53:38,048 TRACE [MutationStage-31] ElasticSecondaryIndex.java:2158 readCellValue indexer=730313363 name=value kind=REGULAR type=text value={"dw1":{"6":{"total_weight":"72664168.50","total_count":"5979710.00","product_name":"Masala 12g","target_weight":"12","mean_weight":"12.15","th_packed_weight":"71756520.00","ega":"907648.50","ega_per":"1.26"}},"dw2":{"6":{"total_weight":"72654813.00","total_count":"5979710.00","product_name":"Masala 12g","target_weight":"12","mean_weight":"12.15","th_packed_weight":"71756520.00","ega":"898293.00","ega_per":"1.25"}}}
tpstats输出:
Pool Name Active Pending Completed Blocked All time blocked
ReadStage 0 0 0 0 0
MiscStage 0 0 0 0 0
CompactionExecutor 0 0 9 0 0
MutationStage 32 920 5808076 0 0
MemtableReclaimMemory 0 0 8 0 0
GossipStage 0 0 0 0 0
SecondaryIndexManagement 0 0 0 0 0
RequestResponseStage 0 0 0 0 0
ReadRepairStage 0 0 0 0 0
CounterMutationStage 0 0 0 0 0
MigrationStage 0 0 0 0 0
MemtablePostFlush 0 0 8 0 0
PerDiskMemtableFlushWriter_0 0 0 8 0 0
ValidationExecutor 0 0 0 0 0
Sampler 0 0 0 0 0
MemtableFlushWriter 0 0 8 0 0
InternalResponseStage 0 0 0 0 0
ViewMutationStage 0 0 0 0 0
AntiEntropyStage 0 0 0 0 0
CacheCleanupExecutor 0 0 0 0 0
Message type Dropped
READ 0
RANGE_SLICE 0
_TRACE 0
HINT 0
MUTATION 0
COUNTER_MUTATION 0
BATCH_STORE 0
BATCH_REMOVE 0
REQUEST_RESPONSE 0
PAGED_RANGE 0
READ_REPAIR 0
MutationStage下的挂起计数永远不会变为零。这种状态已经存在很长时间了。此群集中没有其他节点,目前也没有写入任何数据。对我来说,您描述的症状表明正在从
commitlog
重播突变
您可以通过以下方式解决此问题:
commitlog/
的内容移动到另一个目录对我来说,你描述的症状表明突变正在从
commitlog
中重演
您可以通过以下方式解决此问题:
commitlog/
的内容移动到另一个目录成功了。上次它在大约24小时内自行修复,没有机会尝试您的解决方案。今天又发生了一次,这就解决了。干杯成功了。上次它在大约24小时内自行修复,没有机会尝试您的解决方案。今天又发生了一次,这就解决了。干杯