You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sumanth Pasupuleti (JIRA)" <ji...@apache.org> on 2019/02/07 17:23:00 UTC
[jira] [Created] (CASSANDRA-15013) Message Flusher queue can grow
unbounded, potentially running JVM out of memory
Sumanth Pasupuleti created CASSANDRA-15013:
----------------------------------------------
Summary: 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
Fix For: 4.0, 3.0.x, 3.11.x
Attachments: 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org