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 0C9F917C9C for ; Thu, 14 May 2015 20:27:18 +0000 (UTC) Received: (qmail 10547 invoked by uid 500); 14 May 2015 20:27:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 10507 invoked by uid 500); 14 May 2015 20:27:14 -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 10497 invoked by uid 99); 14 May 2015 20:27:14 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2015 20:27:14 +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 C240CC0B1C for ; Thu, 14 May 2015 20:27:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.001 X-Spam-Level: **** X-Spam-Status: No, score=4.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id uZeM6xhum3XZ for ; Thu, 14 May 2015 20:27:04 +0000 (UTC) Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com [209.85.214.170]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 5075542996 for ; Thu, 14 May 2015 20:27:04 +0000 (UTC) Received: by obcus9 with SMTP id us9so61723217obc.2 for ; Thu, 14 May 2015 13:26:13 -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=RPMlZtWMIRK6D/AJ+GuPPWUu0NvTTNhDhAasVEnVEZU=; b=B/fKgo0EAunVkEqE8UUDjGnLGzOCrZe2k8MMdWCRvbYU1HRqbpo9Wi+P8AQoAvYW8w x2dCG8WuZeBwGkd9BGnXb8CkcRfCK1vP73dZPiFhgI+u0SVEHIdTv9oQcWKGXaC9t2tw nuL6xuRp5H88m7QzYan5ArQ3WN3PQJBnBYZxWShqOtWC1anK98mxvU0CRruoeu5LMCiu niYBVckodOokrvB2gAmmFVvfaasdmueJLfr7yMdnh0+UsEQS7CGmBlIxyXqk5etdw//X DtVRGMSzwP71hvcuLLXdmz+Z61ppDxkr07JVROqOi1B0ojYSE21GzEswRA72YC9tku7Y sy2w== X-Gm-Message-State: ALoCoQmV4DjIhVlzhe84qSjP6n8sOFV381KsYX45RRoZUCiuxsz3X5VaMjAwDf6hh+mCm2530wb1 MIME-Version: 1.0 X-Received: by 10.182.44.199 with SMTP id g7mr5149201obm.28.1431635173421; Thu, 14 May 2015 13:26:13 -0700 (PDT) Received: by 10.202.214.206 with HTTP; Thu, 14 May 2015 13:26:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 May 2015 15:26:13 -0500 Message-ID: Subject: Re: Updating Table Schemas Slows Down Cluster From: Nate McCall To: Cassandra Users Content-Type: multipart/alternative; boundary=001a11c2e6c0f5c9380516108938 --001a11c2e6c0f5c9380516108938 Content-Type: text/plain; charset=UTF-8 You might be seeing the effects of https://issues.apache.org/jira/browse/CASSANDRA-9136 which was just fixed in 2.0.15. The connection thrashing from the above would definitely cause some hiccups. On Thu, May 14, 2015 at 3:10 PM, Christopher Kelly wrote: > Hi all, > > We're running a 24 node cluster and we've noticed that whenever we either > update an existing table or add a new table, the cluster's load increases > immensely during and after for about 1 minute, triggering a lot of read and > write timeouts. Has anyone seen this behavior before or have any ideas as > to why schema updates are such an intensive operation? We are running on > 2.0.10. > > Thanks, > Chris > -- ----------------- Nate McCall Austin, TX @zznate Co-Founder & Sr. Technical Consultant Apache Cassandra Consulting http://www.thelastpickle.com --001a11c2e6c0f5c9380516108938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You might be seeing the effects of=C2=A0https://issues.apache.org/ji= ra/browse/CASSANDRA-9136 which was just fixed in 2.0.15.=C2=A0

=
The connection thrashing from the above would definitely cause s= ome hiccups.=C2=A0

On Thu, May 14, 2015 at 3:10 PM, Christopher Kelly <= cekelly@cs.princeton.edu> wrote:
Hi all,

We're running a 24 no= de cluster and we've noticed that whenever we either update an existing= table or add a new table, the cluster's load increases immensely durin= g and after for about 1 minute, triggering a lot of read and write timeouts= .=C2=A0 Has anyone seen this behavior before or have any ideas as to why sc= hema updates are such an intensive operation? We are running on 2.0.10.

Thanks,
Chris



--
-----------------
Nate McCall
A= ustin, TX
@zznate

Co-Founder & Sr. Technical Consultant
Ap= ache Cassandra Consulting
http://www.thelastpickle.com
--001a11c2e6c0f5c9380516108938--