[
https://issues.apache.org/jira/browse/CASSANDRA-17768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627265#comment-17627265
]
Aleksey Yeschenko commented on CASSANDRA-17768:
-----------------------------------------------
bq. What's the downside to us reinstating the KeepAliveTask scheduling code
from 4.0 in 4.1 defaulted to on?
Honestly, there is really no downside, it's a tiny message once every 5 minutes
by default. I'd just rather not handle this myself at the moment, and I'm not
sure the issue itself justifies blocking the RC, given relative unimportance
and the relative ease of reinstating at any point, including in a minor.
If we feel strongly that it just cannot wait until 4.1.1 at all, I'll make it
happen, but this isn't as trivial as copy-pasting some 4.0 code back, post
refactor, and testing + committing is going to take some time.
> 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-rc, 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: [email protected]
For additional commands, e-mail: [email protected]
