5, 2014 3:34 AM
To: user@cassandra.apache.org
Subject: CQLSSTableWriter memory leak
I am using Cassandra's CQLSSTableWriter to import a large amount of data into
Cassandra. When I use CQLSSTableWriter to write to a table with compound
primary key, the memory consumption keeps growing
50,000,000 rows to a single partition! My, that IS
ambitious.
-- Jack Krupansky
From:Xu Zhongxing
Sent: Thursday, June 5, 2014 3:34 AM
To:user@cassandra.apache.org
Subject: CQLSSTableWriter memory leak
I am using Cassandra's CQLSSTableWriter to import a large amount of data into
Cassandra. When
I am using Cassandra's CQLSSTableWriter to import a large amount of data into
Cassandra. When I use CQLSSTableWriter to write to a table with compound
primary key, the memory consumption keeps growing. The GC of JVM cannot collect
any used memory. When writing to tables with no compound primary
: Thursday, June 5, 2014 3:34 AM
To: user@cassandra.apache.org
Subject: CQLSSTableWriter memory leak
I am using Cassandra's CQLSSTableWriter to import a large amount of data into
Cassandra. When I use CQLSSTableWriter to write to a table with compound
primary key, the memory consumption keeps
@cassandra.apache.org
Subject: CQLSSTableWriter memory leak
I am using Cassandra's CQLSSTableWriter to import a large amount of data into
Cassandra. When I use CQLSSTableWriter to write to a table with compound
primary key, the memory consumption keeps growing. The GC of JVM cannot collect
any
