Currently there is no limit. It is basically depends on jetty's
HashSessionManager. A quick glance through the HashSessionManager doesn't
reveal any API to control the max number of sessions. I will keep looking.
I just fixed the issue of resource leak. Resources are not released
properly when they
Venki,
Even for authenticated sessions, do we impose any kind of upper limit on
the number of concurrent connections? I seems like we should issue a
reasonable error message about an over-used Drillbit before the process
dies due to hitting the system file handle limit.
- Jason
On Thu, Feb 4, 20
Thanks Venki,
Let me know how I can help further.
> On Feb 2, 2016, at 10:23 PM, Venki Korukanti
> wrote:
>
> I think you made valid points. It makes sense to have session less REST
> calls in both auth enabled and disabled cases.
>
> In case of auth enabled:
> 1) Session-less calls can be aut
I think you made valid points. It makes sense to have session less REST
calls in both auth enabled and disabled cases.
In case of auth enabled:
1) Session-less calls can be authenticated using Basic auth (this was
already asked on mailing list sometime back) as a start and move onto token
based au
No, it wasn’t logging out, it was just stopping, obviously that caused dangling
sessions for the authenticated scenario.
I don’t think that a short timeout for anonymous sessions is a good way to go
for anonymous api calls. Session management isn’t what anybody would expect
when using a RES
When auth is *enabled*, is the worker process logging out after queries are
done? When auth is *disabled* can you set session_max_idle_secs in
drill.exec.http block in drill-override.conf to something like 30 (secs)
and try? This way anonymous sessions are closed quickly and not kept for
1hr (defau
I have a background worker process (on a server, not a browser) that kicks off
every minute or so and issues some queries sequentially to the rest query
endpoint.In 1.4 with no authentication this worked fine except that in 1
instance I need to issue a CTAS query with a different format (jso
Currently we keep the DrillClient per session. All the state is in Server
and DrillClient is the reference to reuse the state. DrillClient is
automatically closed when the session expires (default value is 1hr after
the last activity on session) or user explicitly logs out. I am trying to
understan
First: Im a total newb at contributing to apache projects so please excuse any
indiscretions, feel free to give comments on style or whatever, i take feedback
well. Thick skin too.
Ill give some background next and then a proposal.
Background:
I recently changed over to using authentication i
