Great, thanks!!
Regards,
prakhar
On Mon, Jun 9, 2014 at 2:56 PM, Vinod Kone wrote:
> As long as they are on different ports it should be fine. Use "--port" to
> specify the slave port. You should also give each slave its own work
> directory ("--work_dir") so that they don't trample on each ot
As long as they are on different ports it should be fine. Use "--port" to
specify the slave port. You should also give each slave its own work
directory ("--work_dir") so that they don't trample on each other.
On Mon, Jun 9, 2014 at 2:36 PM, Prakhar Panwaria <
prakhar.panwar...@gmail.com> wrote:
Hi Vinod,
Thanks for your reply. Yes, specifying the ip for the slave fixes that
error. And, the slave is also showing up in the Mesos GUI now.
Also, is there a way I could set up multiple slaves on a single machine for
a particular Mesos master. Looks like IP address is being used as an
identifi
Looks like "gethostbyname2" call is returning an error. I've seen this
before on my mac when i have vpn software running (or incorrectly stopped).
im surprised though that master on the same box is fine but only slave has
this issue? what happens if you specify --ip on the slave too?
On Mon, Jun
Hi all,
The vote for Mesos 0.19.0 (rc3) has passed with the following votes.
+1 (Binding)
--
Niklas Nielsen
Benjamin Hindman
Vinod Kone
+1 (Non-binding)
--
Tom Arnfeld
There were no 0 or -1 votes.
Please find the release at:
https://dist.
Thanks all who voted! Will be sending the release email out shortly.
On Mon, Jun 9, 2014 at 7:50 AM, Vinod Kone wrote:
> +1
>
> make check on 0SX 10.9
>
>
> On Sun, Jun 8, 2014 at 9:27 PM, Benjamin Hindman <
> benjamin.hind...@gmail.com
> > wrote:
>
> > +1, make check on OS X 10.7 with clang 3.
In addition to cpu and memory isolation, you will get process isolation.
With posix isolation, processes can "escape" from the slave (e.g. something
that double-forks and uses setsid).
On Mon, Jun 9, 2014 at 9:02 AM, Jie Yu wrote:
> Hi Dick,
>
>
>> what croup isolation provides over stock posix
Hi Vinod, Benjamin, and other mates,
I recently started playing around with Mesos. I think I installed it
successfully (make install went fine), but when I'm starting a Mesos slave
(and even during 'make check'), I'm facing the following warning and error:
>>>
*WARNING: Logging before InitGoogleL
Hi Dick,
> what croup isolation provides over stock posix / process isolation
Currently, mesos provides cpu and memory isolation through cgroups on Linux
boxes '--isolation=cgroups/cpu,cgroups/mem'
the configuration required to setup cgroups
If no other service on the host uses cgroup (no cg
+1
make check on 0SX 10.9
On Sun, Jun 8, 2014 at 9:27 PM, Benjamin Hindman wrote:
> +1, make check on OS X 10.7 with clang 3.3 (and it's also been running at
> Twitter, gcc 4.8).
>
>
> On Sat, Jun 7, 2014 at 10:58 AM, Tom Arnfeld wrote:
>
>> +1 from me. Tested on OSX Mavericks with gcc 4.8 an
So we're running with default isolation (posix)
and thinking about enabling cgroups (mesos 0.17.0
right now but the upgrade to 0.18.2 was seamless
in dev. so that'll probably happen too).
I just need to justify the effort and extra complexity,
so can someone explain briefly
* what croup isolation
11 matches
Mail list logo
