Hi Jeff,
Great! We'll roll back for now, thanks for letting me know.
Conan
On 11 May 2012 10:18, Jeff Williams wrote:
> Conan,
>
> Good to see I'm not alone in this! I just set up a fresh test cluster. I
> first did a fresh install of 1.1.0 and was able to replicate the issue. I
> then did a
Conan,
Good to see I'm not alone in this! I just set up a fresh test cluster. I first
did a fresh install of 1.1.0 and was able to replicate the issue. I then did a
fresh install using 1.0.10 and didn't see the issue. So it looks like rolling
back to 1.0.10 could be the answer for now.
Jeff
O
Hi,
OK we're pretty sure we dropped and re-created the keyspace before
restarting the Cassandra nodes during some testing (we've been migrating to
a new cluster). The keyspace was created via the cli:
create keyspace m7
with placement_strategy = 'NetworkTopologyStrategy'
and strategy_options
Hi Aaron,
Thanks for getting back to me! Yes, I believe our keyspace was created
prior to 1.1, and I think I also understand why you're asking that, having
found this:
https://issues.apache.org/jira/browse/CASSANDRA-4219
Here's our startup log:
https://gist.github.com/2654155
There isn't much
Was this a schema that was created prior to 1.1 ?
What process are you using to create the schema ?
Can you share the logs from system startup ? Up until it logs "Listening for
thrift clients". (if they are long please link to them)
Cheers
-
Aaron Morton
Freelance Developer
@a
Sorry, forgot to mention we're running Cassandra 1.1.
Conan
On 8 May 2012 17:51, Conan Cook wrote:
> Hi Cassandra Folk,
>
> We've experienced a problem a couple of times where Cassandra nodes lose a
> keyspace after a restart. We've restarted 2 out of 3 nodes, and they have
> both experienced
