No, all keyspaces that we created do not have secondary indexes. So probably
the settings 'memtable_flush_queue_size' is not relevant?
It may be.
If you had a lot a CF's and cassandra tried to flush more than
memtable_flush_queue_size at once.
one would think that the compaction would
Hi Aaron, thank you for comment.
It may be.
If you had a lot a CF's and cassandra tried to flush more than
memtable_flush_queue_size at once.
We created 6 keyspaces where maximum CF in a keyspace is 5 CF. The setting
'memtable_flush_queue_size' is using the default value which is 4.
What version are you on ?
HTimedOutException is logged for all the nodes.
TimedOutException happens when less than CL replica nodes respond to the
coordinator in time.
You could get the error from all nodes in your cluster if the 3 nodes that
store the key are having problems.
Hi Aaron, thank you for your reply. Please read inline comment.
On Tue, Sep 18, 2012 at 7:36 PM, aaron morton aa...@thelastpickle.comwrote:
What version are you on ?
cassandra version 1.0.8
HTimedOutException is logged for all the nodes.
TimedOutException happens when less than CL
Hello,
A context to our environment, we have a clusters of 9 nodes with a few
keyspaces. The client write to the cluster with consistency level of one to
a keyspace in the cluster with a replication factor of 3. The hector client
is configured such that all the nodes in cluster is specified and
