[
https://issues.apache.org/jira/browse/CASSANDRA-11097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876952#comment-16876952
]
Andy Tolbert commented on CASSANDRA-11097:
------------------------------------------
Might already be aware of this but some of the datastax drivers send a
'heartbeat' {{OPTIONS}} message every 30 seconds to keep connections active as
we've seen some environments disconnect idle connections as soon as 5 minutes
([doc|https://docs.datastax.com/en/developer/java-driver/3.7/manual/pooling/#heartbeat]).
Is the expectation that to make use of this feature that client side
heartbeats should be disabled?
> Idle session timeout for secure environments
> --------------------------------------------
>
> Key: CASSANDRA-11097
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11097
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/CQL
> Reporter: Jeff Jirsa
> Assignee: Alex Petrov
> Priority: Low
> Labels: lhf, ponies
>
> A thread on the user list pointed out that some use cases may prefer to have
> a database disconnect sessions after some idle timeout. An example would be
> an administrator who connected via ssh+cqlsh and then walked away.
> Disconnecting that user and forcing it to re-authenticate could protect
> against unauthorized access.
> It seems like it may be possible to do this using a netty
> {{IdleStateHandler}} in a way that's low risk and perhaps off by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
