[
https://issues.apache.org/jira/browse/CASSANDRA-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139102#comment-14139102
]
Sylvain Lebresne commented on CASSANDRA-7951:
---------------------------------------------
I'm not really convinced this is needed either. If your client want to ping the
server, presumably it will do so at a very hight rate, at which point the
amount of CPU required to build a response to the {{OPTIONS}} is really
completely irrelevant. And more importantly, it's probably smarter to actually
do a trivial system table query (or even an actual user query) as on top of
checking the network connection, this also check that your node is roughtly
working correctly.
> 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)
