Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
MIME-Version: 1.0
In-Reply-To: <0C8A8247-324D-444A-B968-D669A5DAC306@apache.org>
References: <CAPycdbozcOOZeWKabkj0pFEzvXniTLC_eOWPrEjCTts-Li21LA@mail.gmail.com>
 <0C8A8247-324D-444A-B968-D669A5DAC306@apache.org>
From: Ben Sherman <bensherman@gmail.com>
Date: Tue, 29 Nov 2016 17:10:18 -0800
Message-ID: <CAPycdbrK-7P6Eu9CEzM8FWrwBC7eR9-tJ2DG_cw57-eCkRrJSQ@mail.gmail.com>
Subject: Re: four letter commands not working as expected.
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=001a113d17dc7a46e205427a5f53
archived-at: Wed, 30 Nov 2016 01:10:47 -0000

--001a113d17dc7a46e205427a5f53
Content-Type: text/plain; charset=UTF-8

I expect if none of the 4 letter commands except ruok give a response, then
the server is definitively not okay.  ruup vs ruok maybe? We see the server
popping into a looking state quite often, and it's the cause of 100% of our
outages involving zookeeper.  This isn't an initial state, it's down until
a restart.

On Tue, Nov 29, 2016 at 3:08 PM, Flavio Junqueira <fpj@apache.org> wrote:

> It looks like the server is in the LOOKING state, so it is not serving
> request but it is up. I'd say that ruok should return imok as long as the
> server is up, it's not necessarily a health check.  We could review the
> semantics of the commands if this behavior and others are confusing.
>
> -Flavio
>
>
> > On 29 Nov 2016, at 19:54, Ben Sherman <bensherman@gmail.com> wrote:
> >
> > Four letter word ruok is returning imok when the server is decidedly not
> > okay - is this the expected behavior?
> >
> > bsherman@zk1:~$ nc localhost 2181 <<< mntr
> > This ZooKeeper instance is not currently serving requests
> > bsherman@zk1:~$ nc localhost 2181 <<< ruok
> > imok
> >
> > I'm running 3.4.9.
> >
> > --ben
>
>

--001a113d17dc7a46e205427a5f53--