Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 462E7188B9 for ; Sun, 6 Mar 2016 05:25:11 +0000 (UTC) Received: (qmail 93175 invoked by uid 500); 6 Mar 2016 05:25:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93124 invoked by uid 500); 6 Mar 2016 05:25:08 -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 93114 invoked by uid 99); 6 Mar 2016 05:25:07 -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; Sun, 06 Mar 2016 05:25:07 +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 88C9DC0478 for ; Sun, 6 Mar 2016 05:25:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 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_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 2TVkvAvCeDwW for ; Sun, 6 Mar 2016 05:25:05 +0000 (UTC) Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 2A0045F39A for ; Sun, 6 Mar 2016 05:25:05 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id rt7so81502837obb.3 for ; Sat, 05 Mar 2016 21:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=2NaccAOKo5d0a3tDGEH6muHypGI7w5uPI4mRoZWoO6U=; b=0auLf0gLVdFlUtAFlPUihH4IatKOOMBONyyxs7HpC/taOPZjKdrxK6OpyxHxFpCAuR 6LwXYsDL1Ed/sz5GyUwxprRTtkMDBg1ZdJJYjj3jn678ONqfH/Ihbb2kdYnFw8mHRBMv cXIXl1JW99AyNV+NZ8i+aeCTtkAb20Jvc/mOikpfp1udL+96QELF20k/EcsTPXPXWMc6 BRG1G5p2SHHXYa8skzcwMbOHrUoBr988umvBfPxICy6wzEjTG2HWPmZhXsRefxY+02sJ s0ix1XDpPgpltpYd38q7pCfANE36722YcU7ni00Ejx0OMv6wNB4n9rrqCks7/sysfhGe y9dA== 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:date :message-id:subject:from:to; bh=2NaccAOKo5d0a3tDGEH6muHypGI7w5uPI4mRoZWoO6U=; b=IoeGJ5tfc/MFWZ9JNqPfcCPqvWUpuitse5Ia2MngbihlEVYb40NrrQMloKI7NGz98D awdxscbZP/t9xBEEskjotkynmZnzsRtGbp2+ICWjZRtkp6iGw7odnjL8R7XY/Pvm/rre EdkfDx40gNUZOk53kWOCO0khxc1BSlPC0LQxOT4EKJ3sw97c8rXrwlxsHXYtdU7xrZf8 grdL/akUV/p/OrvBjnKM5N3mPSLscwzenv9e6CXJ7wprsGh/XaQEi58nySkLc7Odk7kZ zea4oqp0fN4yrC09QeqN9rf9ftYeRLwZNhyL32KH8qprviMs8pqYAp9/h1AenvoqcYa/ EPIw== X-Gm-Message-State: AD7BkJJKmTQnYW3KpGk7sjxtrhdrqJPdQebDwG5Aa40FL54J4t5APjVKAujfEWQ/4kSW8KfdVB0gqNgNkjT8zQ== MIME-Version: 1.0 X-Received: by 10.60.82.229 with SMTP id l5mr10457527oey.6.1457241903950; Sat, 05 Mar 2016 21:25:03 -0800 (PST) Received: by 10.202.102.32 with HTTP; Sat, 5 Mar 2016 21:25:03 -0800 (PST) Received: by 10.202.102.32 with HTTP; Sat, 5 Mar 2016 21:25:03 -0800 (PST) In-Reply-To: References: <156AA069D74CB042AA529A6900665253248ABE8F@CO1PRD6102MB001.025d.mgd.msft.net> Date: Sun, 6 Mar 2016 10:55:03 +0530 Message-ID: Subject: Re: How to create an additional cluster in Cassandra exclusively for Analytics Purpose From: Bhuvan Rawal To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b6725dc097c1c052d5a92c4 --047d7b6725dc097c1c052d5a92c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks Sean and Nirmallaya. @Jack, We are going with DSC right now and plan to use spark and later solr over the analytics DC. The use case is to have olap and oltp workloads separated and not intertwine them, whether it is achieved by creating a new DC or a new cluster altogether. From Nirmallaya's and Sean's answer I could understand that its easily achievable by creating a separate DC, app client will need to be made DC aware and it should not make a coordinator in dc3. And same goes for spark configuration, it should read from 3rd DC. Correct me if I'm wrong. On Mar 4, 2016 7:55 PM, "Jack Krupansky" wrote: > > DataStax Enterprise (DSE) should be fine for three or even four data centers in the same cluster. Or are you talking about some custom Solr implementation? > > -- Jack Krupansky > > On Fri, Mar 4, 2016 at 9:21 AM, wrote: >> >> Sure. Just add a new DC. Alter your keyspaces with a new replication factor for that DC. Run repairs on the new DC to get the data streamed. Then make sure your clients only connect to the DC(s) that they need. >> >> >> >> Separation of workloads is one of the key powers of a Cassandra cluster. >> >> >> >> You may want to look at different configurations for the analytics cluster =E2=80=93 smaller replication factor, more memory per node, more di= sk per node, perhaps less vnodes. Others may chime in with their experience. >> >> >> >> >> >> Sean Durity >> >> >> >> From: Bhuvan Rawal [mailto:bhu1rawal@gmail.com] >> Sent: Friday, March 04, 2016 3:27 AM >> To: user@cassandra.apache.org >> Subject: How to create an additional cluster in Cassandra exclusively for Analytics Purpose >> >> >> >> Hi, >> >> >> >> We would like to create an additional C* data center for batch processing using spark on CFS. We would like to limit this DC exclusively for Spark operations and would like to continue the Application Servers to continue fetching data from OLTP. >> >> >> >> Is there any way to configure the same? >> >> >> >> >> =E2=80=8B >> >> Regards, >> >> Bhuvan >> >> >> ________________________________ >> >> The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment. > > --047d7b6725dc097c1c052d5a92c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks Sean and Nirmallaya.

