Hello,
My question is how can we run with mesos 0.18.0 whereas requirement on
zookeeper are on an older version : 3.3.4 (mesos embed 3.4.3).
Actually I have problems tring to register on an existing mesos 0.18.2
cluster running.
When I try to run aurora on an existing cluster I get those logs on
On 10 July 2014 09:00, Damien Hardy wrote:
> Hello,
>
> My question is how can we run with mesos 0.18.0 whereas requirement on
> zookeeper are on an older version : 3.3.4 (mesos embed 3.4.3).
>
> Actually I have problems tring to register on an existing mesos 0.18.2
> cluster running.
> When I tr
Can you share the scheduler's command line arguments? This behavior would
present if the quorum size [1] is greater than the number of active
schedulers (or if the schedulers are unable to communicate).
[1]
https://github.com/apache/incubator-aurora/blob/master/docs/deploying-aurora-scheduler.md#
Quick question for the gang:
What's the right way to handle experimental branches? I've got a batch of
code that I'm not ready to send for review, but I'm getting on a plane
tomorrow, and I don't want my laptop to have the only copy of the code. Is
it kosher to push my branch to the main git repos
I'd go with: fork the repository under your name, add it as a remote
and push it to that repository. Something like:
# fork the repos to something like:
github.com/MarkChuCarroll/incubator-aurora using github.com ui
git remote add markchucarroll
https://github.com/MarkChuCarroll/incubator-auro
Hey Mark
I think we talked about this right before we cut the initial rc0 and the
consensus was that any dev branches should be on your own fork to keep the
main git repo branches for release candidates and to help cut down on extra
commits@ noise from work in progress. have a good trip
-Jake
