11:52 AM, Hannes Schmidt wrote:
> As promised: https://issues.apache.org/jira/browse/CASSANDRA-2654
>
> On Sun, May 15, 2011 at 7:09 AM, Jonathan Ellis wrote:
>> Great debugging work!
>>
>> That workaround sounds like the best alternative to me too.
>>
>> On
As promised: https://issues.apache.org/jira/browse/CASSANDRA-2654
On Sun, May 15, 2011 at 7:09 AM, Jonathan Ellis wrote:
> Great debugging work!
>
> That workaround sounds like the best alternative to me too.
>
> On Sat, May 14, 2011 at 9:46 PM, Hannes Schmidt wrote:
>> O
s to keep the buffer
sizes small in order to reduce the impact of the leak. My patch takes
care of that.
I will post a link to the JIRA issue with the patch shortly.
[1] http://bugs.sun.com/view_bug.do?bug_id=6210541
On Wed, May 4, 2011 at 11:50 AM, Hannes Schmidt wrote:
> Hi,
>
> We are
ve components attached
to them like JNA-allocated memory or direct byte buffers?
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 5 May 2011, at 22:30, Hannes Schmidt wrote
On Thu, May 5, 2011 at 5:56 PM, Benjamin Coverston
wrote:
> How many column families do you have?
We have 10 key spaces, each with 2 column families.
>
> On 5/4/11 12:50 PM, Hannes Schmidt wrote:
>>
>> Hi,
>>
>> We are using Cassandra 0.6.12 in a cluster of 9 n
> I have not looked into smaps before. But it actually seems odd that that
> mmaped Index files are taking up so *little memory*. Are they only a
> few kb on disk?
The sum of the sizes of all *-Index.db files in /var/lib/cassandra is 2924kb.
> Is this a snapshot taken shortly after the process
>
This was my first thought, too. We switched to mmap_index_only and
didn't see any change in behavior. Looking at the smaps file attached
to my original post, one can see that the mmapped index files take up
only a minuscule part of RSS.
On Wed, May 4, 2011 at 11:37 PM, Oleg Anastasyev wrote:
> Pr
Hi,
We are using Cassandra 0.6.12 in a cluster of 9 nodes. Each node is
64-bit, has 4 cores and 4G of RAM and runs on Ubuntu Lucid with the
stock 2.6.32-31-generic kernel. We use the Sun/Oracle JDK.
Here's the problem: The Cassandra process starts up with 1.1G resident
memory (according to top) b
