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
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
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
10 matches
Mail list logo
