You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/01/07 18:49:54 UTC
[jira] Created: (CASSANDRA-682) After bootstrap, some nodes cannot
find keys
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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798126#action_12798126 ]
Brandon Williams commented on CASSANDRA-682:
--------------------------------------------
I tested bootstrap on 0.5 and this did not occur, for what it's worth.
> 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800024#action_12800024 ]
Brandon Williams commented on CASSANDRA-682:
--------------------------------------------
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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800025#action_12800025 ]
Brandon Williams commented on CASSANDRA-682:
--------------------------------------------
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.
[jira] Resolved: (CASSANDRA-682) After bootstrap, some nodes cannot
find keys
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek resolved CASSANDRA-682.
-------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 0.9)
0.5
Same root cause as CASSANDRA-696.
> 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.5
>
>
> 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.
[jira] Updated: (CASSANDRA-682) After bootstrap, some nodes cannot
find keys
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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: (This appears to be a new regression in 0.9.))
> 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.
[jira] Updated: (CASSANDRA-682) After bootstrap, some nodes cannot
find keys
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798127#action_12798127 ]
Jonathan Ellis commented on CASSANDRA-682:
------------------------------------------
(This appears to be a new regression in 0.9.)
> 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798130#action_12798130 ]
Brandon Williams commented on CASSANDRA-682:
--------------------------------------------
Yes, the tokens are spread evenly and I used 0 instead of 2**127, simply because it's easier to remember and type.
> 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799884#action_12799884 ]
Brandon Williams commented on CASSANDRA-682:
--------------------------------------------
No, this was with the default config, so only one keyspace.
> 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798129#action_12798129 ]
Jonathan Ellis commented on CASSANDRA-682:
------------------------------------------
i take it you specified initialtoken manually, get the result of 0?
> 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.
[jira] Commented: (CASSANDRA-682) After bootstrap, some nodes
cannot find keys
Posted by "Michael Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799693#action_12799693 ]
Michael Lee commented on CASSANDRA-682:
---------------------------------------
maybe it's the same bug as 673?
does you use multi-keyspace, and one of them is empty??
> 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.