Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D31B810586 for ; Thu, 20 Feb 2014 19:30:17 +0000 (UTC) Received: (qmail 5231 invoked by uid 500); 20 Feb 2014 19:30:17 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 5157 invoked by uid 500); 20 Feb 2014 19:30:16 -0000 Mailing-List: contact user-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.apache.org Delivered-To: mailing list user@helix.apache.org Received: (qmail 5150 invoked by uid 99); 20 Feb 2014 19:30:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 19:30:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of osgigeek@gmail.com designates 209.85.128.173 as permitted sender) Received: from [209.85.128.173] (HELO mail-ve0-f173.google.com) (209.85.128.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 19:30:09 +0000 Received: by mail-ve0-f173.google.com with SMTP id jw12so2276384veb.32 for ; Thu, 20 Feb 2014 11:29:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=AwzWQSyK2GXCyysLBRSEgWfZ73+vKE8YIIHdsVQX3nQ=; b=Dw5ziORaZfuKmlAmAxELDxM9HORpU6qr/X/wQ7m+ojthNnvGEn3W4sEbHKyoBl6nw7 XDnXkWw8YMROLo0aKjZ+/R2ZKk1d04lUhyc3+63TTa9X/cGRjIcypJuKsTMwP5/lHDBO vIqJGRBNmCJctT91m2p9h/s/z3MhPWVa1wcZFjyzZ5pJiqrWhgwFmiSQ/cvnf5Lv1iNk 71a3TYYf3fCW6DJf1NrlPm/Gf9mWo4RYD7GHGg972Rzw/g6DzWg0cSF00ZSZVFVCVJhp vmO3FowNubPfl6U0eX3SROHm12NbVEBX1c5zTXVfK3xjX29lvNQyh94jf6TO9m3TzfAF Wkog== MIME-Version: 1.0 X-Received: by 10.221.29.196 with SMTP id rz4mr2115328vcb.8.1392924589038; Thu, 20 Feb 2014 11:29:49 -0800 (PST) Received: by 10.220.90.80 with HTTP; Thu, 20 Feb 2014 11:29:48 -0800 (PST) In-Reply-To: References: Date: Thu, 20 Feb 2014 11:29:48 -0800 Message-ID: Subject: Re: Helix 0.6.2- Messages on startup From: Sandeep Nayak To: user@helix.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I probably missed it in the documentation, but how can I check the external view? Also, is there a time period after which the first node logs that it has identified itself as the leader? Just wanted to know what is the indicator that things work and I do have a leader and follower in the cluster? Thanks, Sandeep On Thu, Feb 20, 2014 at 9:34 AM, Kanak Biscuitwala wrote: > We didn't, but now we do. > ________________________________ >> Date: Thu, 20 Feb 2014 09:26:10 -0800 >> Subject: Re: Helix 0.6.2- Messages on startup >> From: g.kishore@gmail.com >> To: user@helix.apache.org >> >> Do we have a jira for this ? >> >> >> On Wed, Feb 19, 2014 at 11:20 PM, Kanak Biscuitwala >> > wrote: >> Hi Sandeep, >> >> Does Helix still generate an external view correctly despite these log >> messages? >> >> I believe the first message is a known issue: the callbacks are >> initialized once by the HelixManager implementation, and then >> initialized again when the controller becomes leader (for the first >> controller, these will happen very close to one another). It's >> generally a harmless message. >> >> The second one indicates that the controller is getting events (which >> path was changed to trigger the event?), but hasn't yet become leader. >> When it does, it will invoke the pipeline and do the right thing. >> >> I think in either case, a race is causing the log messages to appear, >> but it shouldn't affect the correctness of the Helix controller >> operation. >> >> Kanak >> >> Date: Wed, 19 Feb 2014 23:13:19 -0800 >> Subject: Helix 0.6.2- Messages on startup >> From: osgigeek@gmail.com >> To: user@helix.apache.org >> >> Hi guys, >> >> So I finally got my setup done with states etc. But when I start the >> first node I see the following messages >> >> expected types: [CALLBACK, FINALIZE] but was INIT >> I see this for /cluster/Controller, >> /cluster/INSTANCES/Instance/MESSAGES and several other paths. >> The other message I see is >> Cluster manager: first-node is not leader. Pipeline will not be invoked >> Any ideas on what I am missing here? >> Thanks, >> Sandeep >>