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 EE6B1200BCD for ; Sun, 13 Nov 2016 01:00:54 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E1194160B14; Sun, 13 Nov 2016 00:00:54 +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 0C826160B00 for ; Sun, 13 Nov 2016 01:00:53 +0100 (CET) Received: (qmail 95607 invoked by uid 500); 13 Nov 2016 00:00:52 -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 95596 invoked by uid 99); 13 Nov 2016 00:00:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Nov 2016 00:00:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D47AA1A026F for ; Sun, 13 Nov 2016 00:00:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.88 X-Spam-Level: * X-Spam-Status: No, score=1.88 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Vy07vXr-MYQ3 for ; Sun, 13 Nov 2016 00:00:49 +0000 (UTC) Received: from mail-vk0-f41.google.com (mail-vk0-f41.google.com [209.85.213.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 15E4F5FC52 for ; Sun, 13 Nov 2016 00:00:49 +0000 (UTC) Received: by mail-vk0-f41.google.com with SMTP id w194so39995415vkw.2 for ; Sat, 12 Nov 2016 16:00:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=yrPzU61Dsgyw7B+jo0kAp6cYUI+tHSf/+X1ZMTlsf6I=; b=ZTbhLIk6H6Ci/VhYDsvDlC/8lb6niFO2zNS57hs6jc0txfj8wVmginYVeNGLGjY6IS 4LS4ojN3ti6jNp0Q9HJO0yewkv3zClag4KEKNRrczDJ8h/plAw1XGIhhLYHm1OFMR4Eo Xbh+TjdqM3jDu3WbogNd3LT/y6mtiJxGPRspxHl3lU9BFKBhW/C0eplNfmyFzteLxV5j pF92biQ1RiWq8z8FUmf/CH6peFL9u0Iy3yJPQ++Y0zuT4gIcuO7L6kpC/j75rIRm94NP A0PZR/bD88dJwZDkIdZmjr7s6w4VG05FeSWNDHRYp1oYDJ0W78v8Mz6uDqUu0CLx4n/C ZK3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=yrPzU61Dsgyw7B+jo0kAp6cYUI+tHSf/+X1ZMTlsf6I=; b=M6/U1aNu2d9HLR+74TAbDAEEIOXxuT8Vc0RK9/W8L8T9LX29SdK9AuIUaqooTRHdl7 FQ9w2XGSLppoYpUH5BXAxp61sig0EttNPY6IUmKecTOOzUiMzPHRqp9UQsRodoNeoPII WOKe8a3RNbIjbe/UJ9Eiy2yjrce/IKMiNRPoIGkp0d5s5muNaf5qCOU3hq8WkZQw/bG0 Z6GjdawAeiD6ntHK0wjlxSJBLGR9v9g4MFaoCKNPymtdB8Ep9WK4HsBhHNQk04a77dV/ aoKHagwEGkJ0Isdbjc25ap4S7y66vX/B09ieJLzM9gr0EyNJoUztAIhQ5qD/29AD/ggs Rjdw== X-Gm-Message-State: ABUngvec5Y1Rjvw6QDaKYA/vrmFFQL2O84utQNvDjl6g5Hx/is6feT/BoUwulGZ/ziF5KLscSuRTWVgwimZ9Xw== X-Received: by 10.31.1.215 with SMTP id 206mr6458977vkb.126.1478995239557; Sat, 12 Nov 2016 16:00:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.0.21 with HTTP; Sat, 12 Nov 2016 16:00:19 -0800 (PST) In-Reply-To: References: <0DC3C0BD-5D64-4608-8146-1E6C0B5AE179@gmail.com> From: sat Date: Sat, 12 Nov 2016 16:00:19 -0800 Message-ID: Subject: Re: Priority for cassandra nodes in cluster To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a113dc588e0dfd505412369d2 archived-at: Sun, 13 Nov 2016 00:00:55 -0000 --001a113dc588e0dfd505412369d2 Content-Type: text/plain; charset=UTF-8 Hi, Thanks all for your valuable suggestion. Thanks and Regards A.SathishKumar On Sat, Nov 12, 2016 at 2:59 PM, Ben Bromhead wrote: > +1 w/ Benjamin. > > However if you wish to make use of spare hardware capacity, look to > something like mesos DC/OS or kubernetes. You can run multiple services > across a fleet of hardware, but provision equal resources to Cassandra and > have somewhat reliable hardware sharing mechanisms. > > On Sat, 12 Nov 2016 at 14:12 Jon Haddad wrote: > >> Agreed w/ Benjamin. Trying to diagnose issues in prod will be a >> nightmare. Keep your DB servers homogeneous. >> >> On Nov 12, 2016, at 1:52 PM, Benjamin Roth >> wrote: >> >> 1. From a 15 year experience of running distributed Services: dont Mix >> Services on machines if you don't have to. Dedicate each server to a single >> task if you can afford it. It is easier to manage and reduces risks in case >> of overload or failure >> 2. You can assign a different number of tokens for each node by setting >> this in Cassandra.yaml before you bootstrap that node >> >> Am 12.11.2016 22:48 schrieb "sat" : >> >> Hi, >> >> We are planning to install 3 node cluster in production environment. Is >> it possible to provide weightage or priority to the nodes in cluster. >> >> Eg., We want more more records to be written to first 2 nodes and less to >> the 3rd node. We are thinking of this approach because we want to install >> other IO intensive messaging server in the 3rd node, in order to reduce the >> load we are requesting for this approach. >> >> >> Thanks and Regards >> A.SathishKumar >> >> >> -- > Ben Bromhead > CTO | Instaclustr > +1 650 284 9692 > Managed Cassandra / Spark on AWS, Azure and Softlayer > -- A.SathishKumar 044-24735023 --001a113dc588e0dfd505412369d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Thanks all for your valuable sugges= tion.

Thanks and Regards
A.SathishKumar<= /div>

On Sat= , Nov 12, 2016 at 2:59 PM, Ben Bromhead <ben@instaclustr.com> wrote:
+1 w/ Benjami= n.=C2=A0

However if you wish to make use of spare hardwa= re capacity, look to something like mesos DC/OS or kubernetes. You can run = multiple services across a fleet of hardware, but provision equal resources= to Cassandra and have somewhat reliable hardware sharing mechanisms.

On Sat, 12 Nov 2016 at 14:12 Jon Haddad <jonathan.haddad@gma= il.com> wrote:
Agreed w/ Benjamin.=C2=A0 Trying to di= agnose issues in prod will be a nightmare.=C2=A0 Keep your DB servers homog= eneous. =C2=A0

=
On Nov 12, 2016, at 1:52 PM, Benjamin Roth <benjamin.roth@jaumo.com> wrote:

1. From a 15 year experi= ence of running distributed Services: dont Mix Services on machines if you = don't have to. Dedicate each server to a single task if you can afford = it. It is easier to manage and reduces risks in case of overload or failure=
2. You can assign a different number of tokens for each node by setting thi= s in Cassandra.yaml before you bootstrap that node


Am 12.11.2016 22:48 schrieb "sat" <sathish.alwar@gmail.com>:
Hi,
<= div class=3D"m_-6942480627107961646gmail_msg">
We ar= e planning to install 3 node cluster in production environment. Is it possi= ble to provide weightage or priority to the nodes in cluster.=C2=A0

Eg., W= e want more more records to be written to first 2 nodes and less to the 3rd= node. We are thinking of this approach because we want to install other IO= intensive messaging server in the 3rd node, in order to reduce the load we= are requesting for this approach.


Thanks and Regards
A.SathishKumar


--
=
Ben Bromhead
CTO |=C2=A0Instaclustr
Managed Cassandra / Spark on AWS, Azure and Softlayer
=



--
A.Sathi= shKumar
044-24735023
--001a113dc588e0dfd505412369d2--