drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hsuan Yi Chu <hyi...@maprtech.com>
Subject Re: Zookeeper down before query starts/after query finishes
Date Sun, 08 Nov 2015 17:36:54 GMT
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

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?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message