RE: Issues on upgrading from 2.2.3 to 3.0

2015-12-14 Thread SEAN_R_DURITY
Thank you! I made my comments in the JIRA. Sean Durity – Lead Cassandra Admin From: Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com] Sent: Monday, December 14, 2015 3:25 PM To: user@cassandra.apache.org Subject: Re: Issues on upgrading from 2.2.3 to 3.0 https://issues.apache.org/jira/browse

Re: Issues on upgrading from 2.2.3 to 3.0

2015-12-14 Thread Jeff Jirsa
user@cassandra.apache.org" Subject: RE: Issues on upgrading from 2.2.3 to 3.0 Is there a JIRA for the discussion of dropping PropertyFileSnitch? That is all that we use, and it is much easier to package and distribute than GossipingPropertyFileSnitch. I would vote against dropping the m

RE: Issues on upgrading from 2.2.3 to 3.0

2015-12-14 Thread SEAN_R_DURITY
[mailto:pauloricard...@gmail.com] Sent: Thursday, December 03, 2015 7:04 AM To: user@cassandra.apache.org Subject: Re: Issues on upgrading from 2.2.3 to 3.0 You can migrate from the RackInferingSnitch to PropertiesFileSnitch by populating the cassandra-topology.properties with the same rack/dc

Re: Issues on upgrading from 2.2.3 to 3.0

2015-12-03 Thread Paulo Motta
You can migrate from the RackInferingSnitch to PropertiesFileSnitch by populating the cassandra-topology.properties with the same rack/dc assignments of the previous snitch (what you can't change is the assignment, but you can change snitches if you maintain the same assignments as before). For ex

Re: Issues on upgrading from 2.2.3 to 3.0

2015-12-02 Thread Carlos A
Bryan, thanks for replying. I had that figured out already few days ago. The issue was that the snitch method was also changed on the configuration hence the problem. Now, if you change from rackInferingSnitch to PropertiesFileSnitch it will not run as the data has to be migrated. Is that correct?

Re: Issues on upgrading from 2.2.3 to 3.0

2015-12-02 Thread Bryan Cheng
Has your configuration changed? This is a new check- https://issues.apache.org/jira/browse/CASSANDRA-10242. It seems likely either your snitch changed, your properties changed, or something caused Cassandra to think one of the two happened... What's your node layout? On Fri, Nov 27, 2015 at 6:45

Issues on upgrading from 2.2.3 to 3.0

2015-11-27 Thread Carlos A
Hello all, I had 2 of my systems upgraded to 3.0 from the same previous version. The first cluster seem to be fine. But the second, each node starts and then fails. On the log I have the following on all of them: INFO [main] 2015-11-27 19:40:21,168 ColumnFamilyStore.java:381 - Initializing sy