Hello.
It is a question.
The operation of the write operation and the read operation at the consistency
level QUORUM was confirmed in the following
environment.
4-node configuration
・ 10.17.38.204 (seed node)
・ 10.17.38.210
・ 10.17.38.215
・ 10.17.38.218
First, the following command was executed from the node at 10.17.38.204, and
the trace result of the write operation was output.
> CREATE KEYSPACE test1 WITH REPLICATION = {'class': 'NetworkTopologyStrategy',
> 'dc1': 1};
> USE test1;
> CREATE TABLE test_table (id int PRIMARY, col1 int, col2 int);
> TRACING on;
> CONSISTENCY quorum;
> INSERT INTO test_table (id, col1, ccol2) VALUES (2, 2, 2);
As a result, the trace result of the write operation was displayed.
The result was about 40 lines.
Then, the following command was executed and the trace result of the read
operation was output.
> SELECT * FROM test_table;
Then, the trace result was output over 3000 lines.
The results often include the following messages:
・ Enqueuing response to /XX.XX.XX.XX[ReadStage-XX]
・ Read 0 live rows and 0 tombstone cells [ReadStage-XX]
・ Processing response from /XX.XX.XX.XX [ReuestResponseStage-XX]
・ Enqueuing request to /XX.XX.XX.XX [Native-Transport-Requests-XX]
・ RANGE_SLICE message received from /XX.XX.XX.XX [MessagingService-Incoming- /
XX.XX.XX.XX]
・ Sending RANGE_SLICE message to /XX.XX.XX.XX [MessagingService-Outgoing- /
XX.XX.XX.XX-Small]
・ REQUEST_RESPONSE message received from /XX.XX.XX.XX
[MessagingService-Incoming- / XX.XX.XX.XX]
・ Sending REQUST_RESPONSE message to /XX.XX.XX.XX [MessagingService-Outgoing- /
XX.XX.XX.XX-Small]
・ Executing seq scan across 0 sstables for (max (XXXXXXXXXXXXXXXXX), max
(XXXXXXXXXXXXXXXX)] [ReadStage-X]
Is the result correct by executing the TRACING command?
Or is something wrong?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
