Cassandra: node coordinator awaiting replica nodes response

I imported about 4 million rows from CSV using COPY. After 90 minutes, I received the following error, which suggests some problem while waiting for replica nodes. The key space is configured with a replication factor of 1, and there is only one node in the cluster. So why should the coordinator wait for any other node?

Processed 4050000 rows; Write: 624.27 rows/ss
code=1100 [Coordinator node timed out waiting for replica nodes' responses] message="Operation timed out - received only 0 responses." info=

{'received_responses': 0, 'required_responses': 1, 'write_type': 0, 'consistency': 1}
Aborting import at record #4050617. Previously-inserted values still present.
4050671 rows imported in 1 hour, 26 minutes, and 43.649 seconds.

I already saw this question: The node coordinator is confined to waiting for replica nodes in Cassandra Datastax during data insertion

But this does not answer why the coordinator expects replica nodes to be present when the replication coefficient is 1, and this is a cluster of 1 node.

Additional Information:

Node Status

student@cascor:~$ nodetool status
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address    Load       Tokens  Owns    Host ID                               Rack
UN  127.0.0.1  1.64 GB    256     ?       f550e955-00f3-49a4-bc2d-c7f775079359  rack1

Note: Non-system keyspaces don't have the same replication settings, effective ownership information is meaningless

Keyspace Configuration

cqlsh:excelsior> desc keyspace;

CREATE KEYSPACE excelsior WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'}  AND durable_writes = true;
0
1

: 'received_responses': 0, 'required_responses': 1 node, , . . , , , CPU, , node " ", 1 node , . , (write_request_timeout_in_ms) , COPY .

+2

Source: https://habr.com/ru/post/1612709/


All Articles