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 67EEC10AD5 for ; Wed, 7 Aug 2013 10:28:51 +0000 (UTC) Received: (qmail 96060 invoked by uid 500); 7 Aug 2013 10:28:51 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95866 invoked by uid 500); 7 Aug 2013 10:28:49 -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 95854 invoked by uid 99); 7 Aug 2013 10:28:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Aug 2013 10:28:48 +0000 Date: Wed, 7 Aug 2013 10:28:48 +0000 (UTC) From: "Alex Zarutin (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-5555) Allow sstableloader to handle a larger number of files 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-5555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731855#comment-13731855 ] Alex Zarutin commented on CASSANDRA-5555: ----------------------------------------- Verified the fix on latest Cassandra 1.2 with about 42 thousands of SSTable files using the "how to reproduce" steps already attached. During the processing the files, I did not see big change in memory consumption and CPU utilization. Running the process with 256M of the memory as Java -Xmx, the real usage stayed around 140M during the entire process. Suggest to resolve this issue, unless we really want to test it on thousand of huge files - much bigger that 1M that we used in this test. > Allow sstableloader to handle a larger number of files > ------------------------------------------------------ > > Key: CASSANDRA-5555 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5555 > Project: Cassandra > Issue Type: Improvement > Components: Core, Tools > Reporter: Tyler Hobbs > Assignee: Tyler Hobbs > Fix For: 1.2.7, 2.0 beta 2 > > Attachments: 5555-01.txt, 5555-02.txt, 5555-2.txt, 5555-fix-heap-and-streaming-1.2.patch, 5555-fix-heap-and-streaming-1.2-v2.patch, 5555-fix-heap-and-streaming-trunk.patch, cass_5555_pic_8.png, CASSANDRA-5555.txt, CASSANDRA-5555.txt, CASSANDRA-5555.txt > > > With the default heap size, sstableloader will OOM when there are roughly 25k files in the directory to load. It's easy to reach this number of files in a single LCS column family. > By avoiding creating all SSTableReaders up front in SSTableLoader, we should be able to increase the number of files that sstableloader can handle considerably. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira