You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (Jira)" <ji...@apache.org> on 2020/04/07 13:11:00 UTC
[jira] [Commented] (CASSANDRA-15607) Incorrect Outcome returned
when acquiring capacity for incoming message
[ https://issues.apache.org/jira/browse/CASSANDRA-15607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077220#comment-17077220 ]
Aleksey Yeschenko commented on CASSANDRA-15607:
-----------------------------------------------
Good catch. A one-line fix [here|https://github.com/iamaleksey/cassandra/commits/15607-4.0].
> Incorrect Outcome returned when acquiring capacity for incoming message
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15607
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15607
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Sam Tunnicliffe
> Assignee: Aleksey Yeschenko
> Priority: Normal
>
> When acquiring capacity to process an inbound internode message, a failure to allocate from the endpoint-specific reserve returns the wrong {{Outcome}}. This means we only ever register with {{globalWaitQueue}}, although this probably doesn't actually ever get detected as the global and endpoint queues are always signalled together.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org