Re: downgrade from 1.1.4 to 1.0.X
On Thu, Sep 20, 2012 at 10:13:49AM +1200, aaron morton wrote: No. They use different minor file versions which are not backwards compatible. Thanks Aaron. Is upgradesstables capable of downgrading the files to 1.0.8? Looking for a way to make this work. Regards, Arend-Jan On 18/09/2012, at 11:18 PM, Arend-Jan Wijtzes ajwyt...@wise-guys.nl wrote: Hi, We are running Cassandra 1.1.4 and like to experiment with Datastax Enterprise which uses 1.0.8. Can we safely downgrade a production cluster or is it incompatible? Any special steps involved? -- Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
downgrade from 1.1.4 to 1.0.X
Hi, We are running Cassandra 1.1.4 and like to experiment with Datastax Enterprise which uses 1.0.8. Can we safely downgrade a production cluster or is it incompatible? Any special steps involved? Arend-Jan -- Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
lost keyspace
Hi,
Today we rebooted a node in our cluster for maintenance and after that
one of the keyspaces went missing. This is what we did leading up to
this:
nodetool drain -h localhost
reboot
restart cassandra
There was an error during startup:
ERROR [MutationStage:109] 2012-08-08 14:05:56,443 RowMutationVerbHandler.java
(line 61) Error in row mutation
org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find cfId=1014
(then we found keyspace twitter is missing)
The sstables are still there so I tried to re-create the keyspace:
cassandra-cli -h localhost
[default@unknown] create keyspace twitter with placement_strategy =
'org.apache.cassandra.locator.SimpleStrategy' and strategy_options =
{replication_factor:3} ;
b890b65a-40a6-3fc5-838d-34d58368cb64
Waiting for schema agreement...
... schemas agree across the cluster
NotFoundException()
default@unknown] use twitter;
Keyspace 'twitter' not found.
So we can't create the keyspace. The cassandra version is 1.1.0.
What is the proper way to deal with this?
Thanks for your help.
Arend-Jan
--
Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
Re: lost keyspace
Forgot to mention that the keyspace 'twitter' was created, then droppend
and re-created a couple of days ago.
How about if I create a new keyspace with the same definition and then
copy the existing tables into the proper place and call nodetool
refresh on each node. Would that work or are there references in the
tables to the keyspace name?
On Wed, Aug 08, 2012 at 03:03:52PM +0200, Arend-Jan Wijtzes wrote:
Hi,
Today we rebooted a node in our cluster for maintenance and after that
one of the keyspaces went missing. This is what we did leading up to
this:
nodetool drain -h localhost
reboot
restart cassandra
There was an error during startup:
ERROR [MutationStage:109] 2012-08-08 14:05:56,443 RowMutationVerbHandler.java
(line 61) Error in row mutation
org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find cfId=1014
(then we found keyspace twitter is missing)
The sstables are still there so I tried to re-create the keyspace:
cassandra-cli -h localhost
[default@unknown] create keyspace twitter with placement_strategy =
'org.apache.cassandra.locator.SimpleStrategy' and strategy_options =
{replication_factor:3} ;
b890b65a-40a6-3fc5-838d-34d58368cb64
Waiting for schema agreement...
... schemas agree across the cluster
NotFoundException()
default@unknown] use twitter;
Keyspace 'twitter' not found.
So we can't create the keyspace. The cassandra version is 1.1.0.
What is the proper way to deal with this?
Thanks for your help.
Arend-Jan
--
Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
--
Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
Re: lost keyspace
On Wed, Aug 08, 2012 at 05:08:56PM +0200, Mateusz Korniak wrote: On Wednesday 08 of August 2012, Arend-Jan Wijtzes wrote: Forgot to mention that the keyspace 'twitter' was created, then droppend and re-created a couple of days ago. How about if I create a new keyspace with the same definition and then copy the existing tables into the proper place and call nodetool refresh on each node. Would that work or are there references in the tables to the keyspace name? Worth to try, should work. Perhaps use _copy_ of SStables. I did that during schema version desync solving few times on 1.0.x. Make sure you have same schema version on all nodes first. OK that worked. One extra step was required and that was to rename the keyspace part in the filenames of the sstables. Still would like to know why the original keyspace got lost and if there is a 'proper' way to restore it. -- Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
endless hinted handoff with 1.1
Hi, We are running a small test cluster and recently installed Cassandra 1.1 and started with a new clean database. We keep seeing these messages in the log on just one of our nodes: INFO [HintedHandoff:1] 2012-05-21 09:49:56,757 HintedHandOffManager.java (line 294) Started hinted handoff for token: 85070591730234615865843651857942052864 with IP: /10.0.0.73 INFO [HintedHandoff:1] 2012-05-21 09:49:56,775 HintedHandOffManager.java (line 382) Finished hinted handoff of 0 rows to endpoint /10.0.0.73 INFO [HintedHandoff:1] 2012-05-21 09:59:56,756 HintedHandOffManager.java (line 294) Started hinted handoff for token: 42535295865117307932921825928971026432 with IP: /10.0.0.69 INFO [HintedHandoff:1] 2012-05-21 09:59:56,757 HintedHandOffManager.java (line 382) Finished hinted handoff of 0 rows to endpoint /10.0.0.69 INFO [HintedHandoff:1] 2012-05-21 09:59:56,757 HintedHandOffManager.java (line 294) Started hinted handoff for token: 85070591730234615865843651857942052864 with IP: /10.0.0.73 INFO [HintedHandoff:1] 2012-05-21 09:59:56,775 HintedHandOffManager.java (line 382) Finished hinted handoff of 0 rows to endpoint /10.0.0.73 INFO [HintedHandoff:1] 2012-05-21 10:09:56,757 HintedHandOffManager.java (line 294) Started hinted handoff for token: 42535295865117307932921825928971026432 with IP: /10.0.0.69 INFO [HintedHandoff:1] 2012-05-21 10:09:56,758 HintedHandOffManager.java (line 382) Finished hinted handoff of 0 rows to endpoint /10.0.0.69 INFO [HintedHandoff:1] 2012-05-21 10:09:56,758 HintedHandOffManager.java (line 294) Started hinted handoff for token: 85070591730234615865843651857942052864 with IP: /10.0.0.73 INFO [HintedHandoff:1] 2012-05-21 10:09:56,879 HintedHandOffManager.java (line 382) Finished hinted handoff of 0 rows to endpoint /10.0.0.73 All four nodes are up: -bash-4.1$ nodetool ring -h localhost Note: Ownership information does not include topology, please specify a keyspace. Address DC RackStatus State LoadOwns Token 127605887595351923798765477786913079296 10.0.0.65 datacenter1 rack1 Up Normal 244.41 MB 25.00% 0 10.0.0.69 datacenter1 rack1 Up Normal 155.39 MB 25.00% 42535295865117307932921825928971026432 10.0.0.73 datacenter1 rack1 Up Normal 220.42 MB 25.00% 85070591730234615865843651857942052864 10.0.0.77 datacenter1 rack1 Up Normal 296.14 MB 25.00% 127605887595351923798765477786913079296 This has been going on for days. Note that it's just two key's in the log that keep repeating. No recent messages about HintedHandOff in the logs on the other nodes. Let me know if you need more info. Arend-Jan -- Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
