Hi Pradeep,
Sorry I cannot get too much info from this log message, I see that you are
using balloon_framework, can you try mesos-execute?
Can you please add the option of GLOG_v=1 when start master and append the
whole log since the master start?
Thanks,
Guangya
On Wed, Oct 7, 2015 at 6:17 PM
Below are the logs from Master.
-Pradeep
1007 12:16:28.257853 8005 leveldb.cpp:343] Persisting action (20 bytes) to
leveldb took 119428ns
I1007 12:16:28.257884 8005 leveldb.cpp:401] Deleting ~2 keys from leveldb
took 18847ns
I1007 12:16:28.257891 8005 replica.cpp:679] Persisted action at 1440
Hi Pradeep,
Can you please append more log for your master node? Just want to see what
is wrong with your master, why the framework start to failover?
Thanks,
Guangya
On Wed, Oct 7, 2015 at 5:27 PM, Pradeep Kiruvale
wrote:
> Hi Guangya,
>
> I am running a frame work from some other physical n
Hi Guangya,
I am running a frame work from some other physical node, which is part of
the same network. Still I am getting below messages and the framework not
getting registered.
Any idea what is the reason?
I1007 11:24:58.781914 32392 master.cpp:4815] Framework failover timeout,
removing frame
Hi Guangya,
Thanks for the reply.
I also think the same. I found one of this old e-mail thread where in the
same thing was discussed.
He set up a client on a separate physical system, then it started working
fine.
I will also try and see.
Regards,
Pradeep
On 5 October 2015 at 13:51, Guangya
Hi Pradeep,
I think that the problem might be caused by that you are running the lxc
container on master node and not sure if there are any port conflict or
what else wrong.
For my case, I was running the client in a new node but not on master node,
perhaps you can have a try to put your client o
Hi Guangya,
Hmm!...That is strange in my case!
If I run from the mesos-execute on one of the slave/master node then the
tasks get their resources and they get scheduled well.
But if I start the mesos-execute on another node which is neither
slave/master then I have this issue.
I am using an lxc
Hi Pradeep,
>From your log, seems that the master process is exiting and this caused the
framework fail over to another mesos master. Can you please show more
detail for your issue reproduced steps?
I did some test by running mesos-execute on a client host which does not
have any mesos service an
Hi Guangya,
I am facing one more issue. If I try to schedule the tasks from some
external client system running the same cli mesos-execute.
The tasks are not getting launched. The tasks reach the Master and it just
drops the requests, below are the logs related to that
I1005 11:33:35.025594 21369
Hi Pradeep,
Glad it finally works! Not sure if you are using systemd.slice or not, are
you running to this issue: https://issues.apache.org/jira/browse/MESOS-1195
Hope Jie Yu can give you some help on this ;-)
Thanks,
Guangya
On Mon, Oct 5, 2015 at 5:25 PM, Pradeep Kiruvale
wrote:
> Hi Guang
Hi Guangya,
Thanks for sharing the information.
Now I could launch the tasks. The problem was with the permission. If I
start all the slaves and Master as root it works fine.
Else I have problem with launching the tasks.
But on one of the slave I could not launch the slave as root, I am facing
Hi Pradeep,
My steps was pretty simple just as
https://github.com/apache/mesos/blob/master/docs/getting-started.md#examples
On Master node: root@mesos1:~/src/mesos/m1/mesos/build# GLOG_v=1
./bin/mesos-master.sh --ip=192.168.0.107 --work_dir=/var/lib/mesos
On 3 Slave node: root@mesos007:~/src/mes
Hi Guangya,
Thanks for your reply.
I just want to know how did you launch the tasks.
1. What processes you have started on Master?
2. What are the processes you have started on Slaves?
I am missing something here, otherwise all my slave have enough memory and
cpus to launch the tasks I mentione
Hi Pradeep,
I did some test with your case and found that the task can run randomly on
the three slave hosts, every time may have different result. The logic is
here:
https://github.com/apache/mesos/blob/master/src/master/allocator/mesos/hierarchical.hpp#L1263-#L1266
The allocator will help random
Yes there should be configuration options for this in mesos configuration -
see documentation. I am leaving now so i wont be able to respond till Sunday
2015-10-03 11:18 GMT+02:00 Pradeep Kiruvale :
> I have different login names for different system. I have a client system,
> from where I launch
I have different login names for different system. I have a client system,
from where I launch the tasks. But these tasks are not getting any
resources. So, they are not getting scheduled.
I mean to say my cluster arrangement is 1 client, 1 Master, 3 slaves. All
are different physical systems.
Is
mesos framework receive offers and based on those offers it decides where
to run tasks.
mesos-execute is little framework that executes your task (hackbench) - see
here https://github.com/apache/mesos/blob/master/src/cli/execute.cpp
https://github.com/apache/mesos/blob/master/src/cli/execute.cpp
Hi Ondrej,
Thanks for your reply
I did solve that issue, yes you are right there was an issue with slave IP
address setting.
Now I am facing issue with the scheduling the tasks. When I try to schedule
a task using
/src/mesos-execute --master=192.168.0.102:5050 --name="cluster-test"
--command="/
Hi Pradeep,
the problem is with IP your slave advertise - mesos by default resolves
your hostname - there are several solutions (let say your node ip is
192.168.56.128)
1) export LIBPROCESS_IP=192.168.56.128
2) set mesos options - ip, hostname
one way to do this is to create files
echo "192.
Hi Guangya,
Thanks for reply. I found one interesting log message.
7410 master.cpp:5977] Removed slave
6a11063e-b8ff-43bd-86cf-e6eef0de06fd-S52 (192.168.0.178): a new slave
registered at the same address
Mostly because of this issue, the systems/slave nodes are getting
registered and de-registe
Hi Pradeep,
Please check some of my questions in line.
Thanks,
Guangya
On Fri, Oct 2, 2015 at 12:55 AM, Pradeep Kiruvale wrote:
> Hi All,
>
> I am new to Mesos. I have set up a Mesos cluster with 1 Master and 3
> Slaves.
>
> One slave runs on the Master Node itself and Other slaves run on dif
Hi All,
I am new to Mesos. I have set up a Mesos cluster with 1 Master and 3 Slaves.
One slave runs on the Master Node itself and Other slaves run on different
nodes. Here node means the physical boxes.
I tried running the tasks by configuring one Node cluster. Tested the task
scheduling using m
22 matches
Mail list logo
