related to -ib--.db
>
> Run a repair after deletion
>
>
> On Thu, Jan 30, 2014 at 10:17 PM, Francisco Nogueira Calmon Sobral
> wrote:
> Ok. I'll try this idea with one sstable. But, should I delete all the files
> associated with it? I mean, there is a differenc
Rahul Menon wrote:
>
> > Francisco,
> >
> > the sstables with *-ib-* is something that was from a previous version of
> > c*. The *-ib-* naming convention started at c* 1.2.1 but 1.2.10 onwards im
> > sure it has the *-ic-* convention. You could try running a nodetool
> &
arted at c* 1.2.1 but 1.2.10 onwards im sure
> it has the *-ic-* convention. You could try running a nodetool sstableupgrade
> which should ideally upgrade the sstables with the *-ib-* to *-ic-*.
>
> Rahul
>
> On Wed, Jan 29, 2014 at 12:55 AM, Francisco Nogueira Calmon Sobral
&g
Dear experts,
We are facing a annoying problem in our cluster.
We have 9 amazon extra large linux nodes, running Cassandra 1.2.11.
The short story is that after moving the data from one cluster to another,
we've been unable to run 'nodetool repair'. It get stuck due to a
CorruptSSTableExceptio
Hi, Ross.
We had the same problem under the same version of Cassandra. We opted to copy
ALL the stables from the old cluster to each new node, then run nodetool
refresh. The missing rows have appeared after this procedure.
Best regards,
Francisco.
On Nov 27, 2013, at 7:49 PM, Ross Black wro
We also run into the same problem when trying to load data from a 8 node
cluster (C* 1.2.1, Vnodes and same rack) into a 9 node cluster (C* 1.2.11,
Vnodes and different racks) using sstableloader.
We observed that a Key that clearly belonged to 3 nodes (using nodetool
getendpoints) has not been
Hi, all!
I've performed a test in my cluster, regarding the sstableloader behaviour on
counter column families. The test cluster has 3 nodes running Cassandra 1.2.3
with RF=3. The machine that sstableloader run had Cassandra 1.2.11.
The counter column family had only one row, so I chose one nod
Hi all!
According to the DataStax blog
(http://www.datastax.com/dev/blog/modern-hinted-handoff), once the dead node is
up again, all the nodes that have hints to the node start sending information.
However, it is written that they verify at every 10 minutes if there were timed
out hints.
Do t
;
>
> 2013/9/2 Francisco Nogueira Calmon Sobral
> We had some problems when using secondary indexes because of three issues:
>
> - The query is a Range Query, which means that it is slow.
> - There is an open bug regarding the use of row cache for secondary indexes
> (CASSA
We had some problems when using secondary indexes because of three issues:
- The query is a Range Query, which means that it is slow.
- There is an open bug regarding the use of row cache for secondary indexes
(CASSANDRA-4973)
- The cardinality of our secondary key was very low (this was bad)
We
heers
>
> -
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 27/04/2013, at 12:27 AM, Francisco Nogueira Calmon Sobral
> wrote:
>
>> Hi all!
>>
>> We are
Hi all!
We are using Cassandra 1.2.1 with a 8 node cluster running at Amazon. We
started with 6 nodes and added the 2 later. When performing some reads in
Cassandra, we observed a high difference between gets using the primary key and
gets using secondary indexes:
[default@Sessions] get Users
I am using the same version and observed something similar.
I've added a new node, but the instructions from Datastax did not work for me.
Then I ran "nodetool rebuild" on the new node. After finished this command, it
contained two times the load of the other nodes. Even when I ran "nodetool
cl
13 matches
Mail list logo
