Thanks for doing the follow-up! I'll gradually enable the option on our
clusters sometime next week and let you know if we hit any issues.
Assuming we don't run into any roadblocks: How about changing the
default of `-zk_use_curator` from False to True for the next release?
Then we cane make signi
I had a short look at the code. It seems like there is no support for
SOCKS proxies, at least not out of the box.
Our client speaks to the scheduler using HTTP. It supports two
connections mechanisms, both realized via subclasses of SchedulerClient
[1]:
* ZookeeperSchedulerClient: It gets the le
Personally, I would not mind if we drop the executor overhead
completely and ask the users add it on their own. We would probably
have to enforce a minimal task size to prevent Thermos OOMs, but that
should not be a big problem.
On Mi, 2016-09-07 at 16:41 -0400, Rick Mangi wrote:
> > > > > > One
Hi,
would it be possible to show us your relevant scheduler configuration
and your ini file? This will make it easier to reproduce the issue.
Thanks,
Stephan
On Do, 2016-10-13 at 17:58 +, Ajmera, Jatan wrote:
>
>
>
> Hi,
>
>
> > > I was previously communicating about this issue on the
is confirms my concern about adding auth support on only
> one side of the CLI/Scheduler :)
>
> On Sun, Oct 16, 2016 at 9:46 AM, Stephan Erb wrote:
> > Hi,
> >
> > would it be possible to show us your relevant scheduler
> > configuration and your ini file? This wi
Yeah, see https://github.com/apache/aurora/blob/master/docs/operations/
security.md#http-basic-authentication
On So, 2016-10-16 at 10:26 -0700, David McLaughlin wrote:
> > I *just* seen that in the e2e test. Have we documented that
anywhere?
>
> > > On Sun, Oct 16, 2016 at 10:
Hi Mohit,
I believe you are running into a form of
https://issues.apache.org/jira/browse/AURORA-1596. Assuming it is the same
cause, you might try to increase the lock timeout introduced in the linked
issue.
As a much more viable solution, I would recommend to update to 0.19 though:
Aurora do
> Q1: Does Aurora use COMMAND or DEFAULT executor?
Aurora is currently using neither. In Mesos terms Thermos is a CUSTOM executor.
On top, Aurora supports alternative custom executors [1] such as the Docker
compose executor [2].
Mesos seems to be betting on the new DEFAULT executor. It should b
Hi Miguel,
I believe you are running into a current limitation of the observer: The
executor checkpoints its process PIDs to disk and the observer reads them. The
observer then tries to get process statistics for each PID. If those live
within a PID namespace, then the observer won’t be able to
Hey Renan,
thanks again for bringing this up. In my experience, the pain comes from
building, testing & voting rather the packaging scripts themselves. I therefore
think we should discontinue building, but continue to maintain the scripts so
that users can build them on their own when necessary
Thanks for driving this effort! I am looking forward to the change, as
it hopefully makes it easier for new contributors.
On Tue, 2018-06-19 at 13:21 -0700, Renan DelValle wrote:
> All,
>
> The vote to move from the legacy ASF git hosting to the GitBox service has
> passed. When we finish our mo
Same for me, I will try to keep up with code reviews as good as I can.
Should we consider posting RB links and Github PRs to the mailinglist if they
failto attract reviews within 2 days? This acts as a reminder for the assigned
reviewers andwill attract the urgently needed additional reviewers.
Supporting both versions temporarily for one release might be helpful for a
seamless upgrade path.However, of that is too much effort going directly to
Python 3 sounds okay to me as well.
There are a few complications with Thrift though. I have left some details on
the github issue.
Thanks for b
13 matches
Mail list logo
