You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by F21 <f2...@gmail.com> on 2015/09/25 14:02:23 UTC
Web ui offers tab blank
I am running mesos 0.24 on CoreOS. I also have Marathon 0.10.1 running.
I am trying to run the HDFS framework and notice that it's complaining
that there isn't enough resources when trying to launch an executor.
I wanted to see what offers are being made, but when I click the
"offers" tab in the web ui, I see no offers.
Is this a bug? Or have I neglected a configuration option?
Re: Web ui offers tab blank
Posted by F21 <f2...@gmail.com>.
These are the logs from the hdfs scheduler:
04:41:23.299 [Thread-297] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:23.300 [Thread-297] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:23.312 [Thread-297] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.12
04:41:23.312 [Thread-297] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1814"
04:41:27.300 [Thread-298] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 2 offers
04:41:27.300 [Thread-298] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1819"
04:41:27.300 [Thread-298] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1820"
04:41:27.300 [Thread-298] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1819"
04:41:27.300 [Thread-298] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:27.300 [Thread-298] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:27.325 [Thread-298] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.13
04:41:27.325 [Thread-298] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1819"
04:41:27.325 [Thread-298] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1820"
04:41:27.325 [Thread-298] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:27.325 [Thread-298] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:27.325 [Thread-298] INFO o.a.mesos.hdfs.scheduler.NameNode -
Offer does not have enough resources
04:41:27.326 [Thread-298] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1820"
04:41:29.503 [Thread-299] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 2 offers
04:41:29.503 [Thread-299] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1822"
04:41:29.503 [Thread-299] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1823"
04:41:29.503 [Thread-299] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1822"
04:41:29.503 [Thread-299] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:29.503 [Thread-299] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:29.521 [Thread-299] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.12
04:41:29.521 [Thread-299] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1822"
04:41:29.521 [Thread-299] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1823"
04:41:29.521 [Thread-299] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:29.521 [Thread-299] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:29.539 [Thread-299] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.11
04:41:29.539 [Thread-299] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1823"
04:41:32.525 [Thread-300] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 2 offers
04:41:32.525 [Thread-300] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1827"
04:41:32.525 [Thread-300] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1828"
04:41:32.526 [Thread-300] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1827"
04:41:32.526 [Thread-300] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:32.526 [Thread-300] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:32.548 [Thread-300] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.13
04:41:32.548 [Thread-300] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1827"
04:41:32.548 [Thread-300] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1828"
04:41:32.548 [Thread-300] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:32.548 [Thread-300] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:32.548 [Thread-300] INFO o.a.mesos.hdfs.scheduler.NameNode -
Offer does not have enough resources
04:41:32.548 [Thread-300] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1828"
04:41:35.546 [Thread-301] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 1 offers
04:41:35.546 [Thread-301] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1830"
04:41:35.546 [Thread-301] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1830"
04:41:35.546 [Thread-301] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:35.546 [Thread-301] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:35.576 [Thread-301] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.12
04:41:35.576 [Thread-301] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1830"
04:41:36.548 [Thread-302] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 1 offers
04:41:36.548 [Thread-302] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1833"
04:41:36.548 [Thread-302] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1833"
04:41:36.548 [Thread-302] INFO o.apache.mesos.hdfs.util.DnsResolver -
Resolving DNS for journalnode1.hdfs.mesos
04:41:36.548 [Thread-302] INFO o.apache.mesos.hdfs.util.DnsResolver -
Successfully found journalnode1.hdfs.mesos
04:41:36.569 [Thread-302] INFO o.a.mesos.hdfs.scheduler.NameNode - We
need to coloate the namenode with a journalnode and there isno
journalnode running on this host. 192.168.33.11
04:41:36.570 [Thread-302] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, declining offer: value:
"20150926-040939-169978048-5050-594-O1833"
04:41:37.565 [Thread-303] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
Received 2 offers
04:41:37.566 [Thread-303] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1835"
04:41:37.566 [Thread-303] INFO o.a.m.hdfs.scheduler.HdfsScheduler -
value: "20150926-040939-169978048-5050-594-O1836"
04:41:37.567 [Thread-303] INFO o.a.mesos.hdfs.scheduler.HdfsNode -
Node: namenode, evaluating offer: value:
"20150926-040939-169978048-5050-594-O1835"
In the master, I see the following:
I0926 04:41:13.067692 794 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1799 ] on slave
20150926-040939-169978048-5050-594-S0 at slave(1)@192.168.33.10:5051
(192.168.33.10) for framework 20150925-063839-169978048-5050-1342-0000
(marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:13.069633 794 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-9999, 10001-52000]; cpus(*):2.5;
mem(*):205; disk(*):10723 (total: ports(*):[1-3999, 4050-4999,
5055-52000]; cpus(*):4; mem(*):1485; disk(*):10823, allocated:
ports(*):[10000-10000]; cpus(*):1.5; mem(*):1280; disk(*):100) on slave
20150926-040939-169978048-5050-594-S0 from framework
20150925-063839-169978048-5050-1342-0000
I0926 04:41:13.074669 801 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1798 ] on slave
20150926-040939-169978048-5050-594-S1 at slave(1)@192.168.33.11:5051
(192.168.33.11) for framework 20150925-094948-169978048-5050-575-0000
(hdfs) at scheduler-cdb5b3e3-ad70-41e8-be1f-202039631ee3@192.168.33.10:34037
I0926 04:41:13.075084 801 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-52000]; cpus(*):4; mem(*):1485;
disk(*):10823 (total: ports(*):[1-3999, 4050-4999, 5055-52000];
cpus(*):4; mem(*):1485; disk(*):10823, allocated: ) on slave
20150926-040939-169978048-5050-594-S1 from framework
20150925-094948-169978048-5050-575-0000
I0926 04:41:14.064031 798 master.cpp:4613] Sending 1 offers to
framework 20150925-063839-169978048-5050-1342-0000 (marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:14.077571 801 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1800 ] on slave
20150926-040939-169978048-5050-594-S1 at slave(1)@192.168.33.11:5051
(192.168.33.11) for framework 20150925-063839-169978048-5050-1342-0000
(marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:14.079902 801 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-52000]; cpus(*):4; mem(*):1485;
disk(*):10823 (total: ports(*):[1-3999, 4050-4999, 5055-52000];
cpus(*):4; mem(*):1485; disk(*):10823, allocated: ) on slave
20150926-040939-169978048-5050-594-S1 from framework
20150925-063839-169978048-5050-1342-0000
I0926 04:41:15.077798 797 master.cpp:4613] Sending 1 offers to
framework 20150925-063839-169978048-5050-1342-0000 (marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:15.090351 799 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1801 ] on slave
20150926-040939-169978048-5050-594-S3 at slave(1)@192.168.33.13:5051
(192.168.33.13) for framework 20150925-063839-169978048-5050-1342-0000
(marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:15.091563 799 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-52000]; cpus(*):4; mem(*):1485;
disk(*):10823 (total: ports(*):[1-3999, 4050-4999, 5055-52000];
cpus(*):4; mem(*):1485; disk(*):10823, allocated: ) on slave
20150926-040939-169978048-5050-594-S3 from framework
20150925-063839-169978048-5050-1342-0000
I0926 04:41:15.504425 795 http.cpp:321] HTTP GET for
/master/state.json from 192.168.33.1:53196 with User-Agent='Mozilla/5.0
(Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/45.0.2454.101 Safari/537.36'
I0926 04:41:17.110131 799 master.cpp:4613] Sending 1 offers to
framework 20150925-063839-169978048-5050-1342-0000 (marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:17.112371 799 master.cpp:4613] Sending 2 offers to
framework 20150925-094948-169978048-5050-575-0000 (hdfs) at
scheduler-cdb5b3e3-ad70-41e8-be1f-202039631ee3@192.168.33.10:34037
I0926 04:41:17.127305 796 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1802 ] on slave
20150926-040939-169978048-5050-594-S2 at slave(1)@192.168.33.12:5051
(192.168.33.12) for framework 20150925-063839-169978048-5050-1342-0000
(marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:17.129078 796 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-52000]; cpus(*):4; mem(*):1485;
disk(*):10823 (total: ports(*):[1-3999, 4050-4999, 5055-52000];
cpus(*):4; mem(*):1485; disk(*):10823, allocated: ) on slave
20150926-040939-169978048-5050-594-S2 from framework
20150925-063839-169978048-5050-1342-0000
I0926 04:41:17.148516 799 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1803 ] on slave
20150926-040939-169978048-5050-594-S0 at slave(1)@192.168.33.10:5051
(192.168.33.10) for framework 20150925-094948-169978048-5050-575-0000
(hdfs) at scheduler-cdb5b3e3-ad70-41e8-be1f-202039631ee3@192.168.33.10:34037
I0926 04:41:17.151549 799 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1804 ] on slave
20150926-040939-169978048-5050-594-S3 at slave(1)@192.168.33.13:5051
(192.168.33.13) for framework 20150925-094948-169978048-5050-575-0000
(hdfs) at scheduler-cdb5b3e3-ad70-41e8-be1f-202039631ee3@192.168.33.10:34037
I0926 04:41:17.153192 794 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-9999, 10001-52000]; cpus(*):2.5;
mem(*):205; disk(*):10723 (total: ports(*):[1-3999, 4050-4999,
5055-52000]; cpus(*):4; mem(*):1485; disk(*):10823, allocated:
ports(*):[10000-10000]; cpus(*):1.5; mem(*):1280; disk(*):100) on slave
20150926-040939-169978048-5050-594-S0 from framework
20150925-094948-169978048-5050-575-0000
I0926 04:41:17.153986 794 hierarchical.hpp:814] Recovered
ports(*):[1-3999, 4050-4999, 5055-52000]; cpus(*):4; mem(*):1485;
disk(*):10823 (total: ports(*):[1-3999, 4050-4999, 5055-52000];
cpus(*):4; mem(*):1485; disk(*):10823, allocated: ) on slave
20150926-040939-169978048-5050-594-S3 from framework
20150925-094948-169978048-5050-575-0000
I0926 04:41:18.120578 799 master.cpp:4613] Sending 2 offers to
framework 20150925-094948-169978048-5050-575-0000 (hdfs) at
scheduler-cdb5b3e3-ad70-41e8-be1f-202039631ee3@192.168.33.10:34037
I0926 04:41:18.122284 799 master.cpp:4613] Sending 1 offers to
framework 20150925-063839-169978048-5050-1342-0000 (marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
I0926 04:41:18.140413 794 master.cpp:2739] Processing ACCEPT call for
offers: [ 20150926-040939-169978048-5050-594-O1807 ] on slave
20150926-040939-169978048-5050-594-S0 at slave(1)@192.168.33.10:5051
(192.168.33.10) for framework 20150925-063839-169978048-5050-1342-0000
(marathon) at
scheduler-4f7b57a5-cded-4e8f-90d7-7ad160488544@192.168.33.10:34340
Even though it's evident there are offers, I still don't see anything in
the offers tab of the web ui.
On 26/09/2015 4:17 AM, Vinod Kone wrote:
> What do the master and scheduler logs say?
>
> On Fri, Sep 25, 2015 at 5:02 AM, F21 <f21.groups@gmail.com
> <ma...@gmail.com>> wrote:
>
> I am running mesos 0.24 on CoreOS. I also have Marathon 0.10.1
> running.
>
> I am trying to run the HDFS framework and notice that it's
> complaining that there isn't enough resources when trying to
> launch an executor.
>
> I wanted to see what offers are being made, but when I click the
> "offers" tab in the web ui, I see no offers.
>
> Is this a bug? Or have I neglected a configuration option?
>
>
Re: Web ui offers tab blank
Posted by Vinod Kone <vi...@gmail.com>.
What do the master and scheduler logs say?
On Fri, Sep 25, 2015 at 5:02 AM, F21 <f2...@gmail.com> wrote:
> I am running mesos 0.24 on CoreOS. I also have Marathon 0.10.1 running.
>
> I am trying to run the HDFS framework and notice that it's complaining
> that there isn't enough resources when trying to launch an executor.
>
> I wanted to see what offers are being made, but when I click the "offers"
> tab in the web ui, I see no offers.
>
> Is this a bug? Or have I neglected a configuration option?
>