Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED8789A21 for ; Tue, 16 Dec 2014 15:07:13 +0000 (UTC) Received: (qmail 57675 invoked by uid 500); 16 Dec 2014 15:07:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 57640 invoked by uid 500); 16 Dec 2014 15:07:13 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 57628 invoked by uid 99); 16 Dec 2014 15:07:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 15:07:13 +0000 Date: Tue, 16 Dec 2014 15:07:13 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8477) CMS GC can not recycle objects MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248344#comment-14248344 ] Jonathan Ellis commented on CASSANDRA-8477: ------------------------------------------- bq. for 2.0/2.1, I'm not sure there is much to do except maybe extend the tombstone_warning_threshold to include range tombstones too Yes, we should do that. > CMS GC can not recycle objects > ------------------------------ > > Key: CASSANDRA-8477 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8477 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: 2.1.1 or 2.1.2-SNAPSHOT(after CASSANDRA-8459 resolved) > Reporter: Philo Yang > Assignee: Sylvain Lebresne > Attachments: cassandra.yaml, histo.txt, jstack.txt, log1.txt, log2.txt, system.log, system.log.2014-12-15_1226 > > > I have a trouble in my cluster that CMS full gc can not reduce the size of old gen. Days ago I post this problem to the maillist, people think it will be solved by tuning the gc setting, however it doesn't work for me. > Then I saw a similar bug in CASSANDRA-8447, but [~benedict] think it is not related. With the jstack on https://gist.github.com/yangzhe1991/755ea2a10520be1fe59a, [~benedict] find a bug and resolved it in CASSANDRA-8459. So I build a latest version on 2.1 branch and run the SNAPSHOT version on the nodes with gc trouble. > However, there is still the gc issue. So I think opening a new tick and post more information is a good idea. Thanks for helping me. -- This message was sent by Atlassian JIRA (v6.3.4#6332)