I stand corrected on one point (Thanks, Sorabh!): the Drill web server does
have a session timeout, configurable in boot options, that defaults to one hour.
- Paul
> On Jun 23, 2017, at 2:10 PM, Paul Rogers wrote:
>
> Hi John,
>
> Your use case is interesting. I’m certainly
LOL. Let me try again.
https://issues.apache.org/jira/browse/DRILL-5584
Best regards,
Rob
-Original Message-
From: Kunal Khatua [mailto:kkha...@mapr.com]
Sent: Friday, June 23, 2017 11:38 AM
To: user@drill.apache.org
Subject: RE: Apache Drill C++ Client Binary Versioning Information
I
I think you missed sharing the Apache JIRA :)
From: Robert Wu [mailto:r...@magnitude.com]
Sent: Thursday, June 22, 2017 5:19 PM
To: user@drill.apache.org
Subject: RE: Apache Drill C++ Client Binary Versioning Information
Oh sorry, looks like attachment is not going through.
I've captured the
Oh sorry, looks like attachment is not going through.
I've captured the information in this JIRA.
Best regards,
Rob
From: Robert Wu
Sent: Tuesday, June 13, 2017 12:07 PM
To: 'user@drill.apache.org'
Subject: Apache Drill C++ Client Binary Versioning Information
Hi
That makes sense, ya, I would love to hear about the challenges of this in
general from the Drill folks.
Also, I wonder if Paul R at MapR has any thoughts in how something like
this would be handled in the Drill on Yarn Setup.
John
On Fri, Jun 23, 2017 at 10:58 AM, Keys Botzum
I think we are on the same page regarding SSL.
Regarding (1) it's best that I defer to the drill experts but I will mention
that sharing session state can greatly complicate scalability. Since switching
drillbits should be a rare event, it is probably more scalable to send back to
the client a
So a few things
1. The issue is that as is, SSL stuff works fine, but when the IP address
that DNS returns for the hostname changes, the session is invalidated and I
am forced to logon again... this is annoying and loses session context
information. If I try to lay out my cluster differently,
There is something here I'm not understanding. In the below the hostname is
always the same so there should be no problem as long as all drillbits share a
common signer.
I'm also just not following how certificate authentication issues are even
linked to the Drill session issues. Whether or
The wild card certificate isn't a problem on it's own, it's using it in a
manner that allows me to maintain all of the various features I want. Let
me lay this out,
In marathon I have a task, it runs a drill bit. Since that task is located
at the node prod/drillprod (for my env it's
Why is a wildcard certificate a problem? They are quite common. One just needs
all of the Drillbits to share a common domain for the wildcard to be easy and
thus avoid having to list individual hosts.
Are you saying that you can't use hostnames and must use IPs?
In case I'm not clear, here's
10 matches
Mail list logo