Well, the schema versions are still apparently consistent across the nodes
that are actually part of the ring (according to "describe cluster"). I
could just upgrade, but I'm trying to hold out for datastax enterprise or at
least community and would rather not have to upgrade to 0.8.7 and then 1.x
On Fri, Oct 14, 2011 at 2:36 PM, Eric Czech wrote:
> Thanks again. I have truncated certain cf's recently and the cli didn't
> complain and listings of the cf rows return nothing after truncation. Is
> that data not actually deleted?
Hmm, well, now I'm confused because if 3259 is your problem t
Thanks again. I have truncated certain cf's recently and the cli didn't
complain and listings of the cf rows return nothing after truncation. Is
that data not actually deleted?
On Fri, Oct 14, 2011 at 1:28 PM, Brandon Williams wrote:
> On Thu, Oct 13, 2011 at 11:33 PM, Eric Czech
> wrote:
> >
On Thu, Oct 13, 2011 at 11:33 PM, Eric Czech wrote:
> Thanks Brandon! Out of curiosity, would making schema changes through a
> thrift interface (via hector) be any different? In other words, would using
> hector instead of the cli make schema changes possible without upgrading?
No, but if the
Thanks Brandon! Out of curiosity, would making schema changes through a
thrift interface (via hector) be any different? In other words, would using
hector instead of the cli make schema changes possible without upgrading?
On Thu, Oct 13, 2011 at 8:22 AM, Brandon Williams wrote:
> You're runnin
You're running into https://issues.apache.org/jira/browse/CASSANDRA-3259
Try upgrading and doing a rolling restart.
-Brandon
On Thu, Oct 13, 2011 at 9:11 AM, Eric Czech wrote:
> Nope, there was definitely no intersection of the seed nodes between the two
> clusters so I'm fairly certain that th
Nope, there was definitely no intersection of the seed nodes between the two
clusters so I'm fairly certain that the second cluster found out about the
first through what was in the LocationInfo* system tables. Also, I don't
think that procedure will really help because I don't actually want the
s
Do you have same seed node specified in cass-analysis-1 as cass-1,2,3?
I am thinking that changing the seed node in cass-analysis-2 and
following the directions in
http://wiki.apache.org/cassandra/FAQ#schema_disagreement might solve
the problem. Somone please correct me.
On Thu, Oct 13, 2011 at 12
I don't think that's what I'm after here since the unwanted nodes were
originally assimilated into the cluster with the same initial_token values
as other nodes that were already in the cluster (that have, and still do
have, useful data). I know this is an awkward situation so I'll try to
depict i
Does nodetool removetoken not work?
On Thu, Oct 13, 2011 at 12:59 AM, Eric Czech wrote:
> Not sure if anyone has seen this before but it's really killing me right
> now. Perhaps that was too long of a description of the issue so here's a
> more succinct question -- How do I remove nodes associat
Not sure if anyone has seen this before but it's really killing me right
now. Perhaps that was too long of a description of the issue so here's a
more succinct question -- How do I remove nodes associated with a cluster
that contain no data and have no reason to be associated with the cluster
what
Hi, I'm having what I think is a fairly uncommon schema issue --
My situation is that I had a cluster with 10 nodes and a consistent schema.
Then, in an experiment to setup a second cluster with the same information
(by copying the raw sstables), I left the LocationInfo* sstables in the
system ke
12 matches
Mail list logo
