Since I had to upgrade, I have to fix my Perl client to match the new
thrift interface. It'll be later today. Then I can retry.
On 10/27/2010 2:09 PM, Jonathan Ellis wrote:
> Thanks for the clarification.
>
> Are you still seeing the tiny files?
>
> On Wed, Oct 27, 2010 at 4:02 PM, Chip Salzenbe
Thanks for the clarification.
Are you still seeing the tiny files?
On Wed, Oct 27, 2010 at 4:02 PM, Chip Salzenberg wrote:
> That's what you're looking at. Sorry for the confusion. I left all the
> files in place for the upgrade. What I meant was that back when b2 was
> running, "import" was
That's what you're looking at. Sorry for the confusion. I left all the
files in place for the upgrade. What I meant was that back when b2 was
running, "import" was how I had created Standard1 in the first place.
On 10/27/2010 1:54 PM, Jonathan Ellis wrote:
> Sorry, I should have been more clear
Sorry, I should have been more clear: rc1 is upgrade-in-place
compatible with b2, so I would have liked to see what the settings
were before running it through an export/import cycle.
These settings look fine and I doubt you will see bizarre tiny files.
On Wed, Oct 27, 2010 at 2:52 PM, Chip Salze
(moving to user list.)
This sounds like you are GC storming (gcinspector lines in the log
could confirm/refute this) and if I were to guess it would be that the
memtable thresholds picked by b2 are too high. We cut them in half
for rc1 in http://issues.apache.org/jira/browse/CASSANDRA-1641, but a
OK, after upgrading to "apache-cassandra-2010-10-27_12-30-38", here's
what "show keyspaces" says about the relevant keyspace:
ColumnFamily: Standard1
Columns sorted by: org.apache.cassandra.db.marshal.BytesType
Row cache size / save period: 0.0/0
Key cache size / save period:
Not in b2.
On Oct 27, 2010 11:08 AM, "Chip Salzenberg" wrote:
> Are these values available in JMX? If so, which ones are they? I'd
> prefer not to possibly destroy the evidence by upgrading.
>
> On 10/27/2010 6:50 AM, Jonathan Ellis wrote:
>> Connect with the cli and run "show keyspaces." It sound
I set 60 clients to aggressively inserting into a 0.7.0beta2 standard
keyspace overnight. This morning, its heap usage is maxed, it's using
400% CPU (which is a lot less than the box has, so that's OK), and it's
making progress very... very... slowly. The timestamps near the end the
commit logs t
Are these values available in JMX? If so, which ones are they? I'd
prefer not to possibly destroy the evidence by upgrading.
On 10/27/2010 6:50 AM, Jonathan Ellis wrote:
> Connect with the cli and run "show keyspaces." It sounds like
> Cassandra somehow picked ludicrously low memtable threshold
Connect with the cli and run "show keyspaces." It sounds like
Cassandra somehow picked ludicrously low memtable thresholds. There
will be a line like
Memtable thresholds: 0.2953125/63/60
This may not be in the b2 cli, in which case you will need to upgrade
to the nightly from
http://hudso
I should add that the disk free space also changed, so the data
directory had a lot more space available than before:
/dev/cciss/c0d1 2.8T 202M 2.6T 1% /var/lib/cassandra/data
On 10/27/2010 2:17 AM, Chip Salzenberg wrote:
> I recently tested 0.7.0beta2 with good results on a reason
I recently tested 0.7.0beta2 with good results on a reasonably powerful
machine: 8 Xeon cores (16 if you count hyperthreads), 64G memory, and
some nice HP RAID. So far so good. But when I took the same config and
moved it to a basically identical box with 128G of memory, cassandra
started respond
12 matches
Mail list logo
