r indexes results in a rollback of the entire
> transaction.
>
> I hope this is helpful to you.
> Tom
>
>
> On Mon, Nov 4, 2013 at 12:20 PM, Thomas Stets wrote:
>
>> What is the best way to manage index tables on update/deletion of the
>> indexed data?
>>
&
What is the best way to manage index tables on update/deletion of the
indexed data?
I have a table containing all kinds of data fora user, i.e. name, address,
contact data, company data etc. Key to this table is the user ID.
I also maintain about a dozen index tables matching my queries, like nam
The Cassandra Operations page
(http://wiki.apache.org/cassandra/Operations) says:
> Unless your application performs no deletes, it is vital that production
clusters run nodetool repair periodically on all nodes in the cluster. The
hard requirement for repair frequency is the value used for GCGrac
On Fri, Sep 21, 2012 at 10:39 AM, aaron morton wrote:
> Have you tried nodetool resetlocalschema on the 1.1.5 ?
>
Yes, I tried a resetlocalschema, and a repair. This didn't change anything.
BTW I could find no documentation, what a resetlocalschema actually does...
regards, Thomas
node behaved just like after the
update: it just forgot my keyspace.
Right now I'm at a loss on how to proceed. Any ideas? I'm pretty sure I can
reproduce the problem,
so if anyone has an idea on what to try, or where to look, I can do some
tests (within limits)
On Wed, Sep 19, 2012 at 4:43 P
On Wed, Sep 19, 2012 at 5:12 PM, Michael Kjellman
wrote:
> Sounds like you are loosing your system keyspace. When you say nothing
> important changed between yaml files do you mean with or without your
> changes?
>
I compared the 1.1.1 cassandra.yaml (with my changes) to the cassandra.yaml
distri
I consistently keep losing my keyspace on upgrading from cassandra 1.1.1 to
1.1.5
I have the same cassandra keyspace on all our staging systems:
development: a 3-node cluster
integration: a 3-node cluster
QS: a 2-node cluster
(productive will be a 4-node cluster, which is as yet not active)
All
