Hello Benedict and Edward,
Thank you very much for the comments.
I think the batch parameter is useful when doing some transactional
processing on C* where we need atomicity and higher durability.
Anyways, I think it is not working as expected at least in the latest
versions in 2.1 and 2.2.
So,
That is the maximum length of time that queries may be batched together
for, not the minimum. If there is a break in the flow of queries for the
commit log, it will commit those outstanding immediately. It will anyway
commit in clusters of commit log file size (default 32Mb).
I know the
I mentioned during my Cassandra.yaml presentation at the summit that I
never saw anyone use these settings. Things off by default are typically
not highly not covered well by tests. It sounds like it is not working.
Quick suggestion: go back in time maybe to a version like 1.2.X or 0.7 and
see if
Hello Satoshi and the community,
I am also using commitlog_sync for durability, but I have never
modified commitlog_sync_batch_window_in_ms parameter yet,
so I wondered if it is working or not.
As Satoshi said, I also changed commitlog_sync_batch_window_in_ms (to
1) and restarted C* and
Hi, all.
I have a question about "batch" commit log sync behavior with C* version
2.2.8.
Here's what I have done:
* set commitlog_sync to the "batch" mode as follows:
> commitlog_sync: batch
> commitlog_sync_batch_window_in_ms: 1
* ran a script which inserts the data to a table
* prepared
