You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2010/07/12 03:33:54 UTC

[jira] Updated: (CASSANDRA-685) add backpressure to StorageProxy

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

Matthew F. Dennis updated CASSANDRA-685:
----------------------------------------

    Attachment: trunk-685.txt

trunk-685.txt tags incoming requests with a timestamp.  When the request is pulled from the queue to be processed, it's timestamp is checked against the RPC_TIMEOUT and discarded if needed.

Recovery is throttled by tracking the futures for the submitted tasks and waiting until they're finished in blocks of MAX_OUTSTANDING_REPLAY_COUNT (currently 1024, could probably be much larger).

> 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: Matthew F. Dennis
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: 0001-impose-stage-queue-limit-of-2048-operations-which-shou.txt, 0002-make-TcpConnection.write-throw-WriteEnqueueException-i.txt, trunk-685.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.