storage.cql.executor-service
Hello: storage.cql.executor-service.enabled property is removed in 1.0.0. iirc the current documentation contains the recommendation, that for production scenarios it should be disabled and let the driver handle the queries. Is there a change?
1 Reply
Yes, that option won’t be necessary anymore CQL layer in 1.0.0 was completely re-written to leverage Async approach instead. Thus, the pool won’t be used for IO operations, but it will be used for data deserialisation only. Be default the pool size will be set to CPUs * 2 which is considered to be the best possible amount of threads for non blocking operations for standard commodity processors (where vThreads is typically 1 or 2 per unit).
It’s not advised changing storage.cql.executor-service configurations in 1.0.0 unless you know what you are doing.
Notice the option is MASKABLE. Meaning that if you used a big core pool size before, it’s advised to change that to the value “-1”.