cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michaël Figuière (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7951) Add a Keep Alive operation to the Native Protocol
Date Thu, 18 Sep 2014 15:52:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139083#comment-14139083
] 

Michaël Figuière commented on CASSANDRA-7951:
---------------------------------------------

Do not underestimate the amount of bureaucracy and lobbying that can be required to have a
firewall setting changed in large organizations, especially if that has to go through the
"security expert" office :)

> 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)

Mime
View raw message