Does kong establish
keepalive connections to cassandra? I see these logs when kong boots up
no support for cosockets in this context, falling back to LuaSocket, context: init_worker_by_lua*
I assume it doesn’t because the documentation of lua-resty-socket also mentions,
When falling back to LuaSocket, it provides you with shims for cosocket-only functions such as `getreusedtimes` , `setkeepalive` etc...
Is there a way to enable keepalive connections to Cassandra?