[ https://issues.apache.org/jira/browse/CASSANDRA-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138981#comment-13138981 ]
Stu Hood commented on CASSANDRA-3005: ------------------------------------- (sidenote: we should consider counting dropped messages on the sending side the same way we count them on the receiving side: in the dropped message counts in MessagingService. Alternatively, it might be good to count in both locations) > OutboundTcpConnection's sending queue grows unboundedly without any > backpressure logic > -------------------------------------------------------------------------------------- > > Key: CASSANDRA-3005 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3005 > Project: Cassandra > Issue Type: Improvement > Reporter: Melvin Wang > Assignee: Melvin Wang > Attachments: 3005-v3.txt, c3005-v2, c3005-v4, c3005.patch > > > OutboundTcpConnection's sending queue unconditionally queues up the request > and process them in sequence. Thinking about tagging the message coming in > with timestamp and drop them before actually sending it if the message stays > in the queue for too long, which is defined by the message's own time out > value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira