[
https://issues.apache.org/jira/browse/CASSANDRA-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137029#comment-14137029
]
Michaël Figuière commented on CASSANDRA-7951:
---------------------------------------------
A way to do it with the current specification of the protocol is to send an
{{OPTIONS}} message, but this force the server to answer with a more complex
response and it seems that we have enough room to spend an opcode on this
specific requirement...
> Add a Keep Alive operation to the Native Protocol
> -------------------------------------------------
>
> Key: CASSANDRA-7951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7951
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Michaël Figuière
> Priority: Minor
> Labels: protocolv4
>
> Socket level keep-alive option doesn't seem to bring a strong enough
> guarantee that the connection won't be dropped as some OS or Firewall level
> settings might force some different behavior.
> To simplify things and bring the strong guarantee on this point that users
> expect, it would be interesting to add a {{NOOP}} or {{KEEPALIVE}}.
> Note that we could also turn it into a {{HEARTBEAT}} operation that would
> expect a response from the server to allow client to regularly probe for
> Cassandra node health in situation where the queries traffic is too low to
> bring this probing implicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