@Jack, We are going with DSC right now and plan to use spark= and later solr over the analytics DC. The use case is to have=C2=A0 olap a= nd oltp workloads separated and not intertwine them, whether it is achieved= by creating a new DC or a new cluster altogether. From Nirmallaya's an= d Sean's answer I could understand that its easily achievable by creati= ng a separate DC, app client will need to be made DC aware and it should no= t make a coordinator in dc3. And same goes for spark configuration, it shou= ld read from 3rd DC. Correct me if I'm wrong.

On Mar 4, 2016 7:55 PM, "Jack Krupansky" <jack.krupansky@gmail.com> wro= te:
>
> DataStax Enterprise (DSE) should be fine for three or even four data c= enters in the same cluster. Or are you talking about some custom Solr imple= mentation?
>
> -- Jack Krupansky
>
> On Fri, Mar 4, 2016 at 9:21 AM, <SEAN_R_DURITY@homedepot.com> wrote:
>>
>> Sure. Just add a new DC. Alter your keyspaces with a new replicati= on factor for that DC. Run repairs on the new DC to get the data streamed. = Then make sure your clients only connect to the DC(s) that they need.
>>
>> =C2=A0
>>
>> Separation of workloads is one of the key powers of a Cassandra cl= uster.
>>
>> =C2=A0
>>
>> You may want to look at different configurations for the analytics= cluster =E2=80=93 smaller replication factor, more memory per node, more d= isk per node, perhaps less vnodes. Others may chime in with their experienc= e.
>>
>> =C2=A0
>>
>> =C2=A0
>>
>> Sean Durity
>>
>> =C2=A0
>>
>> From: Bhuvan Rawal [mailto:= bhu1rawal@gmail.com]
>> Sent: Friday, March 04, 2016 3:27 AM
>> To: user@cassandra.ap= ache.org
>> Subject: How to create an additional cluster in Cassandra exclusiv= ely for Analytics Purpose
>>
>> =C2=A0
>>
>> Hi,
>>
>> =C2=A0
>>
>> We would like to create an additional C* data center for batch pro= cessing using spark on CFS. We would like to limit this DC exclusively for = Spark operations and would like to continue the Application Servers to cont= inue fetching data from OLTP.=C2=A0
>>
>> =C2=A0
>>
>> Is there any way to configure the same?
>>
>> =C2=A0
>>
>>
>> =E2=80=8B
>>
>> Regards,
>>
>> Bhuvan
>>
>>
>> ________________________________
>>
>> The information in this Internet Email is confidential and may be = legally privileged. It is intended solely for the addressee. Access to this= Email by anyone else is unauthorized. If you are not the intended recipien= t, any disclosure, copying, distribution or any action taken or omitted to = be taken in reliance on it, is prohibited and may be unlawful. When address= ed to our clients any opinions or advice contained in this Email are subjec= t to the terms and conditions expressed in any applicable governing The Hom= e Depot terms of business or client engagement letter. The Home Depot discl= aims all responsibility and liability for the accuracy and content of this = attachment and for any damages or losses arising from any inaccuracies, err= ors, viruses, e.g., worms, trojan horses, etc., or other items of a destruc= tive nature, which may be contained in this attachment and shall not be lia= ble for direct, indirect, consequential or special damages in connection wi= th this e-mail message or its attachment.
>
>

--047d7b6725dc097c1c052d5a92c4--