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 Mon, 11 Jan 2010 23:20:54 GMT

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

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

the first patch makes it so the target node won't OOM and will instead backpressure the control
node.

the second makes it so the control node will notice the backpressure and pass it on (via timeoutexception)
to the thrift client, rather than OOMing itself from continuing to enqueue messages to an
unresponsive target.

> 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.9
>
>         Attachments: 0001-impose-stage-queue-limit-of-4096-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