Truncate does a few things (based on version)
truncate takes snapshots
truncate causes a flush
in very old versions truncate causes a schema migration.
In newer versions like cassandra 3.4 you have this knob.
# How long the coordinator should wait for truncates to complete
# (This can be much longer, because unless auto_snapshot is disabled
# we need to flush first so we can snapshot before removing the data.)
truncate_request_timeout_in_ms: 60000
In older versions you can not control when this call will timeout, it is
fairly normal that it does!
On Wed, Sep 28, 2016 at 12:50 PM, George Sigletos <sigle...@textkernel.nl>
wrote:
> Hello,
>
> I keep executing a TRUNCATE command on an empty table and it throws
> OperationTimedOut randomly:
>
> cassandra@cqlsh> truncate test.mytable;
> OperationTimedOut: errors={}, last_host=cassiebeta-01
> cassandra@cqlsh> truncate test.mytable;
> OperationTimedOut: errors={}, last_host=cassiebeta-01
>
> Having a 3 node cluster running 2.1.14. No connectivity problems. Has
> anybody come across the same error?
>
> Thanks,
> George
>
>
