Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CABMBZ=kf2Umbn8HqbfNuU17Vvuqzhe_5v1mrYhXy3Ji1-0STyg@mail.gmail.com>
References: 
 <CABMBZ=kf2Umbn8HqbfNuU17Vvuqzhe_5v1mrYhXy3Ji1-0STyg@mail.gmail.com>
Date: Sun, 8 Nov 2015 09:36:54 -0800
Message-ID: 
 <CABMBZ==L+oi9myKrCv+2U5KHbKMaSy+_z+WL5LHheUAMkq0umQ@mail.gmail.com>
Subject: Re: Zookeeper down before query starts/after query finishes
From: Hsuan Yi Chu <hyichu@maprtech.com>
To: dev@drill.apache.org
Content-Type: multipart/alternative; boundary=001a114da6ea2f2c6f05240aec25

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

I just submitted a pull request to address DRILL-3751, which focuses on the
scenario where query already finishes and zookeeper dies. So Foreman cannot
delete the profiles of running queries in zookeeper.

I think in this case, after a few retries, Foreman can assume Zookeeper is
down. And, this query is assumed to fail since client might not be able to
receive the result (see the behavior in DRILL-3751
<https://issues.apache.org/jira/browse/DRILL-3751>).

Does this make sense?


On Fri, Nov 6, 2015 at 10:43 AM, Hsuan Yi Chu <hyichu@maprtech.com> wrote:

> My understanding is :
> Before query starts/After query finishes, Foreman will put/delete running
> query profiles in zookeeper.
>
> However, if zookeeper is down before the put/delete is successful, Drill
> would be blocked at the put/delete operation.
>
> See https://issues.apache.org/jira/browse/DRILL-3751
>
> I think it is not quite right to let Drill just wait for Zookeeper to
> respond. Does it make sense to use "time-out" here?
>
>
>

--001a114da6ea2f2c6f05240aec25--