On 03/12/2015 02:00 PM, Tim St Clair wrote:
You may want to also view
- https://issues.apache.org/jira/browse/MESOS-1806
as folks have discussed straight up consul integration on that JIRA.
Any plans to resolve this JIRA for upcoming 0.22 release.
- Gurvinder
.
On Wed, Mar 11, 2015 at 2:08 AM, Gurvinder Singh
gurvinder.si...@uninett.no mailto:gurvinder.si...@uninett.no wrote:
On 03/10/2015 11:41 PM, Tim Chen wrote:
Hi all,
As Alex said you can run Mesos in CoreOS without Docker if you put in
the dependencies
On 03/10/2015 11:41 PM, Tim Chen wrote:
Hi all,
As Alex said you can run Mesos in CoreOS without Docker if you put in
the dependencies in.
Tim, is there any documentation of using Mesos outside container in
CoreOS available or binary available which we can wget in cloud-init
file to fulfill
,
MPark.
On 9 March 2015 at 17:52, Gurvinder Singh gurvinder.si...@uninett.no
mailto:gurvinder.si...@uninett.no wrote:
Hi,
I am wondering if anybody in the community has looked into or are
running mesos on top of coreos. I would be interested to hear out your
experiences
://www.sparrowmailapp.com/?sig
On Tuesday, March 10, 2015 at 11:08 AM, Gurvinder Singh wrote:
Hi Micheal,
Yes I tested the tutorial and it works fine for testing. Later on I used
fleet to run mesos workers on all coreos machines too. I was wondering
how the landscape is looking in the community
as
native CoreOS service to experiment with.
-- Anton Kirillov Sent with Sparrow
http://www.sparrowmailapp.com/?sig
On Tuesday, March 10, 2015 at 3:12 PM, Gurvinder Singh wrote:
Thanks Anton for sharing your experience. Response in line. On
03/10/2015 01:01 PM, Anton Kirillov wrote:
Hi
Hi,
I am wondering if anybody in the community has looked into or are
running mesos on top of coreos. I would be interested to hear out your
experiences around following areas
- Users management on coreos cluster and containers running with Mesos
- Are you using fleet to run mesos or run it as
This is the config we use for mesos logs
MESOSTIMESTAMP %{MONTHNUM}%{MONTHDAY} %{HOUR}:%{MINUTE}:%{SECOND}
MESOSLOG
%{DATA:loglevel}%{MESOSTIMESTAMP:timestamp}\s+%{POSINT:pid}\s+%{NOTSPACE:class}:
in logstash config
if [type] == mesos {
grok {
patterns_dir = [path to your patterns
:
On Fri, Jul 4, 2014 at 2:05 AM, Gurvinder Singh
gurvinder.si...@uninett.no mailto:gurvinder.si...@uninett.no
wrote:
ERROR storage.BlockManagerMasterActor: Got two different block
manager registrations on 201407031041-1227224054-5050-24004-0
Googling about it seems that mesos is starting slaves
tasks are dispatched is up to the individual framework.
Cheers,
Niklas
On 31 July 2014 07:28, Gurvinder Singh gurvinder.si...@uninett.no
mailto:gurvinder.si...@uninett.no wrote:
Hi,
I am wondering how mesos handle the task scheduling when the resource
are limited
Hi,
I am wondering how mesos handle the task scheduling when the resource
are limited and multiple users want to access them at the same time. Is
there any kind of fair scheduling as I see currently mainly FIFO. If
there is how can I specify that.
Thanks,
Gurvinder
We are getting this issue when we are running jobs with close to 1000
workers. Spark is from the github version and mesos is 0.19.0
ERROR storage.BlockManagerMasterActor: Got two different block manager
registrations on 201407031041-1227224054-5050-24004-0
Googling about it seems that mesos is
12 matches
Mail list logo
