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 E66D91069 for ; Tue, 19 Apr 2011 13:02:39 +0000 (UTC) Received: (qmail 96752 invoked by uid 500); 19 Apr 2011 13:02:34 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96730 invoked by uid 500); 19 Apr 2011 13:02:34 -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 96722 invoked by uid 99); 19 Apr 2011 13:02:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 13:02:34 +0000 X-ASF-Spam-Status: No, hits=-0.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.32.180.16] (HELO VA3EHSOBE007.bigfish.com) (216.32.180.16) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2011 13:02:27 +0000 Received: from mail59-va3-R.bigfish.com (10.7.14.240) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.8; Tue, 19 Apr 2011 13:02:05 +0000 Received: from mail59-va3 (localhost.localdomain [127.0.0.1]) by mail59-va3-R.bigfish.com (Postfix) with ESMTP id 3E8BC8382D3 for ; Tue, 19 Apr 2011 13:02:05 +0000 (UTC) X-SpamScore: 6 X-BigFish: VS6(zz2387nzz1202hzz8275bh8275dhz2dh87h2a8h668h839h61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: KIP:(null);UIP:(null);IPVD:NLI;H:IE2RD2HUB024.red002.local;RD:none;EFVD:NLI X-FB-DOMAIN-IP-MATCH: fail Received: from mail59-va3 (localhost.localdomain [127.0.0.1]) by mail59-va3 (MessageSwitch) id 1303218124955905_30234; Tue, 19 Apr 2011 13:02:04 +0000 (UTC) Received: from VA3EHSMHS009.bigfish.com (unknown [10.7.14.244]) by mail59-va3.bigfish.com (Postfix) with ESMTP id E640D1728050 for ; Tue, 19 Apr 2011 13:02:04 +0000 (UTC) Received: from IE2RD2HUB024.red002.local (213.199.187.153) by VA3EHSMHS009.bigfish.com (10.7.99.19) with Microsoft SMTP Server (TLS) id 14.1.225.8; Tue, 19 Apr 2011 13:02:01 +0000 Received: from IE2RD2XVS021.red002.local ([10.33.56.25]) by IE2RD2HUB024.red002.local ([10.43.198.102]) with mapi; Tue, 19 Apr 2011 06:01:56 -0700 From: Roland Gude To: "user@cassandra.apache.org" Date: Tue, 19 Apr 2011 06:01:54 -0700 Subject: AW: AW: Two versions of schema Thread-Topic: AW: Two versions of schema Thread-Index: Acv95XfaGldXw4ShSG2QgkThrUSoCQAq+pCg Message-ID: <120CB7532EA53A4D8CA6B63F94B4ADB351E6D631A4@IE2RD2XVS021.red002.local> References: <1302894224705-6277365.post@n2.nabble.com> <120CB7532EA53A4D8CA6B63F94B4ADB351E6D630C9@IE2RD2XVS021.red002.local> <1303143993908-6284276.post@n2.nabble.com> In-Reply-To: <1303143993908-6284276.post@n2.nabble.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Yeah it happens from time to time even if everything seems to be fine that = schema changes don't work correctly. But it's always repairable with the de= scribed procedure. Therefore the operator being available is a must have I = think. Drain is a nodetool command. The node flushes data and stops accepting new = writes. This just speeds up bringing the node back up again in this case. P= robably a flush is equally acceptable. -----Urspr=FCngliche Nachricht----- Von: mcasandra [mailto:mohitanchlia@gmail.com]=20 Gesendet: Montag, 18. April 2011 18:27 An: cassandra-user@incubator.apache.org Betreff: Re: AW: Two versions of schema In my case all hosts were reachable and I ran nodetool ring before running the schema update. I don't think it was because of node being down. I tihnk for some reason it just took over 10 secs because I was reducing key_cache from 1M to 1000. I think it might be taking long to trim the keys hence 10 sec default may not be the right way. What is drain? -- View this message in context: http://cassandra-user-incubator-apache-org.30= 65146.n2.nabble.com/Two-versions-of-schema-tp6277365p6284276.html Sent from the cassandra-user@incubator.apache.org mailing list archive at N= abble.com.