From user-return-63065-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Mon Jan 28 09:44:48 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6150118060E for ; Mon, 28 Jan 2019 09:44:48 +0100 (CET) Received: (qmail 99056 invoked by uid 500); 28 Jan 2019 08:44:46 -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 99033 invoked by uid 99); 28 Jan 2019 08:44:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2019 08:44:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C21C91807E5 for ; Mon, 28 Jan 2019 08:44:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.798 X-Spam-Level: * X-Spam-Status: No, score=1.798 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id qRAxdv-KdI_6 for ; Mon, 28 Jan 2019 08:44:44 +0000 (UTC) Received: from mail-pl1-f171.google.com (mail-pl1-f171.google.com [209.85.214.171]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 635995F21F for ; Mon, 28 Jan 2019 08:44:43 +0000 (UTC) Received: by mail-pl1-f171.google.com with SMTP id u6so7445842plm.8 for ; Mon, 28 Jan 2019 00:44:43 -0800 (PST) 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=+IHviFvdc/hF/JNR5VQ+bpUUpu6F2kkk9+AYWzJSTPk=; b=TvxtFDvOpEpcEGEGBcIv1FZEpd5WKDU2MbIRdShkWqDwlkETWomiA+tdOMApLMg84L t6HBqmLYQPhgiNlyttIOiDEBmGCkq+cUfGn0w1fJdlYB8N04M5lqEoYL5r/sEBcRmL6D 0Z0A0XcrkZjnEeEfO+7VlVYRdfQAfdDW8qTg/0TffLNqfBeDcLHmaroFMXZXiuzE9yRu A6o2ADItA3ExvVojEWoF5UdXgEfB+ZUoVTCFnq6yETUFdCNfd47mdrWb5rG9Shc6rDAO laDmmLC1HNtJBqJU2yo0oUN+4Fg8ID37e2QQ44leSD8wKGgddWLt/ZMMnJb4qVYYpa+r IGhQ== 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=+IHviFvdc/hF/JNR5VQ+bpUUpu6F2kkk9+AYWzJSTPk=; b=f+PjASl9fhuSAQop4syXK2QTjxwQ4wOyH9c8U4t7AglAYsZYGBUhhgT/v7NJJf+YG1 BLeVmZZxFSUN9YZANL/mHSh+n15kWFvm9+39GwZv8GXqfZknTpibYb95ZtHMN3VHZ2IS 7ka4IoZ2B6QQ2LsRkY85WJuAN8GJvgNkYNapEdK3Qx7vGuA09RlAZi2Lk/djDmcAhiFh szOREIYAcjB4jFWWaDf7DwVtMDtvUkIBjZbvTIkqYgcqDqRWJoyKlpQnpeAi9G2AJIsE BB3KblNY8pNZ+uUf9AWStoPazQedyqoeCjoAU1i/uw2MQVrfg1Y/yiYgyKTqykduOEuf Xibw== X-Gm-Message-State: AJcUukcwPYzP8yNjLdxce8nP+NrVJdpkeBzPowRD6fm9efGBF35Pxx66 eoJjDWQMHOrHg+9NoLqMGhmT50lz2BYCcJwv+5WizB3z X-Google-Smtp-Source: ALg8bN6edmaXe5hAwQfkybVRRzyfzoLXPjRWkfTI+xXlDbKh2VXeIDEIqtl3pcIjOI5t52oMGLykSa//OSFDFRhRKEg= X-Received: by 2002:a17:902:2887:: with SMTP id f7mr20522049plb.176.1548665075916; Mon, 28 Jan 2019 00:44:35 -0800 (PST) MIME-Version: 1.0 From: Ahmed Eljami Date: Mon, 28 Jan 2019 09:44:24 +0100 Message-ID: Subject: Question about allocate_tokens_for_keyspace To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary="000000000000b9e47a058080afa8" --000000000000b9e47a058080afa8 Content-Type: text/plain; charset="UTF-8" Hi Folks, I'm about to configure a new cluster with num_token = 32 and using the new token allocation. For the first keyspace, I understood that it will be used to start my cluster: allocate_tokens_for_keyspace = my_first_ks. My question is how about the rest of keyspaces ? they will take the same conf than the first ks or I have to add them to the cassandra.yaml and restart each time my cluster? Thanks --000000000000b9e47a058080afa8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Folks,

I'm about to configure a new cluster wi= th num_token =3D 32 and using the new token allocation.

For the first keyspace,=20 I understood=C2=A0 that it will be used to start my cluster: all= ocate_tokens_for_keyspace =3D my_first_ks.

= My question is how about the rest of keyspaces ? they will take the same c= onf than the first ks or I have to add them to the cassandra.yaml and resta= rt each time my cluster?

Thanks

--000000000000b9e47a058080afa8--