From user-return-11698-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Wed Sep 19 11:05:02 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3CAA4180621 for ; Wed, 19 Sep 2018 11:05:02 +0200 (CEST) Received: (qmail 1508 invoked by uid 500); 19 Sep 2018 09:05:01 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 1493 invoked by uid 99); 19 Sep 2018 09:05:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2018 09:05:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CED7E180A55 for ; Wed, 19 Sep 2018 09:04:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.88 X-Spam-Level: * X-Spam-Status: No, score=1.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_SHORT=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=tink.se Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ZYPWA-MsEVo4 for ; Wed, 19 Sep 2018 09:04:58 +0000 (UTC) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 5B1A75F46D for ; Wed, 19 Sep 2018 09:04:58 +0000 (UTC) Received: by mail-oi0-f52.google.com with SMTP id m11-v6so4415807oic.2 for ; Wed, 19 Sep 2018 02:04:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tink.se; s=tink; h=mime-version:from:date:message-id:subject:to; bh=XuCoRQd7gh7p5owxO+2x3SBFXK4EGR93EBvfRoOr7Lg=; b=b5/hPMZYF9ZHQfNHH43dfI7rdz0mPuPDWFfAnCuRPTu82MZWwSCnPwcCnrUX5QmidS QUjIQX5PhpQZG2kOm/N4jQmrrcnvghN743AIMWejdzOzNudXH7iYN9PNADUbZyFZyYlK CVvDex/faaOD2Cx9UrHwflSHQ+cLBki3WX/iw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=XuCoRQd7gh7p5owxO+2x3SBFXK4EGR93EBvfRoOr7Lg=; b=cfQhHVegN6OM6A14nGv3Jr6l0h/j01ZSARrcd1/1x7lBaQIOucIw3Cl+d+2csJbeOa j5h5odx81B+TeUhNC0llbEGm0gKdQqryx4eq5tdfQuWB5jqqrtA7vgUYMdWOtn4HNpAm HhyuPa1qYw7ws7F0q6dHqtPINS0WokSUqhZhkgqySkteSFNhIQdsteQu2/EeFkH0uEGl LN+ooI0Y7y8NXtZ+hr9TNYaWtvBseBwcVVCScrrwpgE/hqp/UrcGx2ELTKQKcmeVHuo7 l3IgYn/a5LHgixzuta10DR692y5GpizB7JZf4ppPpdJHyS9cPd4ABuTLAzxsSId2xQsm pBcg== X-Gm-Message-State: APzg51CgqslXEAmzbRxAyYMDmCVPSAoW8XBOrnQ/lrsDGsImL2kXOkdO 7ZYLvDObdeoit3tDFuJ6ETuaV1LD4fuUZW6/UZIb12Z72J/iAA== X-Google-Smtp-Source: ANB0VdZSAypruphuGGGf0tugmbvnNPf454LE6A9DAwlclk5b5pTa9rvgHrWvj4Fu0Aw7uI20LPm7Ie6f3dpAJvh3+Ks= X-Received: by 2002:a54:4784:: with SMTP id o4-v6mr983720oic.101.1537347897333; Wed, 19 Sep 2018 02:04:57 -0700 (PDT) MIME-Version: 1.0 From: Jens Rantil Date: Wed, 19 Sep 2018 11:04:46 +0200 Message-ID: Subject: Healthcheck To: "" Content-Type: multipart/alternative; boundary="00000000000051304d057635b389" --00000000000051304d057635b389 Content-Type: text/plain; charset="UTF-8" Hello, We are in need for a shell command that we can execute on a specific node to make sure that the node has come up and has synced up with the ensemble. Is there any such command? Currently we are doing curl --silent --show-error --fail http://localhost:8080/commands/stat | grep -qE '"server_state" : "(follower|leader)"' but I suspect that that only takes the master election into account and not the fact that we've synced up. Anyone that has a better solution? One idea would to wait for `initLimit*tickTime+someDelta` ms and make sure that the same Java system process is still running. I also notice that the official Kubernetes Helm chart simply is doing an `ruok` 4-letter command for ready and liveness check. Any input appreciated - thanks, Jens -- Jens Rantil Backend engineer Tink AB Email: jens.rantil@tink.se Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter --00000000000051304d057635b389--