[
https://issues.apache.org/jira/browse/CASSANDRA-17768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570950#comment-17570950
]
Paulo Motta commented on CASSANDRA-17768:
-----------------------------------------
I think the necessity for this is severely reduced if we use a single
connection for both inbound/outbound streaming traffic, but that was not the
case when the feature was added, so one connection could remain idle for long
periods while the other side was active, what caused connection resets due to
badly configured firewalls/networks.
>From [https://docs.oracle.com/cd/E19787-01/820-2559/using-24/index.html:]
{quote}Where possible, in addition to using the TCP keep-alive mechanism, the
client application also must perform its own periodic keep-alive at its level.
*The TCP keep-alive mechanism is not perfect in all possible boundary cases.*
{quote}
> streaming_keep_alive_period is not used after [CASSANDRA-16927] CEP-10 Phase
> 1: Refactor Streaming
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17768
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Streaming and Messaging
> Reporter: Ekaterina Dimitrova
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> While working on another ticket I noticed that after [CASSANDRA-16927] CEP-10
> Phase 1: Refactor Streaming
> streaming_keep_alive_period is not used anymore, except to print it in error
> message
> [here|https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/streaming/StreamSession.java#L689]
> If the property should not be used anymore, we need to deprecate it and fix
> the error message as it is misleading.
> [~benedict] , [~samt] , [~aleksey] , can you, please, check and take care of
> this one as authors of that patch?
> Thank you in advance!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
