drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Parth Chandra <pchan...@maprtech.com>
Subject Re: Drill HTTP Sessions Across Bits
Date Wed, 08 Jun 2016 17:21:20 GMT
Are you doing this for load balancing? The Apache web server's
mod_proxy_balancer [1] might be a good place to look for a general purpose
solution. Essentially, it will route your first request to a particular
drillbit and then maintain session stickiness by routing all subsequent
requests from the client to the same drillbit.

[1] https://httpd.apache.org/docs/2.4/mod/mod_proxy_balancer.html

On Tue, Jun 7, 2016 at 10:58 AM, John Omernik <john@omernik.com> wrote:

> I have a setup where I can reference my drillbits by the name
> drillbits.zeta this DNS name resolves to any of the drillbits running.  It
> returns IPs for all bits, but it's round robin ish (differing order) I
> "think" this is causing issues like short timeouts in my web connections
> and rest API things. For example, long queries etc.
> Can/should be able to handle request to any bit with a session id known to
> all bits?  For example, if I send request one to bit1 it responds, and the
> next time, (given the proper cookies/session IDs) I send a request to the
> same name, but due to DNS it's routed to bit2?   I suppose this would
> require saving HTTP session state in something like Zookeeper... would that
> even be possible?   I am exploring other options too, just trying to figure
> out what the Drill folks say on the subject.
> John

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