[ https://issues.apache.org/jira/browse/CASSANDRA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961912#comment-16961912 ]
Benedict Elliott Smith commented on CASSANDRA-15375: ---------------------------------------------------- Which version of Cassandra are we discussing here? My preference is to remove the back pressure feature entirely, since it's never really been tested at scale that I know of. In 4.0 we have the capability of pushing the actual internode backpressure back to clients, in a similar manner to [~sumanth.pasupuleti] achieved recently in CASSANDRA-15013 But if that's too contentious, sure, let's clean up our logging :) > back pressure log line is misleading > ------------------------------------ > > Key: CASSANDRA-15375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15375 > Project: Cassandra > Issue Type: Bug > Components: Observability/Logging > Reporter: Jon Haddad > Assignee: Jon Haddad > Priority: Low > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org