Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 67901 invoked from network); 26 Jul 2010 06:52:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Jul 2010 06:52:06 -0000 Received: (qmail 61811 invoked by uid 500); 26 Jul 2010 06:52:05 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 61737 invoked by uid 500); 26 Jul 2010 06:52:04 -0000 Mailing-List: contact dev-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 dev@cassandra.apache.org Received: (qmail 61729 invoked by uid 99); 26 Jul 2010 06:52:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 06:52:03 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.216.172] (HELO mail-qy0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 06:51:59 +0000 Received: by qyk1 with SMTP id 1so1730290qyk.10 for ; Sun, 25 Jul 2010 23:51:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.73.73 with SMTP id p9mr5781574qaj.320.1280127097845; Sun, 25 Jul 2010 23:51:37 -0700 (PDT) Received: by 10.229.189.75 with HTTP; Sun, 25 Jul 2010 23:51:37 -0700 (PDT) In-Reply-To: References: Date: Mon, 26 Jul 2010 08:51:37 +0200 Message-ID: Subject: Re: Cassandra and Lucene From: Michelan Arendse To: dev@cassandra.apache.org Content-Type: multipart/alternative; boundary=00c09f7b2a4aef4025048c44d003 --00c09f7b2a4aef4025048c44d003 Content-Type: text/plain; charset=ISO-8859-1 I have 2 seeds in my cluster, with a replication of 2. I am using cassandra 0.6.2. It keeps running out of memory so I don't know if there are some memory leaks. This is what is in the log: at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) ... 2 more ERROR [GC inspection] 2010-07-22 18:41:57,157 CassandraDaemon.java (line 78) Fatal exception in thread Thread[GC inspection,5,main] java.lang.OutOfMemoryError: Java heap space at java.util.AbstractList.iterator(AbstractList.java:273) at org.apache.cassandra.service.GCInspector.logIntervalGCStats(GCInspector.java:82) at org.apache.cassandra.service.GCInspector.access$000(GCInspector.java:38) at org.apache.cassandra.service.GCInspector$1.run(GCInspector.java:74) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) On Mon, Jul 26, 2010 at 2:14 AM, Aaron Morton wrote: > You may need to provide a some more information. What's the cluster > configuration, what version, what's in the logs etc. > > Aaron > > > On 24 Jul, 2010,at 03:40 AM, Michelan Arendse > wrote: > > Hi > > I have recently started working on Cassandra as I need to make a distribute > Lucene index and found that Lucandra was the best for this. Since then I > have configured everything and it's working ok. > > Now the problem comes in when I need to write this Lucene index to > Cassandra > or convert it so that Cassandra can read it. The test index is 32 gigs and > i > find that Cassandra times out alot. > > What happens can't Cassandra take that load? Please any help will be great. > > Kind Regards, > > --00c09f7b2a4aef4025048c44d003--