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 C94451077F for ; Tue, 11 Mar 2014 15:42:12 +0000 (UTC) Received: (qmail 79311 invoked by uid 500); 11 Mar 2014 15:42:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 79274 invoked by uid 500); 11 Mar 2014 15:42:09 -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 79265 invoked by uid 99); 11 Mar 2014 15:42:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 15:42:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_IMAGE_ONLY_28,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jlacefield@datastax.com designates 209.85.220.177 as permitted sender) Received: from [209.85.220.177] (HELO mail-vc0-f177.google.com) (209.85.220.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 15:42:04 +0000 Received: by mail-vc0-f177.google.com with SMTP id if17so5876525vcb.36 for ; Tue, 11 Mar 2014 08:41:43 -0700 (PDT) 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:content-type; bh=i8ssHTLFCxuivv55NKmPygGeZ4O9P8IAhixd2H7kECA=; b=bnrWkOCPI6MnBWGkZ2Hpa7Cqsk1eQ55iCMvq0bLOfbvgxqlkFFyiaSdIrZ2hb4ktFW 7r6Ce0ZqXXGxcn2SABK5Tg+FWyg1tCIn8ml84cJlZgC5ZKL/t9FTc8Zv28+34sKGZek6 ho8odzh3VVRcqGSVl1nKqjgZSg8lbHxTH+vSv7HJpbHQYOG9dPwsRHaQ4ZMKcIxbEMNS NraJZBynQD38u2viLSKHQg7/LtOXtTwXAb5dgPczT5GWPDzO0iCdrs7gA7Y1wqV1G1SK gPdMp6lLsv48MZCUp/2EnR8CXueUSL1QuE+i6qf5lV6SAwT6msOpLWEHZegqp3H+6PKo aBCw== X-Gm-Message-State: ALoCoQkjKMRJRpEAQkNJBqL8GaTpDOIDRKjLvCsg6H4EhvuR9/ONvOshTEYNUdgemvd+8PV8FK93 MIME-Version: 1.0 X-Received: by 10.220.136.6 with SMTP id p6mr28521638vct.9.1394552503558; Tue, 11 Mar 2014 08:41:43 -0700 (PDT) Received: by 10.53.4.3 with HTTP; Tue, 11 Mar 2014 08:41:43 -0700 (PDT) In-Reply-To: <1394551636.1522.93172657.21D0C6FD@webmail.messagingengine.com> References: <1394551636.1522.93172657.21D0C6FD@webmail.messagingengine.com> Date: Tue, 11 Mar 2014 11:41:43 -0400 Message-ID: Subject: Re: DSE Hadoop support for provisioning hardware From: Jonathan Lacefield To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a1134a13a9879b504f4568eca X-Virus-Checked: Checked by ClamAV on apache.org --001a1134a13a9879b504f4568eca Content-Type: text/plain; charset=ISO-8859-1 Hello, Not sure this question is appropriate for the Open Source C* users group. If you would like, please email me directly to discuss DataStax specific items. Thanks, Jonathan jlacefield@datastax.om Jonathan Lacefield Solutions Architect, DataStax (404) 822 3487 On Tue, Mar 11, 2014 at 11:27 AM, Ariel Weisberg wrote: > Hi, > > I am doing a presentation at Big Data Boston about how people are > bridging the gap between OLTP and ingest side databases and their > analytic storage and queries. One class of systems I am talking about > are things like HBase and DSE that let you run map reduce against your > OLTP dataset. > > I remember reading at some point that DSE allows you to provision > dedicated hardware for map reduce, but the docs didn't seem to fully > explain how that works.I looked at > > http://www.datastax.com/documentation/datastax_enterprise/4.0/datastax_enterprise/ana/anaStrt.html > > My question is what kind of provisioning can I do? Can I provision > dedicated hardware for just the filesystem or can I also provision > replicas that are dedicated to the file system and also serving reads > for map reduce jobs. What kind of support is there for keeping OLTP > reads from hitting the Hadoop storage nodes and how does this relate to > doing quorum reads and writes? > > Thanks, > Ariel > --001a1134a13a9879b504f4568eca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

=A0 Not sure this question is ap= propriate for the Open Source C* users group. =A0If you would like, please = email me directly to discuss DataStax specific items.

<= div> Thanks,

Jonathan


Jonathan L= acefield
Solutions Architect, DataStax
(404) 822 3487
<= br>





On Tue, Mar 11, 2014 at 11:27 AM, Ariel = Weisberg <ariel@weisberg.ws> wrote:
Hi,

I am doing a presentation at Big Data Boston about how people are
bridging the gap between OLTP and ingest side databases and their
analytic storage and queries. One class of systems I am talking about
are things like HBase and DSE that let you run map reduce against your
OLTP dataset.

I remember reading at some point that DSE allows you to provision
dedicated hardware for map reduce, but the docs didn't seem to fully explain how that works.I looked at
http://www.datastax.c= om/documentation/datastax_enterprise/4.0/datastax_enterprise/ana/anaStrt.ht= ml

My question is what kind of provisioning can I do? Can I provision
dedicated hardware for just the filesystem or can I also provision
replicas that are dedicated to the file system and also serving reads
for map reduce jobs. What kind of support is there for keeping OLTP
reads from hitting the Hadoop storage nodes and how does this relate to
doing quorum reads and writes?

Thanks,
Ariel

--001a1134a13a9879b504f4568eca--