[
https://issues.apache.org/jira/browse/CASSANDRA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840272#action_12840272
]
Ryan King commented on CASSANDRA-685:
-------------------------------------
Would this back-pressure apply to commit log replay? We recently ran into a
situation where a node with very large commit logs managed to OOM itself by
backing up the row mutation stage queue.
> 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.7
>
> 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.
