From user-return-64800-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Sun Dec 1 09:41:07 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2A4D218061A for ; Sun, 1 Dec 2019 10:41:07 +0100 (CET) Received: (qmail 92091 invoked by uid 500); 1 Dec 2019 09:41:04 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 92081 invoked by uid 99); 1 Dec 2019 09:41:04 -0000 Received: from ui-eu-02.ponee.io (HELO localhost) (116.202.110.96) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Dec 2019 09:41:04 +0000 MIME-Version: 1.0 Message-ID: From: slmnjobs - In-Reply-To: Content-Type: text/plain; charset=utf-8 x-ponymail-agent: PonyMail Composer/0.2 To: X-Mailer: LuaSocket 3.0-rc1 References: Subject: Migration a Keyspace from 3.0.X to 3.11.2 Cluster which already have keyspaces Date: Sun, 01 Dec 2019 09:41:02 -0000 x-ponymail-sender: 4b1ff5850fe26601884fc4db6c301e6de4072fbb Hi everyone, I have a question about migrate a keyspace another cluster. The main problem for us, our new cluster already have 2 keyspaces and we using it in production. Because of we don't sure how token ranges will be change, we would like the share our migration plan here and take back your comments. We have two Cassandra clusters which one of them: CLUSTER-A : - Cassandra version 3.0.10 - describe keyspace: CREATE KEYSPACE mykeyspace WITH replication = {'class': 'NetworkTopologyStrategy', 'DC1': '3', 'DC2': '3', 'DC3': '1'}  AND durable_writes = true; - DC1 : 6 nodes - DC2 : 6 nodes - DC3 : 1 node (backup node, have all data) CLUSTER-B : - Cassandra version 3.11.2 - DC1 : 5 nodes - DC2 : 5 nodes- DC3 : 1 node - Already have 2 keyspaces and write/read traffic We want to migrate a keyspace which on CLUSTER-A to CLUSTER-B. There're some solutions for restore or migrate a keyspace on a new cluster but I haven't seen any safety way about how we can migrate a keyspace on existing cluster which already have keyspaces. Replication Factor won't change. We think about two ways : one of them using sstableloader and other one using COPY TO/COPY FROM commands. Our migration plan is: - export of keyspace schema structure with DESC keyspace on CLUSTER-A - create keyspace schema on CLUSTER-B - disable writing traffic on application layer - load data from CLUSTER-A, DC3 backup node (which have all data) to CLUSTER-B, DC1 with sstableloader or COPY command (each table wiil be copy one by one). - update cluster IP addresses in application configuration - enable writing traffic on application layer So do you see any risk or any suggestion for this plan? Thanks a lot. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org For additional commands, e-mail: user-help@cassandra.apache.org