[
https://issues.apache.org/jira/browse/CASSANDRA-15013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881793#comment-16881793
]
Benedict commented on CASSANDRA-15013:
--------------------------------------
[~jjirsa] has just pointed out that we are seeing _double_ the throughput of
reads (I hadn't carefully looked at all the graphs), which very likely explains
the increase in CPU
It would be nice to perform a run with fixed throughput at a rate trunk can
manage, so we can get directly comparable results. But this is a _huge_ win,
nice work!
(If we can grab flame graphs anyway, there'd be no harm and it would be nice to
take a look to confirm nothing unexpected)
> 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,
> perftest_blockedthreads.png, perftest_connections_count.png,
> perftest_cpu_usage.png, perftest_heap_usage.png,
> perftest_readlatency_99th.png, perftest_readlatency_avg.png,
> perftest_readops.png, perftest_writelatency_99th.png,
> perftest_writelatency_avg.png, perftest_writeops.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]
