[
https://issues.apache.org/jira/browse/CASSANDRA-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769310#comment-16769310
]
Benedict edited comment on CASSANDRA-15013 at 2/15/19 1:30 PM:
---------------------------------------------------------------
I guess maybe let's wait and see how much more complicated it would be? You're
right that the {{OptionsMessage}} should be sufficient for supplying the
option, and I think the complicated bit is going to be negotiating safely with
the {{requestExecutor}} when we should start and stop reading.
If it turns out to be super challenging, by all means let's make it a 4.0-only
follow-up, but if (as I suspect) it's nominally extra work, I think it's better
to tie up the work while there's pressure to do so. WDYT?
was (Author: benedict):
I guess maybe let's wait and see how much more complicated it would be? You're
right that the {{OptionsMessage}} should be sufficient for supplying the
option, and I think the complicated bit is going to be negotiating safely with
the {{requestExecutor}} when we should start and stop reading.
If it turns out to be super challenging, by all means let's make it a 4.0-only
follow-up, but if (as I suspect) it's nominally extra work, I think it's better
to tie up the work while there's pressure to do so.
> 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: Major
> 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]
