Hi Carlo,
Can you post steps to reproduce over on
https://issues.apache.org/jira/browse/CASSANDRA-3819 ? We have tried
and failed to cause this problem.
On Thu, Jan 26, 2012 at 6:24 AM, Carlo Pires wrote:
> I found out this is related to schema change. Happens *every time* I create
> drop and n
ssandra-user-incubator-apache-org.3065146.n2.nabble.com/Cannot-start-cassandra-node-anymore-tp7150978p7240588.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
finition/CF names, so we dropped the
> key space and recreated with new definition.
>
> Huy
>
>
>
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cannot-start-cassandra-node-anymore-tp7150978p72
, but later we had to change some definition/CF names, so we dropped the
key space and recreated with new definition.
Huy
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cannot-start-cassandra-node-anymore-tp7150978p7227283.html
Sent from the
On Thu, Jan 26, 2012 at 1:24 PM, Carlo Pires wrote:
> I found out this is related to schema change. Happens *every time* I create
> drop and new CF with composite types. As workaround I:
Would you mind opening a ticket on JIRA
(https://issues.apache.org/jira/browse/CASSANDRA) with the stack trace
I'm not in production yet. As exercise, stopped all nodes when this error
occurred and I could not start any node again.
why would you ever want to stop all nodes together?
On Thu, Jan 26, 2012 at 1:24 PM, Carlo Pires wrote:
> I found out this is related to schema change. Happens *every time* I create
> drop and new CF with composite types. As workaround I:
>
> * never stop all nodes together
>
> To stop a node:
>
I found out this is related to schema change. Happens *every time* I create
drop and new CF with composite types. As workaround I:
* never stop all nodes together
To stop a node:
* repair and compact a node before stopping it
* stop and start it again
* if it started fine good if not, remove all
service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:356)
> at
> org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107)
> Exception encountered during startup: null
>
>
>
> Thanks!
>
> Huy
>
>
> --
> View thi
(too much to quote)
Looks to me like this should be fixable by removing hints from the
node in question (I don't remember whether this is a bug that's been
identified and fixed or not).
I may be wrong because I'm just basing this on a quick look at the
stack trace but it seems to me there are hin
If you have the time turn logging up to DEBUG and start again, it will log
where it failed. Put the logs aside incase there is a bug there.
To get things running again: Move the commit log segment out of the directory
and try the restart. Then run a repair from the node.
Have you made any re
Hi,
I can't start a node of my cluster. Could someone help me to catch the
problem?
Using: debian with cassandra 1.0.6.
root@carlo-laptop:/etc/cassandra# cat /var/log/cassandra/output.log
INFO 13:46:00,596 JVM vendor/version: Java HotSpot(TM) 64-Bit Server
VM/1.6.0_26
INFO 13:46:00,600 Heap si
12 matches
Mail list logo
