Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1A4ED200C77 for ; Mon, 1 May 2017 22:32:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 18DC4160BAE; Mon, 1 May 2017 20:32:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 60BD9160BA0 for ; Mon, 1 May 2017 22:32:34 +0200 (CEST) Received: (qmail 26625 invoked by uid 500); 1 May 2017 20:32:32 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 26615 invoked by uid 99); 1 May 2017 20:32:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 May 2017 20:32:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 44FB9C01DB for ; Mon, 1 May 2017 20:32:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.397 X-Spam-Level: X-Spam-Status: No, score=-0.397 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id IRnCZWKhWIBm for ; Mon, 1 May 2017 20:32:31 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 56CAD5F2FD for ; Mon, 1 May 2017 20:32:31 +0000 (UTC) Received: by mail-io0-f178.google.com with SMTP id a103so129487817ioj.1 for ; Mon, 01 May 2017 13:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=C8QiyE2ucF/YTicbl6hHwGVsWx4hSETrvOemS19+hQU=; b=mekwajZYz6pI8sj6qQz89FCCauzYaibS7IHcBIS71yjOUARsxmpSwwiedeCOLz29QK ZG8oNtGiFDqECw6eCFRSWhnoyPIFPZZm0y0gbbFmvwk4a4UjurGsoemY9QU0WBucOJdJ 9TMYiicyQcjV2uc3GHOVSipmuTGW6XvIP4jy8S48tDLMcZC2tAEjQbaqPKeADUwK2ggK msQl8EEe5BLv1NBzJw71Z32Ea8wwyw8Ppj5rgxLq5HVPrZExnpSxMQfsaRBybInip7wE byiD4jE5+QciThmEEHbsiPFO0MntMBT7KdqoWBlllYlSWQKo++To780oGJbt6a/F0dGe x6Hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=C8QiyE2ucF/YTicbl6hHwGVsWx4hSETrvOemS19+hQU=; b=WDYnxCA9K2yqlYZSw8T+WQQZz2exYsRU8vq3H4n+qvqMVs0RsQ1GJhNSMgy30agzGD wmmarRiZ/fJ1dkSM1t+BO14sKGq8QcRMM9tHm3XedmfgfekUMEM2fj3pvHF3t2rpSGj5 dDr4/firDgBFgiVP8c85UYvWwEf20UT9jQOJejVB74HAYKSQV8PmCSqP9gSz4X7HWmjD WDbuUDbPaLLpuELHX7cekVilcbRRBYTZZjCzhm5A5ZjNuPzAYlHajwgKElbKUaR0zYQx 0KWQ0bb3G8TY4434VSDvTcy7n1DuI7O6UZyF9chMZSWGfzWirq8+P9tEoD1Rwh5dmUc5 G4hA== X-Gm-Message-State: AN3rC/62+bDljkMihX2E4LrGKk0GDgv0cFL/hnQLZcllHrFRcAQycxEV STrNnRmOqnGWGxdnwcK7aPW3uBd8UXMBMAs= X-Received: by 10.157.11.145 with SMTP id 17mr9811772oth.144.1493670750668; Mon, 01 May 2017 13:32:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.46.243 with HTTP; Mon, 1 May 2017 13:32:30 -0700 (PDT) From: vasu gunja Date: Mon, 1 May 2017 15:32:30 -0500 Message-ID: Subject: token distribution in multi-dc To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1136e4c2815163054e7c5208 archived-at: Mon, 01 May 2017 20:32:35 -0000 --001a1136e4c2815163054e7c5208 Content-Type: text/plain; charset=UTF-8 Hi , I have a question regarding token distribution in muti-dc setup. We are having multi-dc (DC1+DC2) setup with V-nodes enabled. How token ranges will be distributed in cluster ? Is complete cluster has completed one token range ? Or each DC has complete token range? --001a1136e4c2815163054e7c5208 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi ,

I have a question regar= ding token distribution in muti-dc setup.

We are h= aving multi-dc (DC1+DC2)=C2=A0setup with V-nodes=C2=A0enabled.
Ho= w token ranges will be distributed in cluster ?

I= s complete cluster has completed one token range ?
Or each DC has= complete token=C2=A0 range?


--001a1136e4c2815163054e7c5208--