The thread below makes me wonder "Does RF matter when using sstable loader.?" My assumption was that stable loader will take care of RF when the streaming is done but just wanted to cross check. We are currently moving data from a RF=1 to RF=3 cluster by using sstable loader tool. We will of course be running repair on the destination nodes but was wondering how is the following issue resolved using a repair if my understanding is wrong?
If the above assumption is wrong and since we are using Sstableloader which streams relevant parts to of each table to the destination cluster, it means the destination folder will only get one copy only (because origin RF =1 ) ? If that is the case, how will a repair resolve when a data chunk from an empty folder is used as the chosen replica to perform repair ( as it possible that two "nearest neighbors" are empty in the first place ) .
"Leaving the system keyspaces behind is OK if you are not using vnodes. "Why is it different for vnodes?On Mon, Jul 8, 2013 at 3:37 PM, aaron morton <email@example.com> wrote:This might work for user created keyspaces but might not work for system keyspaceLeaving the system keyspaces behind is OK if you are not using vnodes.CheersOn 9/07/2013, at 10:03 AM, sankalp kohli <firstname.lastname@example.org> wrote:"If RF=N or RF>N, you can just copy all SStables to all nodes, watching out for name collision."This might work for user created keyspaces but might not work for system keyspaceOn Mon, Jul 8, 2013 at 2:07 PM, Robert Coli <email@example.com> wrote:On Fri, Jul 5, 2013 at 7:54 PM, srmore <firstname.lastname@example.org> wrote:RF of old and new cluster is the same RF=3. Keyspaces and schema info is also same.You have a cluster where RF=3 and N=2? Does it.. work?What are the tokens of old and new nodes?tokens for old cluster ( 2-node )If RF=N or RF>N, you can just copy all SStables to all nodes, watching out for name collision.=Rob