cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10113) Undroppable messages can be dropped if message queue gets large
Date Tue, 24 Nov 2015 16:16:11 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita updated CASSANDRA-10113:
---------------------------------------
    Component/s: Streaming and Messaging

> Undroppable messages can be dropped if message queue gets large
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-10113
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10113
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.1.10, 2.2.2, 3.0.0 rc2
>
>
> When outgoing messages are queued, OutboundTcpConnection checks the size of backlog,
and [if it gets more than 1024, it drops expired messages silently from the backlog|https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/net/OutboundTcpConnection.java#L150].
> {{expireMessages()}} just checks message's timeout, which can be {{request_timeout_in_ms}}
(10 sec default) for non- read/write message, and does not check if its droppable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message