sorry, my bad. messed up the yaml file. I will try it again. thanks a lot!
On Tue, Sep 20, 2011 at 5:08 PM, aaron morton wrote:
> Is the data still physically on node 1 ? During start up does it log about
> opening the SSTables ?
>
> Another sometimes problem is if the schema is out of sync, and
Is the data still physically on node 1 ? During start up does it log about
opening the SSTables ?
Another sometimes problem is if the schema is out of sync, and node 1 may not
have all the CF's and will not have opened the SSTables.
Check the logs and check if the physical data is there.
Ch
any help on this? thanks!
On Sun, Sep 18, 2011 at 5:04 PM, Yan Chunlu wrote:
> thanks! is the load info also a bug? node1 supposed to have 80MB.
>
> bash-3.2$ bin/nodetool -h localhost ring
> Address DC RackStatus State LoadOwns
>Token
>
>9379860
thanks! is the load info also a bug? node1 supposed to have 80MB.
bash-3.2$ bin/nodetool -h localhost ring
Address DC RackStatus State LoadOwns
Token
93798607613553124915572813490354413064
node2 datacenter1 rack1 Up Normal 86.03 MB
> It's fixed on 0.8.6. For 0.8.5 you would have to build it from source
> with the patch applied, yes.
>
> (Actually, in my opinion this bugfix is a good reason to release 0.8.6.)
Turns out I had managed to miss the fact that a 0.8.6 release is being
voted on so I'd expect it to happen soonish. Yo
> also not fixed in 0.8.5? I am using the binary version of 0.8.5. Applying
> the fix might need to compile it from the source?
It's fixed on 0.8.6. For 0.8.5 you would have to build it from source
with the patch applied, yes.
(Actually, in my opinion this bugfix is a good reason to release 0.
also not fixed in 0.8.5? I am using the binary version of 0.8.5. Applying
the fix might need to compile it from the source?
On Sun, Sep 18, 2011 at 3:28 AM, Peter Schuller wrote:
> >> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
> >> 0.8.5
>
> [snip]
>
> > Yes. It
>> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
>> 0.8.5
[snip]
> Yes. It will take a few exchanges before the new node knows to use
> the older protocol with the 0.7 nodes.
Not going 0.7.4->0.8.4, due to
https://issues.apache.org/jira/browse/CASSANDRA-3166
OP:
so the schema version not consistent is abnormal?
is there a document explains the possible problem while upgrading? I think
it might be concerned by many cassandra users. cause if anything unexpected
during upgrade, might cause serious problem on production server. cause
there is no way to rever
On Fri, Sep 16, 2011 at 9:42 AM, Yan Chunlu wrote:
> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
> 0.8.5
> after upgrade one node1, two problem happened:
> 1, node2 keep saying:
> "Received connection from newer protocol version. Ignorning message."
> is that normal
You might need to do the nodetool scrub on the nodes to rebuild the sstables
for the different protocols.
On Fri, Sep 16, 2011 at 10:50 PM, Yan Chunlu wrote:
> and also the load is unusual(node1 has 80M data before the upgrade):
>
> bash-3.2$ bin/nodetool -h localhost ring
> Address DC
and also the load is unusual(node1 has 80M data before the upgrade):
bash-3.2$ bin/nodetool -h localhost ring
Address DC RackStatus State LoadOwns
Token
93798607613553124915572813490354413064
node2 datacenter1 rack1 Up Normal 86.03 MB
after kill node1 and start it again, node 3 has the same problems with
node2...
On Fri, Sep 16, 2011 at 10:42 PM, Yan Chunlu wrote:
> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
> 0.8.5
> after upgrade one node1, two problem happened:
>
> 1, node2 keep saying:
>
>
I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
0.8.5
after upgrade one node1, two problem happened:
1, node2 keep saying:
"Received connection from newer protocol version. Ignorning message."
is that normal behaviour?
2, while running "describe cluster" on node1, it
14 matches
Mail list logo
