Hi All,
I am trying to compile mesos on Centos7, but its failing. Please let me
know what is the reason.
Find the logs below.
Regards,
Pradeep
make[2]: ***
[slave/containerizer/mesos/provisioner/docker/libmesos_no_3rdparty_la-registry_puller.lo]
Error 1
make[2]: *** Waiting for unfinished jobs.
How do mesos masters and slaves react to zookeeper cluster changes? When the
masters and slaves start they are given a set of addresses to connect to
zookeeper. But over time, one of those zookeepers fails, and is replaced by a
new server at a new address. How should this be handled in the mesos
Could you show more details about error log? I could build current master
branch in CentOS 7.
On Mon, Nov 9, 2015 at 10:00 PM, Pradeep Kiruvale wrote:
> Hi All,
>
> I am trying to compile mesos on Centos7, but its failing. Please let me
> know what is the reason.
>
> Find the logs below.
>
> Reg
I just have only below logs.
libtool: compile: g++ -DPACKAGE_NAME=\"mesos\" -DPACKAGE_TARNAME=\"mesos\"
-DPACKAGE_VERSION=\"0.26.0\" "-DPACKAGE_STRING=\"mesos 0.26.0\""
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mesos\"
-DVERSION=\"0.26.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DH
There were some build errors due to some reverts in `registry_puller.cpp`.
Your error logs hints that it may be related to this. They should be fixed
now (with `cee4958`).
On Mon, Nov 9, 2015 at 3:23 PM, haosdent wrote:
> Could you show more details about error log? I could build current master
I had the same issue (broken build) on Ubuntu 14.04.. Commit “cee4958” helped.
Kind Regards,
Bartek Plotka
From: Jan Schlicht [mailto:j...@mesosphere.io]
Sent: Monday, November 9, 2015 3:27 PM
To: user@mesos.apache.org
Cc: dev
Subject: Re: Mesos .26 failing on centos7
There were some build erro
Hi all,
Jojy, That is correct, but more specifically a keepalive timer from slave to
master and slave to zookeeper. Can you send a link to the portion of the code
that builds the socket/connection? Is there any reason to not set the
SO_KEEPALIVE option in your opinion?
hasodent, I'm not look
Thanks it helped me.
Regards,
Pradeep
On 9 November 2015 at 15:37, Plotka, Bartlomiej wrote:
> I had the same issue (broken build) on Ubuntu 14.04.. Commit “cee4958”
> helped.
>
>
>
> *Kind Regards,*
>
> Bartek Plotka
>
>
>
> *From:* Jan Schlicht [mailto:j...@mesosphere.io]
> *Sent:* Monday, No
Good News, Netflix release a tools can do it:
https://github.com/Netflix/exhibitor/wiki/Rolling-Ensemble-Change
have a try it.
2015-11-09 22:01 GMT+08:00 Donald Laidlaw :
> How do mesos masters and slaves react to zookeeper cluster changes? When
> the masters and slaves start they are given a s
Hi All,
I am getting authentication issue on my mesos cluster
Please find the slave side and master side logs.
Regards,
Pradeep
*Slave logs *
W1110 01:54:18.641191 111550 slave.cpp:877] Authentication timed out
W1110 01:54:18.641309 111550 slave.cpp:841] Failed to authenticate with
master mas
My commits that caused the trouble are reverted now.
And also 0.26 will not be based on master, it typically are cherry picked
commits to specific tag.
Tim
> On Nov 9, 2015, at 6:37 AM, Plotka, Bartlomiej
> wrote:
>
> I had the same issue (broken build) on Ubuntu 14.04.. Commit “cee4958” hel
Yeah, I know about Exhibitor and how it handles zookeeper ensemble changes.
My question was about how to handle the Mesos servers.
What do you have to do with Mesos, when the zookeeper ensemble changes, to keep
the mesos servers happy and healthy?
Don Laidlaw
866 Cobequid Rd.
Lower Sackville,
Hi Jeremy
The “network” code is at "3rdparty/libprocess/include/process/network.hpp” ,
"3rdparty/libprocess/src/poll_socket.hpp/cpp”.
thanks
jojy
> On Nov 9, 2015, at 6:54 AM, Jeremy Olexa wrote:
>
> Hi all,
>
> Jojy, That is correct, but more specifically a keepalive timer from slave to
Alright, great, I'm making some progress,
I did a simple copy/paste modification and recompiled mesos. The keepalive
timer is set from slave to master so this is an improvement for me. I didn't
test the other direction yet -
https://gist.github.com/jolexa/ee9e152aa7045c558e02 - I'd like to fil
Hi Jeremy
Its great that you are making progress but I doubt if this is what you intend
to achieve since network failures are a valid state in distributed systems. If
you think there is a special case you are trying to solve, I suggest proposing
a design document for review.
For ZK client cod
The way I would do it in a production cluster would be *not* to use
directly IP addresses for the ZK ensemble, but instead rely on some form of
internal DNS and use internally-resolvable hostnames (eg, {zk1, zk2, ...}.
prod.example.com etc) and have the provisioning tooling (Chef, Puppet,
Ansible,
It would really help if you (Jeremy) explained the *actual* problem you are
facing. I'm *guessing* that it's a firewall timing out the sessions
because there isn't activity on them for whatever the timeout of the
firewall is? It seems likely to be unreasonably short, given that mesos
has constan
17 matches
Mail list logo
