cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-685) add backpressure to StorageProxy
Date Tue, 19 Jan 2010 20:06:54 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802445#action_12802445
] 

Jonathan Ellis commented on CASSANDRA-685:
------------------------------------------

Explained backpressure motivation on IRC:

under heavy load each node A will have 2 kinds of traffic to each other node B.  A will have
new commands it needs to send to B, and it will also have replies to commands that B sent
to it.  If B is overloaded, you need to be able to backpressure new commands to it, while
allowing replies to it to go through.  Replies create virtually no extra load and it makes
the clients much happier.


> add backpressure to StorageProxy
> --------------------------------
>
>                 Key: CASSANDRA-685
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-685
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: 0001-impose-stage-queue-limit-of-2048-operations-which-shou.txt,
0002-make-TcpConnection.write-throw-WriteEnqueueException-i.txt
>
>
> Now that we have CASSANDRA-401 and CASSANDRA-488 there is one last piece: we need to
stop the target node from pulling mutations out of MessagingService as fast as it can only
to take up space in the mutation queue and eventually fill up memory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message