Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4FB2F7A5.3030606@mebigfatguy.com>
Date: Tue, 15 May 2012 20:41:09 -0400
From: Dave Brosius <dbrosius@mebigfatguy.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: cassandra upgrade to 1.1 - migration problem
References: 
 <CAEKtLiR_06t5fraJqrOvxtpia43mweQqDs+3=sEH_4B3Q=KkRQ@mail.gmail.com>
 <CAEKtLiRQY4KMu4x0hJVezuAiRkmton_276JzQQ1bROtM8eu0hA@mail.gmail.com>
 <C170A5B0-A12B-41C4-97E8-D4D90FA3DA41@liquidanalytics.com>
 <CAEKtLiSyDEnjCUvM5dzxuLOC_HzT-hSnL2cyqyfKGi5umPZ0BQ@mail.gmail.com>
 <CAEKtLiQen1JTUmj5L_7+1iB1W+jL9FmykR7==TStrmZmyVbFWw@mail.gmail.com>
In-Reply-To: 
 <CAEKtLiQen1JTUmj5L_7+1iB1W+jL9FmykR7==TStrmZmyVbFWw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The replication factor for a keyspace is stored in the 
system.schema_keyspaces column family.

Since you can't view this with cli as the server won't start, the only 
way to look at it, that i know of is to use the

sstable2json tool on the *.db file for that column family...

So for instance on my machine i do

./sstable2json 
/var/lib/cassandra/data/system/schema_keyspaces/system-schema_keyspaces-ia-1-Data.db

and get


{
"7374726573735f6b73": [["durable_writes","true",1968197311980145], 
["name","stress_ks",1968197311980145], 
["strategy_class","org.apache.cassandra.locator.SimpleStrategy",1968197311980145], 
["strategy_options","{\"replication_factor\":\"3\"}",1968197311980145]]

It's likely you don't have a entry from replication_factor.

Theoretically i suppose you could embellish the output, and use 
json2sstable to fix it, but I have no experience here, and would get the 
blessings of datastax fellas, before proceeding.


On 05/15/2012 07:02 PM, Casey Deccio wrote:
> Sorry to reply to my own message (again).  I took a closer look at the 
> logs and realized that the partitioner errors aren't what kept the 
> daemon to stop; those errors are in the logs even before I upgraded.  
> This one seems to be the culprit.
>
> java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at 
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:160)
> Caused by: java.lang.RuntimeException: 
> org.apache.cassandra.config.ConfigurationException: SimpleStrategy 
> requires a replication_factor strategy option.
>         at org.apache.cassandra.db.Table.<init>(Table.java:275)
>         at org.apache.cassandra.db.Table.open(Table.java:114)
>         at org.apache.cassandra.db.Table.open(Table.java:97)
>         at 
> org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:204)
>         at 
> org.apache.cassandra.service.AbstractCassandraDaemon.init(AbstractCassandraDaemon.java:254)
>         ... 5 more
> Caused by: org.apache.cassandra.config.ConfigurationException: 
> SimpleStrategy requires a replication_factor strategy option.
>         at 
> org.apache.cassandra.locator.SimpleStrategy.validateOptions(SimpleStrategy.java:71)
>         at 
> org.apache.cassandra.locator.AbstractReplicationStrategy.createReplicationStrategy(AbstractReplicationStrategy.java:218)
>         at 
> org.apache.cassandra.db.Table.createReplicationStrategy(Table.java:295)
>         at org.apache.cassandra.db.Table.<init>(Table.java:271)
>         ... 9 more
> Cannot load daemon
>
> I'm not sure how to check the replication_factor and/or update it 
> without using cassandra-cli, which requires the daemon to be running.
>
> Casey