The db times out upon dropping a keyspace

ScyllaDB
1

Whenever I try to drop a keyspace, the operation rarely gets executed at the db times out.
I always get this error-

OperationTimedOut: errors={'172.17.0.2': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=172.17.0.2

Why is this happening?

2

It’s impossible to know without more context.
Are there related messages in system log?
What is the timeouts configuration?
What kind of disks are you using?
Is auto_snapshot enabled?

3

Are there related messages in system log?

Not sure, what that means???

What is the timeouts configuration?

default 15s

What kind of disks are you using?

My PC, default 256 ssd 1 tb hdd for storage. Its in dev mode

Is auto_snapshot enabled?

Nope I couldnt find the default option true in the config file.

4

Are there related messages in system log?

Not sure, what that means???

Scylla prints all kinds of messages to a system log.
I’m not sure how you installed it.
Anything under /var/log/?

What is the timeouts configuration?

default 15s

What kind of disks are you using?

My PC, default 256 ssd 1 tb hdd for storage. Its in dev mode

Is auto_snapshot enabled?

Nope I couldnt find the default option true in the config file.

Then actually it is enabled by default.
This means that scylla takes a snapshot of the dropped table(s) / keyspace before deleting it to be on the safe side.
It is possible that this takes too long with a magnetic drive.
Try setting auto_snapshot: false in scylla.yaml and restart scylla for it to take effect.
Then retry dropping the keyspace / table.

5

Its installed via docker-compose on a linux system. Deepin to be precise. v4.something ig. Nothing relatedd to scylla under /var/logs tho at first glance, everything seems related to the internal FS.

Try setting auto_snapshot: false in scylla.yaml and restart scylla for it to take effect.
Then retry dropping the keyspace / table.

aaah yes I saw that in the docs but I couldnt find that in my default scylla.yaml file. So I figured by default it mustve been false. Thats 1 thing ive gotta do for sure yep

Thanks for the input, ill try to fix this once & for all