1、Cassandra “Operation timed out - received only 0 responses.”
2020-03-10 21:50:12,532 WARN [elasticsearch[127.0.0.1][bulk][T#5]] BytesRestResponse.java:133 build path: /radar/radar/1583818560000_hb, params: {index=radar, id=1583818560000_hb, type=radar}
org.elasticsearch.transport.RemoteTransportException: [127.0.0.1][127.0.0.1:9300][indices:data/write/bulk[s][p]]
Caused by: org.apache.cassandra.exceptions.WriteTimeoutException: Operation timed out - received only 0 responses.
at org.apache.cassandra.service.AbstractWriteResponseHandler.get(AbstractWriteResponseHandler.java:104)
at org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:641)
at org.apache.cassandra.service.StorageProxy.mutateWithTriggers(StorageProxy.java:864)
at org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:439)
at org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:425)
at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:224)
at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:255)
at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:240)
at org.elasticsearch.cluster.service.ClusterService.process(ClusterService.java:536)
at org.elasticsearch.cluster.service.ClusterService.process(ClusterService.java:514)
at org.elasticsearch.cluster.service.ClusterService.process(ClusterService.java:505)
at org.elassandra.cluster.QueryManager.upsertDocument(QueryManager.java:838)
at org.elassandra.cluster.QueryManager.insertDocument(QueryManager.java:665)
at org.elasticsearch.action.bulk.TransportShardBulkAction.executeIndexRequestOnPrimary(TransportShardBulkAction.java:574)
at org.elasticsearch.action.bulk.TransportShardBulkAction.executeIndexRequest(TransportShardBulkAction.java:148)
at org.elasticsearch.action.bulk.TransportShardBulkAction.executeBulkItemRequest(TransportShardBulkAction.java:246)
at org.elasticsearch.action.bulk.TransportShardBulkAction.performOnPrimary(TransportShardBulkAction.java:129)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:115)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:73)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:1065)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:1043)
at org.elasticsearch.action.support.replication.ReplicationOperation.execute(ReplicationOperation.java:104)
at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.doRun(TransportReplicationAction.java:331)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:297)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:284)
at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:66)
at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:661)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:672)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
修改cassandra.yaml默认值:(待验证)
write_request_timeout_in_ms: 5000
commitlog_segment_size_in_mb: 32
参考:https://issues.apache.org/jira/browse/CASSANDRA-11891
https://dba.stackexchange.com/questions/145069/cassandra-operation-timed-out-received-only-0-responses-during-write