org.apache.cassandra.concurrent.SEPExecutor

[FS1360472174]

open a ticket on https://issues.apache.org/jira/browse/CASSANDRA-11460,
but nobody give any response.
I found that you are contributor of the SEPExecutor class.so pls help a look.
Summary:
out-of-memory caused by ConcurrentLinkedQueue,i think it is duplicate with bugCASSANDRA-9549,now I understand I make a mistake.
Cassandra9549 caused by Ref.class,and resolved.
my issue caused by SEPExecutor.class
protected final ConcurrentLinkedQueue<FutureTask<?>> tasks = new ConcurrentLinkedQueue<>();

I just see tasks.add method,but not remove operation,so is this one of the reason?

ConcurrentLinkedQueue is non-blocking,and due to my poor cassandra cluster environment.
if it cannot consume as fast as produce,it will also increase and then Out-of-Memory.is that right?