Keepalive connections in cassandra connector

1

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?

1 Like
2

Hi,

Connections to Cassandra are already part of a keepalive pool during runtime processing of the Gateway. It is only in the init context that connections are not being kept-alive.

2 Likes