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 E66B6D11A for ; Mon, 23 Jul 2012 04:00:06 +0000 (UTC) Received: (qmail 21252 invoked by uid 500); 23 Jul 2012 04:00:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 21036 invoked by uid 500); 23 Jul 2012 03:59:53 -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 21001 invoked by uid 500); 23 Jul 2012 03:59:52 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 20988 invoked by uid 99); 23 Jul 2012 03:59:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 03:59:51 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FSL_RCVD_USER,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of codevally@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 03:59:46 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1St9nq-0006eH-4l for cassandra-user@incubator.apache.org; Sun, 22 Jul 2012 20:59:26 -0700 Date: Sun, 22 Jul 2012 20:59:26 -0700 (PDT) From: Roshan To: cassandra-user@incubator.apache.org Message-ID: <1343015966083-7581380.post@n2.nabble.com> Subject: Cassandra Hector failover + load balancing not as expected with version 1.0-5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Currently I am using Cassandra 1.0.6 with Hector 1.0-5 in production, and now in the process of upgrading current Cassandra cluster to 1.1.2 version. As the first upgrade process, I select one node from local development Cassandra cluster (3 node 1.0.6 and RF=3) and execute the nodetool drain to empty the memtables and commit logs. During the drain, that node receive reads+writes from external java client (which uses hector 1.0-5 client) and immediately I am receiving a hector connection failure errors when drain starts. With the hector connection issues, the external client stops sending writes and it's also fails. Below show how I build up the connection with hector. Cluster cluster = HFactory.getOrCreateCluster("test-dev-cluster", "10.1.161.60,10.1.161.61,10.1.161.62"); Keyspace keyspace = HFactory.createKeyspace(getKeyValue(KEYSPACE_NAME_KEY), cluster); Other than the above 2 statements, I am passing any configuration to hector to build up the connections. What I noticed is, every time hector uses zero element from the server list url and still try to connect to the same server, if it fails. Could someone help me to solve this hector fail over? Thanks /Roshan -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-Hector-failover-load-balancing-not-as-expected-with-version-1-0-5-tp7581380.html Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.