[
https://issues.apache.org/jira/browse/CASSANDRA-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807994#comment-16807994
]
Benedict commented on CASSANDRA-15013:
--------------------------------------
{quote}In other words, we would never discard a message if the client chose to
go with backpressure option
{quote}
+1
{quote}I propose cutting a separate ticket for that work, and keeping the scope
limited for this current ticket
{quote}
How about a middle ground: we implement the per-endpoint (IP address) limit
(which would be easily generalised to incorporate an application identifier) in
this patch, so that the logical behaviour of the message control flow isn't
really revisited, we just have to change the inputs and introduce any client
API changes in the follow-up patch?
I personally have a preference for trying to get all of the logical semantics
settled in the first patch, though I'm not deeply wed to that.
> Message Flusher queue can grow unbounded, potentially running JVM out of
> memory
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-15013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15013
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0, 3.0.x, 3.11.x
>
> Attachments: BlockedEpollEventLoopFromHeapDump.png,
> BlockedEpollEventLoopFromThreadDump.png, RequestExecutorQueueFull.png, heap
> dump showing each ImmediateFlusher taking upto 600MB.png
>
>
> This is a follow-up ticket out of CASSANDRA-14855, to make the Flusher queue
> bounded, since, in the current state, items get added to the queue without
> any checks on queue size, nor with any checks on netty outbound buffer to
> check the isWritable state.
> We are seeing this issue hit our production 3.0 clusters quite often.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
