Received: by 10.50.195.169 with SMTP id if9mr905756igc.0.1347453641033;
        Wed, 12 Sep 2012 05:40:41 -0700 (PDT)
X-BeenThere: percona-discussion@googlegroups.com
Received: by 10.50.51.234 with SMTP id n10ls5759915igo.3.canary; Wed, 12 Sep
 2012 05:40:40 -0700 (PDT)
Received: by 10.50.36.199 with SMTP id s7mr7869031igj.3.1347453640236;
        Wed, 12 Sep 2012 05:40:40 -0700 (PDT)
Received: by 10.50.36.199 with SMTP id s7mr7869030igj.3.1347453640225;
        Wed, 12 Sep 2012 05:40:40 -0700 (PDT)
Return-Path: <danillo...@gmail.com>
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169])
        by gmr-mx.google.com with ESMTPS id vb5si1557713igb.0.2012.09.12.05.40.40
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 12 Sep 2012 05:40:40 -0700 (PDT)
Received-SPF: pass (google.com: domain of danillo...@gmail.com designates 209.85.214.169 as permitted sender) client-ip=209.85.214.169;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of danillo...@gmail.com designates 209.85.214.169 as permitted sender) smtp.mail=danillo...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f169.google.com with SMTP id x4so2496057obh.28
        for <percona-discussion@googlegroups.com>; Wed, 12 Sep 2012 05:40:40 -0700 (PDT)
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
         :content-type;
        bh=LRxuuWo7M8+mC8S0W/baOhmPpY/ZbGvI/tKEAohjYEY=;
        b=Xmfr2mfXtOEpt4X/Pq8TsBGAiJZwJUMB5DFmS+PlmYmnZjDTRz1zmpxjirpJH/DFAZ
         ctyJSxBalORjxzngrjz9DY8zM+rKfi5CaiPmTyTu6wkGKpFvKTOwJH4H/QrDqmPysfyT
         qIaj3ygvERtxb5iVm3XCkKQuFMB5ERR9nRXUfQwNh0n1eADiYzmofPNVyemvGXIo0xmC
         dUQwT4iLhBrJpVN8h5qMsHaacfBdIflNKVbkTCIIUJ8sxKmraPOeTnAToZMB0H+NSXfV
         cAjeSvjQsmFN4Py0vjII/LBxtCSX1Ztl1ibQaU6CLBfgsxpbGdBU/g5oJRALi4Dz2aF5
         c1TA==
Received: by 10.182.49.7 with SMTP id q7mr22140258obn.68.1347453639978; Wed,
 12 Sep 2012 05:40:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.138.134 with HTTP; Wed, 12 Sep 2012 05:40:18 -0700 (PDT)
In-Reply-To: <8B8D5200-1413-42CC-853E-57617379B...@percona.com>
References: <e51308fe-dccc-45be-aeeb-bef5d8b2c445@googlegroups.com>
 <CAJM9iN1PWONgcGMD4d00OMx-iAE9Wc+75ym535TsinAk2hi...@mail.gmail.com> <8B8D5200-1413-42CC-853E-57617379B...@percona.com>
From: Danillo Souza <danillo...@gmail.com>
Date: Wed, 12 Sep 2012 09:40:18 -0300
Message-ID: <CAP9UwnzwS_m9fieyr+=yyBUcCs-K1L-hUe5k3iBOkefYa0M...@mail.gmail.com>
Subject: Re: XtraDB Cluster and long running Business Intelligence queries
To: percona-discussion@googlegroups.com
Content-Type: text/plain; charset=UTF-8

Alejandro,


have you tried to use columnar database for BI propose?

I think you gonna get a better performance with it.


Danillo Souza

2012/9/11 Jay Janssen <jay.jans...@percona.com>:
> My only concern would be long running queries on the third node gathering
> enough row locks to trigger the situation described here:
> http://www.mysqlperformanceblog.com/2012/08/17/percona-xtradb-cluster-multi-node-writing-and-unexpected-deadlocks/
>
>
>
> On Sep 11, 2012, at 1:56 PM, Justin Swanhart <greenl...@gmail.com> wrote:
>
> As long as you are using InnoDB tables, then readers won't block
> writers, that is, writes on node A won't be blocked by reads on node
> A, B or C.
>
> I'd suggest that you use a three node cluster, use HA proxy to direct
> OLTP read/writes to one or two nodes and BI requests to the third
> node.  The BI workload likely has a different working set from the
> OLTP workload, which is why I suggest you send BI queries to a
> dedicated node.
>
> --Justin
>
>
> Jay Janssen, Senior MySQL Consultant, Percona Inc.
> http://about.me/jay.janssen
> Percona Live in NYC Oct 1-2nd: http://www.percona.com/live/nyc-2012/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Percona Discussion" group.
> To post to this group, send email to percona-discussion@googlegroups.com.
> To unsubscribe from this group, send email to
> percona-discussion+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/percona-discussion?hl=en.