It depends on why you're adding a new node. If you're running out of disk space or IO capacity in your 2 node cluster, then changing RF to 3 will not improve either condition - you'd still be writing all data to all three nodes.
However if you're looking to improve reliability, a 2 node RF=2 cluster cannot have either node offline without losing quorum, while a 3 node RF=3 cluster can have one node offline and still be able to achieve quorum. RF=3 is a common replication factor because of this characteristic. Make sure your new node is not in its own seeds list, or it will not bootstrap (it will come online immediately and start serving requests). On Mon, Apr 27, 2015 at 8:46 AM, Neha Trivedi <nehajtriv...@gmail.com> wrote: > Hi > We have a 2 Cluster Node with RF=2. We are planing to add a new node. > > Should we change RF to 3 in the schema? > OR Just added a new node with the same RF=2? > > Any other Best Practice that we need to take care? > > Thanks > regards > Neha > >
