after nodetool repair on new node following log appears in cassandra log INFO [StreamConnectionEstablisher:1] 2017-05-31 10:07:23,496 > StreamSession.java:266 - [Stream #f0eb9670-45e8-11e7-a17b-81e9a18c6eac] > Starting streaming to /10.128.1.2 > INFO [StreamConnectionEstablisher:1] 2017-05-31 10:07:23,501 > StreamCoordinator.java:264 - [Stream #f0eb9670-45e8-11e7-a17b-81e9a18c6eac, > ID#0] Beginning stream session with /10.128.1.2 > INFO [STREAM-IN-/10.128.1.2:7000] 2017-05-31 10:07:23,545 > StreamResultFuture.java:173 - [Stream #f0eb9670-45e8-11e7-a17b-81e9a18c6eac > ID#0] Prepare completed. Receiving 2 files(131.594KiB), sending 0 > files(0.000KiB) > INFO [StreamReceiveTask:1] 2017-05-31 10:07:23,705 > StreamResultFuture.java:187 - [Stream > #f0eb9670-45e8-11e7-a17b-81e9a18c6eac] Session with /10.128.1.2 is > complete > INFO [StreamReceiveTask:1] 2017-05-31 10:07:23,707 > StreamResultFuture.java:219 - [Stream > #f0eb9670-45e8-11e7-a17b-81e9a18c6eac] All sessions completed
On Wed, May 31, 2017 at 2:50 PM, Junaid Nasir <jna...@an10.io> wrote: > Cassandra version is 3.10, and yes its not a production server. i have > seen some warnings in logs saying token exist on both servers. other than > that nothing. if you need any more settings/details please ask. thank you > for your time > > > On Wed, May 31, 2017 at 2:04 PM, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > >> On Wed, May 31, 2017 at 9:55 AM, Junaid Nasir <jna...@an10.io> wrote: >> >>> Cassandra ensure that adding or removing nodes are very easy and that >>> load is balanced between nodes when a change is made. but it's not working >>> in my case. >>> I have a single node C* deployment (with 270 GB of data) and want to >>> load balance the data on multiple nodes, >>> >> >> I guess it's fair to assume this is not a production "cluster"? >> >> >>> I followed this guide >>> <https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_node_to_cluster_t.html> >>> >>> `nodetool status` shows 2 nodes but load is not balanced between them >>> >>> Datacenter: dc1 >>> =============== >>> Status=Up/Down >>> |/ State=Normal/Leaving/Joining/Moving >>> -- Address Load Tokens Owns (effective) Host ID Rack >>> UN 10.128.0.7 270.75 GiB 256 48.6% >>> 1a3f6faa-4376-45a8-9c20-11480ae5664c rack1 >>> UN 10.128.0.14 414.36 KiB 256 51.4% >>> 66a89fbf-08ba-4b5d-9f10-55d52a199b41 rack1 >>> >>> I can imagine you are referring to Load column here, which shows only >> 400 KB for the new node. Did the newly added node actually bootstrap? Are >> there any error/warning messages in the Cassandra log? >> >> >>> I also ran 'nodetool repair' on new node but result is same. any >>> pointers would be appreciated :) >>> >> >> Hm, this is not expected. Even if the node didn't bootstrap, repair >> should have streamed the data it is responsible for. >> >> conf file of new node >>> >>> cluster_name: 'cluster1' >>> - seeds: "10.128.0.7" >>> num_tokens: 256 >>> endpoint_snitch: GossipingPropertyFileSnitch >>> >>> I see that you've tried to add the new node as a normal (non-seed) node, >> which supposed to work and it should have bootstrapped itself. Which >> version of Cassandra is it exactly? >> >> -- >> Oleksandr "Alex" Shulgin | Database Engineer | Zalando SE | Tel: +49 176 >> 127-59-707 <+49%20176%2012759707> >> >> >
