# Keepalive connections in cassandra connector

**URL:** <https://discuss.konghq.com/t/keepalive-connections-in-cassandra-connector/6646>\
**Category:** General\
**Created:** [July 1, 2020, 8:58pm UTC](https://discuss.konghq.com/t/keepalive-connections-in-cassandra-connector/6646 "2020-07-01T20:58:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abhishekvrshny](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/abhishekvrshny/32/1613_2.png) [@Abhishekvrshny](https://discuss.konghq.com/u/Abhishekvrshny)\
**Post date:** [July 1, 2020, 8:58pm UTC](https://discuss.konghq.com/t/keepalive-connections-in-cassandra-connector/6646/1 "2020-07-01T20:58:54Z")

</div>

Does kong establish `keepalive` connections to cassandra? I see these logs when kong boots up

```auto
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,

```auto
 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?

---

<div class="post-metadata">

**Author:** ![thibaultcha](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thibaultcha/32/340_2.png) [@thibaultcha](https://discuss.konghq.com/u/thibaultcha)\
**Post date:** [September 7, 2020, 7:48pm UTC](https://discuss.konghq.com/t/keepalive-connections-in-cassandra-connector/6646/2 "2020-09-07T19:48:00Z")

</div>

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.