[
https://issues.apache.org/jira/browse/CASSANDRA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105780#comment-17105780
]
Jordan West commented on CASSANDRA-15375:
-----------------------------------------
While I don't totally agree with your bar for what constitutes an official
public API, my biggest concern was that since we weren't deprecating it, if
there was a user of it, there would be an exception when their configuration
was read on startup. Looking closer at your patch, it does look like this has
been accounted for by indeed marking the fields {{@Deprecated}} in {{Config}}
(as an aside I also agree with the comment that we should note them as such in
cassandra.yaml). So while they will take no effect, they won't harm anyone who
had it set in their config either.
> Remove BackPressureStrategy
> ---------------------------
>
> Key: CASSANDRA-15375
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15375
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client, Observability/Logging
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Low
> Fix For: 4.0
>
>
> This is odd:
> {{INFO [main] 2019-10-25 10:33:07,985 DatabaseDescriptor.java:803 -
> Back-pressure is disabled with strategy
> org.apache.cassandra.net.RateBasedBackPressure\{high_ratio=0.9, factor=5,
> flow=FAST}.}}
> When I saw that, I wasn't sure if back pressure was actually disabled, or if
> I was really using {{RateBasedBackPressure.}}
> This should change to output either:
> {{Back-pressure is disabled}}
> {{or}}
> {{Back-pressure is enabled with strategy
> org.apache.cassandra.net.RateBasedBackPressure\{high_ratio=0.9, factor=5,
> flow=FAST}.}}{{}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
