[
https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-682:
-------------------------------------
Comment: was deleted
(was: Some more info after repeating...I received the follow error a couple of
times on node 42535295865117307932921825928971026432 while node 0 was still in
the process of bootstrapping:
INFO - Waiting for transfer to /10.242.4.13 to complete
WARN - Running on default stage - beware
WARN - Running on default stage - beware
WARN - Problem reading from socket connected to :
java.nio.channels.SocketChannel[conne
cted local=/10.242.4.10:45868 remote=/10.242.4.13:7000]
java.io.IOException: Reached an EOL or something bizzare occured. Reading from:
/10.242
.4.13 BufferSizeRemaining: 16
at org.apache.cassandra.net.io.StartState.doRead(StartState.java:44)
at org.apache.cassandra.net.io.ProtocolState.read(ProtocolState.java:39)
at org.apache.cassandra.net.io.TcpReader.read(TcpReader.java:95)
at
org.apache.cassandra.net.TcpConnection$ReadWorkItem.run(TcpConnection.java:4
27)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
10)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
03)
at java.lang.Thread.run(Thread.java:636)
INFO - Closing errored connection java.nio.channels.SocketChannel[connected
local=/10.2
42.4.10:45868 remote=/10.242.4.13:7000]
No other nodes reported any errors.)
> After bootstrap, some nodes cannot find keys
> --------------------------------------------
>
> Key: CASSANDRA-682
> URL: https://issues.apache.org/jira/browse/CASSANDRA-682
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.9
> Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build
> 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Fix For: 0.9
>
>
> I started a 3 node cluster with RF=3 and loaded about 3M keys into it. I
> proceeded to bootstrap a 4th node and it completed. Upon performing a read
> test, I found that two nodes could find all keys, and two nodes could find
> none, depending upon which machine I queried. Here is the ring output:
> Address Status Load Range
> Ring
> 127605887595351923798765477786913079296
> 10.242.4.13 Up 1023.44 MB 0
> |<--|
> 10.242.4.10 Up 1.34 GB 42535295865117307932921825928971026432
> | |
> 10.242.4.11 Up 1.33 GB 85070591730234615865843651857942052864
> | |
> 10.242.4.12 Up 1.41 GB
> 127605887595351923798765477786913079296 |-->|
> Token 0 was the newly bootstrapped node. Tokens
> 127605887595351923798765477786913079296 and
> 85070591730234615865843651857942052864 were able to read all keys, the other
> two nodes were not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
