Jeff Jirsa updated CASSANDRA-11460:
    Resolution: Won't Fix
        Status: Resolved  (was: Awaiting Feedback)

Closing as wont-fix; reopen if you can repro reliably. 

> memory leak
> -----------
>                 Key: CASSANDRA-11460
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11460
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: stone
>            Priority: Critical
>              Labels: proposed-wontfix
>         Attachments: aaa.jpg
> env:
> cassandra3.3
> jdk8
> 8G Ram
> so set
> 1.met same problem about this:
> https://issues.apache.org/jira/browse/CASSANDRA-9549
> I confuse about that this was fixed in release 3.3 according this page:
> https://github.com/apache/cassandra/blob/trunk/CHANGES.txt
> so I change to 3.4,and also have  found this problem again 
> I think this fix should be included in
> can you explain about this?
> 2.our write rate exceed the value that our cassandra env can support,
> but i think it should descrese the write rate,or block.consumer the writed 
> data,keep the memory down,then go on writing,not cause out-of-memory instead.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to