Hi Val, 1) The genral idea is to have a session pool, cause closing and reopening Cassandra session each time is rather expensive operation.
2) I can easily add session expiration timeout as a parameter for Cassandra store. Will create a ticket for this. 3) It could be easily implemented ether, by closing and reopening session every time or just keeping opened sessions forever, but both approaches are bad. It's better to have a session pool and specify rather long session expiration timeout. Igor On Apr 12, 2017 2:48 AM, "Valentin Kulichenko" < [email protected]> wrote: Hi Igor, I recently faced an issue with Cassandra store closing idle connections after some time. While investigating I found that this is caused by SessionPool and its SessionMonitor thread which closes sessions that were not acquired from the pool within 5 minutes. I have several questions regarding this: - What is the general idea behind this? - Why the timeout is not configurable? - Is it possible to add an option to disable this thread completely? Will this have any drawbacks? -Val
