If you join a node with auto_bootstrap=false you had better be working
at quorum or higher to avoid stale/not found reads. You should then
repair the node right away to get all the missing data back on the
node. This is not suggested. It is best to leave auto_boostrap=true
and let Cassandra handle this on the front end.
This do not works. I joined ring with node without bootstrap and result
is like this:
216.17.99.40 datacenter1 rack1 Up Normal 1.17 GB
99.64% 83030609119105147711596238577753588267
64.6.104.18 datacenter1 rack1 Up Normal 43.15 KB
0.36% 83648735508289295779178617154261005054
Well, this was expected. But running repair on both nodes didnt do anything:
INFO [GossipStage:1] 2011-09-25 08:18:34,287 Gossiper.java (line 715)
Node /216.17.99.40 is now part of the cluster
INFO [GossipStage:1] 2011-09-25 08:18:34,287 Gossiper.java (line 681)
InetAddress /216.17.99.40 is now UP
INFO [AntiEntropySessions:1] 2011-09-25 08:22:16,066
AntiEntropyService.java (line 648) No neighbors to repair with for test
on
(83030609119105147711596238577753588267,83648735508289295779178617154261005054]:
manual-repair-04dd27f0-401b-4452-b0eb-853beeda197b completed.
Data are not moved to new node. Maybe tokens are not too random. I
deleted new node and retried:
64.6.104.18 datacenter1 rack1 Up Normal 45.52 KB
56.94% 9762979552315026283322466206354139578
216.17.99.40 datacenter1 rack1 Up Normal 1.17 GB
43.06% 83030609119105147711596238577753588267
and still nothing, while running repair on both nodes.
INFO [AntiEntropySessions:1] 2011-09-25 08:29:13,447
AntiEntropyService.java (line 648) No neighbors to repair with for test
on
(83030609119105147711596238577753588267,9762979552315026283322466206354139578]:
manual-repair-87bfcc67-2b99-4285-8571-e5bd168ef5e0 completed.
Can you try this too? i cant get scenario: make 1 node - add data, add
second node without bootstrap then repair on both work.
