You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Tomek Janiszewski <ja...@gmail.com> on 2016/01/13 10:59:35 UTC
Re: mesos 0.24.1 and 0.25.0 offers web ui not appearing to work
Hi
I've got problem with web UI after upgrading from 0.22.1 to 0.23.1 (checked
on VM with 0.25 and problem still exists). Task table is not populated with
data. I try to find an issue for this but I only found this email where I
see same problem on Abdul's screens (I attached one to show my problem).
I've checked difference between /master/state.json from version 0.22.1 and
0.23.1 and it looks like failed/killed/lost/stage/started_tasks entries are
missing? Am I right? Where I can find them now?
Thanks
Tomek
śr., 4.11.2015 o 21:09 użytkownik Abdul Jabbar Azam <aj...@gmail.com>
napisał:
> Hello,
> Thanks for that. That means that the offers that arent appearing are being
> used or being held by something. I'll look in the logs to see if that's the
> case.
>
> On Wed, 4 Nov 2015, 17:31 haosdent <ha...@gmail.com> wrote:
>
>> Oh, yes. But so far the offer should in webui is outstanding offers which
>> not yet be accepted. I create the rename ticket here
>> https://issues.apache.org/jira/browse/MESOS-3817
>>
>> On Tue, Nov 3, 2015 at 5:56 AM, Abdul Jabbar Azam <aj...@gmail.com>
>> wrote:
>>
>>>
>>> I found out about the metrics snapshot screen(
>>> http://172.16.2.60:5050/metrics/snapshot) and got the result at the
>>> bottom of the email
>>>
>>> I can see that the offers stuff is working, even though it must have
>>> worked before, because I was running multiple instances of a test bash
>>> script.
>>>
>>> As a beginner I do find the offers screen a bit confusing though. I
>>> would prefer to see offers and state changes over time.
>>>
>>> {
>>>
>>> - allocator/event_queue_dispatches: 0,
>>> - master/cpus_percent: 0,
>>> - master/cpus_revocable_percent: 0,
>>> - master/cpus_revocable_total: 0,
>>> - master/cpus_revocable_used: 0,
>>> - master/cpus_total: 12,
>>> - master/cpus_used: 0,
>>> - master/disk_percent: 0,
>>> - master/disk_revocable_percent: 0,
>>> - master/disk_revocable_total: 0,
>>> - master/disk_revocable_used: 0,
>>> - master/disk_total: 2084062,
>>> - master/disk_used: 0,
>>> - master/dropped_messages: 4,
>>> - master/elected: 1,
>>> - master/event_queue_dispatches: 21,
>>> - master/event_queue_http_requests: 0,
>>> - master/event_queue_messages: 0,
>>> - master/frameworks_active: 1,
>>> - master/frameworks_connected: 1,
>>> - master/frameworks_disconnected: 0,
>>> - master/frameworks_inactive: 0,
>>> - master/invalid_framework_to_executor_messages: 0,
>>> - master/invalid_status_update_acknowledgements: 0,
>>> - master/invalid_status_updates: 0,
>>> - master/mem_percent: 0,
>>> - master/mem_revocable_percent: 0,
>>> - master/mem_revocable_total: 0,
>>> - master/mem_revocable_used: 0,
>>> - master/mem_total: 12632,
>>> - master/mem_used: 0,
>>> - master/messages_authenticate: 0,
>>> - master/messages_deactivate_framework: 0,
>>> - master/messages_decline_offers: 4,
>>> - master/messages_exited_executor: 0,
>>> - master/messages_framework_to_executor: 0,
>>> - master/messages_kill_task: 0,
>>> - master/messages_launch_tasks: 0,
>>> - master/messages_reconcile_tasks: 0,
>>> - master/messages_register_framework: 0,
>>> - master/messages_register_slave: 0,
>>> - master/messages_reregister_framework: 1,
>>> - master/messages_reregister_slave: 3,
>>> - master/messages_resource_request: 0,
>>> - master/messages_revive_offers: 1,
>>> - master/messages_status_update: 0,
>>> - master/messages_status_update_acknowledgement: 0,
>>> - master/messages_unregister_framework: 0,
>>> - master/messages_unregister_slave: 0,
>>> - master/messages_update_slave: 3,
>>> - master/outstanding_offers: 0,
>>> - master/recovery_slave_removals: 0,
>>> - master/slave_registrations: 0,
>>> - master/slave_removals: 0,
>>> - master/slave_removals/reason_registered: 0,
>>> - master/slave_removals/reason_unhealthy: 0,
>>> - master/slave_removals/reason_unregistered: 0,
>>> - master/slave_reregistrations: 3,
>>> - master/slave_shutdowns_canceled: 0,
>>> - master/slave_shutdowns_completed: 0,
>>> - master/slave_shutdowns_scheduled: 0,
>>> - master/slaves_active: 3,
>>> - master/slaves_connected: 3,
>>> - master/slaves_disconnected: 0,
>>> - master/slaves_inactive: 0,
>>> - master/tasks_error: 0,
>>> - master/tasks_failed: 0,
>>> - master/tasks_finished: 0,
>>> - master/tasks_killed: 0,
>>> - master/tasks_lost: 0,
>>> - master/tasks_running: 0,
>>> - master/tasks_staging: 0,
>>> - master/tasks_starting: 0,
>>> - master/uptime_secs: 21.317382912,
>>> - master/valid_framework_to_executor_messages: 0,
>>> - master/valid_status_update_acknowledgements: 0,
>>> - master/valid_status_updates: 0,
>>> - registrar/queued_operations: 0,
>>> - registrar/registry_size_bytes: 746,
>>> - registrar/state_fetch_ms: 22.148096,
>>> - registrar/state_store_ms: 10.608128,
>>> - registrar/state_store_ms/count: 4,
>>> - registrar/state_store_ms/max: 16.499968,
>>> - registrar/state_store_ms/min: 10.608128,
>>> - registrar/state_store_ms/p50: 15.01504,
>>> - registrar/state_store_ms/p90: 16.4582656,
>>> - registrar/state_store_ms/p95: 16.4791168,
>>> - registrar/state_store_ms/p99: 16.49579776,
>>> - registrar/state_store_ms/p999: 16.499550976,
>>> - registrar/state_store_ms/p9999: 16.4999262976,
>>> - system/cpus_total: 2,
>>> - system/load_15min: 0.07,
>>> - system/load_1min: 0.77,
>>> - system/load_5min: 0.22,
>>> - system/mem_free_bytes: 7682621440,
>>> - system/mem_total_bytes: 8372236288
>>>
>>> }
>>>
>>> On Mon, 2 Nov 2015 at 12:39 Guangya Liu <gy...@gmail.com> wrote:
>>>
>>>> Just echo Alex, yes, once the outstanding offer is accepted by
>>>> framework, the master will remove the offer. Thanks!
>>>>
>>>> On Mon, Nov 2, 2015 at 8:13 PM, Alex Rukletsov <al...@mesosphere.com>
>>>> wrote:
>>>>
>>>>> Hi Haosdent,
>>>>>
>>>>> I don't remember exactly (and I'm from my phone now), but I think
>>>>> offers mean outstanding offers. Which means once it's accepted, it's no
>>>>> longer an offer. Could you please verify that and file a rename ticket?
>>>>>
>>>>> Thanks,
>>>>> Alex
>>>>> On 2 Nov 2015 6:24 am, "haosdent" <ha...@gmail.com> wrote:
>>>>>
>>>>>> Hmm, after check current code. Mesos would removeOffer after the
>>>>>> framework accept offer.
>>>>>>
>>>>>> On Mon, Nov 2, 2015 at 11:08 AM, haosdent <ha...@gmail.com> wrote:
>>>>>>
>>>>>>> Could you create a ticket in
>>>>>>> https://issues.apache.org/jira/browse/MESOS ? I think Mesos have
>>>>>>> some problems in state.json endpoint. I am digging into this.
>>>>>>>
>>>>>>> On Mon, Nov 2, 2015 at 6:01 AM, Abdul Jabbar Azam <aj...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I'm new to mesos. Over the past few days I setup a mesos cluster. I
>>>>>>>> can send it a test job and can see that it is working by looking at master
>>>>>>>> web ui[image: Screen Shot 2015-11-01 at 21.44.16.png]
>>>>>>>> Ignore the LOST and FAILED states. They were tasks that were
>>>>>>>> running when I was using mesos 0.25.0. I didn't clear zookeeper before
>>>>>>>> running mesos 0.24.1 on the same cluster.
>>>>>>>>
>>>>>>>> My problem is that the Offers screen isn't showing anything. I
>>>>>>>> don't know whether there is something wrong. Has anybody experienced this
>>>>>>>> before?
>>>>>>>>
>>>>>>>> I've attached the other screens as well.
>>>>>>>>
>>>>>>>> I'm using Ubuntu Server 14.04.3 LTS,mesos-0.24.1, zookeeper 3.4.6,
>>>>>>>> marathon-0.11.1, JDK 8u66
>>>>>>>>
>>>>>>>> Total nodes is 5 where 4 are agents/slaves and 1 is the mesos
>>>>>>>> master, zookeeper and marathon node. I'm not allowed to have any more
>>>>>>>> servers at home ;)
>>>>>>>>
>>>>>>>> I created an ansible script so reinstalling with different version
>>>>>>>> number combinations is not a problem.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> Abdul Jabbar Azam
>>>>>>>> twitter: @ajazam
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Haosdent Huang
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Haosdent Huang
>>>>>>
>>>>> --
>>> Regards
>>>
>>> Abdul Jabbar Azam
>>> twitter: @ajazam
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
> --
> Regards
>
> Abdul Jabbar Azam
> twitter: @ajazam
>
Re: mesos 0.24.1 and 0.25.0 offers web ui not appearing to work
Posted by X Brick <ng...@gmail.com>.
The same problem +1, Our Mesos cluster(0.25) still have this issue when the
leader has been crushed and another one elected the leader. New leader did
not show any task statistics. If I want to get these statistics back, I had
to let the old one take leader back.
2016-01-13 18:17 GMT+08:00 Tomek Janiszewski <ja...@gmail.com>:
> Thanks, I'll upgrade ASAP.
>
> śr., 13.01.2016 o 11:04 użytkownik haosdent <ha...@gmail.com> napisał:
>
>> This one should be fixed since 0.25
>> https://issues.apache.org/jira/browse/MESOS-3282
>>
>> On Wed, Jan 13, 2016 at 5:59 PM, Tomek Janiszewski <ja...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> I've got problem with web UI after upgrading from 0.22.1 to 0.23.1
>>> (checked on VM with 0.25 and problem still exists). Task table is not
>>> populated with data. I try to find an issue for this but I only found this
>>> email where I see same problem on Abdul's screens (I attached one to show
>>> my problem).
>>> I've checked difference between /master/state.json from version 0.22.1
>>> and 0.23.1 and it looks like failed/killed/lost/stage/started_tasks entries
>>> are missing? Am I right? Where I can find them now?
>>>
>>> Thanks
>>> Tomek
>>>
>>> śr., 4.11.2015 o 21:09 użytkownik Abdul Jabbar Azam <aj...@gmail.com>
>>> napisał:
>>>
>>>> Hello,
>>>> Thanks for that. That means that the offers that arent appearing are
>>>> being used or being held by something. I'll look in the logs to see if
>>>> that's the case.
>>>>
>>>> On Wed, 4 Nov 2015, 17:31 haosdent <ha...@gmail.com> wrote:
>>>>
>>>>> Oh, yes. But so far the offer should in webui is outstanding offers
>>>>> which not yet be accepted. I create the rename ticket here
>>>>> https://issues.apache.org/jira/browse/MESOS-3817
>>>>>
>>>>> On Tue, Nov 3, 2015 at 5:56 AM, Abdul Jabbar Azam <aj...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> I found out about the metrics snapshot screen(
>>>>>> http://172.16.2.60:5050/metrics/snapshot) and got the result at the
>>>>>> bottom of the email
>>>>>>
>>>>>> I can see that the offers stuff is working, even though it must have
>>>>>> worked before, because I was running multiple instances of a test bash
>>>>>> script.
>>>>>>
>>>>>> As a beginner I do find the offers screen a bit confusing though. I
>>>>>> would prefer to see offers and state changes over time.
>>>>>>
>>>>>> {
>>>>>>
>>>>>> - allocator/event_queue_dispatches: 0,
>>>>>> - master/cpus_percent: 0,
>>>>>> - master/cpus_revocable_percent: 0,
>>>>>> - master/cpus_revocable_total: 0,
>>>>>> - master/cpus_revocable_used: 0,
>>>>>> - master/cpus_total: 12,
>>>>>> - master/cpus_used: 0,
>>>>>> - master/disk_percent: 0,
>>>>>> - master/disk_revocable_percent: 0,
>>>>>> - master/disk_revocable_total: 0,
>>>>>> - master/disk_revocable_used: 0,
>>>>>> - master/disk_total: 2084062,
>>>>>> - master/disk_used: 0,
>>>>>> - master/dropped_messages: 4,
>>>>>> - master/elected: 1,
>>>>>> - master/event_queue_dispatches: 21,
>>>>>> - master/event_queue_http_requests: 0,
>>>>>> - master/event_queue_messages: 0,
>>>>>> - master/frameworks_active: 1,
>>>>>> - master/frameworks_connected: 1,
>>>>>> - master/frameworks_disconnected: 0,
>>>>>> - master/frameworks_inactive: 0,
>>>>>> - master/invalid_framework_to_executor_messages: 0,
>>>>>> - master/invalid_status_update_acknowledgements: 0,
>>>>>> - master/invalid_status_updates: 0,
>>>>>> - master/mem_percent: 0,
>>>>>> - master/mem_revocable_percent: 0,
>>>>>> - master/mem_revocable_total: 0,
>>>>>> - master/mem_revocable_used: 0,
>>>>>> - master/mem_total: 12632,
>>>>>> - master/mem_used: 0,
>>>>>> - master/messages_authenticate: 0,
>>>>>> - master/messages_deactivate_framework: 0,
>>>>>> - master/messages_decline_offers: 4,
>>>>>> - master/messages_exited_executor: 0,
>>>>>> - master/messages_framework_to_executor: 0,
>>>>>> - master/messages_kill_task: 0,
>>>>>> - master/messages_launch_tasks: 0,
>>>>>> - master/messages_reconcile_tasks: 0,
>>>>>> - master/messages_register_framework: 0,
>>>>>> - master/messages_register_slave: 0,
>>>>>> - master/messages_reregister_framework: 1,
>>>>>> - master/messages_reregister_slave: 3,
>>>>>> - master/messages_resource_request: 0,
>>>>>> - master/messages_revive_offers: 1,
>>>>>> - master/messages_status_update: 0,
>>>>>> - master/messages_status_update_acknowledgement: 0,
>>>>>> - master/messages_unregister_framework: 0,
>>>>>> - master/messages_unregister_slave: 0,
>>>>>> - master/messages_update_slave: 3,
>>>>>> - master/outstanding_offers: 0,
>>>>>> - master/recovery_slave_removals: 0,
>>>>>> - master/slave_registrations: 0,
>>>>>> - master/slave_removals: 0,
>>>>>> - master/slave_removals/reason_registered: 0,
>>>>>> - master/slave_removals/reason_unhealthy: 0,
>>>>>> - master/slave_removals/reason_unregistered: 0,
>>>>>> - master/slave_reregistrations: 3,
>>>>>> - master/slave_shutdowns_canceled: 0,
>>>>>> - master/slave_shutdowns_completed: 0,
>>>>>> - master/slave_shutdowns_scheduled: 0,
>>>>>> - master/slaves_active: 3,
>>>>>> - master/slaves_connected: 3,
>>>>>> - master/slaves_disconnected: 0,
>>>>>> - master/slaves_inactive: 0,
>>>>>> - master/tasks_error: 0,
>>>>>> - master/tasks_failed: 0,
>>>>>> - master/tasks_finished: 0,
>>>>>> - master/tasks_killed: 0,
>>>>>> - master/tasks_lost: 0,
>>>>>> - master/tasks_running: 0,
>>>>>> - master/tasks_staging: 0,
>>>>>> - master/tasks_starting: 0,
>>>>>> - master/uptime_secs: 21.317382912,
>>>>>> - master/valid_framework_to_executor_messages: 0,
>>>>>> - master/valid_status_update_acknowledgements: 0,
>>>>>> - master/valid_status_updates: 0,
>>>>>> - registrar/queued_operations: 0,
>>>>>> - registrar/registry_size_bytes: 746,
>>>>>> - registrar/state_fetch_ms: 22.148096,
>>>>>> - registrar/state_store_ms: 10.608128,
>>>>>> - registrar/state_store_ms/count: 4,
>>>>>> - registrar/state_store_ms/max: 16.499968,
>>>>>> - registrar/state_store_ms/min: 10.608128,
>>>>>> - registrar/state_store_ms/p50: 15.01504,
>>>>>> - registrar/state_store_ms/p90: 16.4582656,
>>>>>> - registrar/state_store_ms/p95: 16.4791168,
>>>>>> - registrar/state_store_ms/p99: 16.49579776,
>>>>>> - registrar/state_store_ms/p999: 16.499550976,
>>>>>> - registrar/state_store_ms/p9999: 16.4999262976,
>>>>>> - system/cpus_total: 2,
>>>>>> - system/load_15min: 0.07,
>>>>>> - system/load_1min: 0.77,
>>>>>> - system/load_5min: 0.22,
>>>>>> - system/mem_free_bytes: 7682621440,
>>>>>> - system/mem_total_bytes: 8372236288
>>>>>>
>>>>>> }
>>>>>>
>>>>>> On Mon, 2 Nov 2015 at 12:39 Guangya Liu <gy...@gmail.com> wrote:
>>>>>>
>>>>>>> Just echo Alex, yes, once the outstanding offer is accepted by
>>>>>>> framework, the master will remove the offer. Thanks!
>>>>>>>
>>>>>>> On Mon, Nov 2, 2015 at 8:13 PM, Alex Rukletsov <al...@mesosphere.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Haosdent,
>>>>>>>>
>>>>>>>> I don't remember exactly (and I'm from my phone now), but I think
>>>>>>>> offers mean outstanding offers. Which means once it's accepted, it's no
>>>>>>>> longer an offer. Could you please verify that and file a rename ticket?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Alex
>>>>>>>> On 2 Nov 2015 6:24 am, "haosdent" <ha...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hmm, after check current code. Mesos would removeOffer after the
>>>>>>>>> framework accept offer.
>>>>>>>>>
>>>>>>>>> On Mon, Nov 2, 2015 at 11:08 AM, haosdent <ha...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Could you create a ticket in
>>>>>>>>>> https://issues.apache.org/jira/browse/MESOS ? I think Mesos have
>>>>>>>>>> some problems in state.json endpoint. I am digging into this.
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 2, 2015 at 6:01 AM, Abdul Jabbar Azam <
>>>>>>>>>> ajazam@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I'm new to mesos. Over the past few days I setup a mesos
>>>>>>>>>>> cluster. I can send it a test job and can see that it is working by looking
>>>>>>>>>>> at master web ui[image: Screen Shot 2015-11-01 at 21.44.16.png]
>>>>>>>>>>> Ignore the LOST and FAILED states. They were tasks that were
>>>>>>>>>>> running when I was using mesos 0.25.0. I didn't clear zookeeper before
>>>>>>>>>>> running mesos 0.24.1 on the same cluster.
>>>>>>>>>>>
>>>>>>>>>>> My problem is that the Offers screen isn't showing anything. I
>>>>>>>>>>> don't know whether there is something wrong. Has anybody experienced this
>>>>>>>>>>> before?
>>>>>>>>>>>
>>>>>>>>>>> I've attached the other screens as well.
>>>>>>>>>>>
>>>>>>>>>>> I'm using Ubuntu Server 14.04.3 LTS,mesos-0.24.1, zookeeper
>>>>>>>>>>> 3.4.6, marathon-0.11.1, JDK 8u66
>>>>>>>>>>>
>>>>>>>>>>> Total nodes is 5 where 4 are agents/slaves and 1 is the mesos
>>>>>>>>>>> master, zookeeper and marathon node. I'm not allowed to have any more
>>>>>>>>>>> servers at home ;)
>>>>>>>>>>>
>>>>>>>>>>> I created an ansible script so reinstalling with different
>>>>>>>>>>> version number combinations is not a problem.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> Abdul Jabbar Azam
>>>>>>>>>>> twitter: @ajazam
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Best Regards,
>>>>>>>>>> Haosdent Huang
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Haosdent Huang
>>>>>>>>>
>>>>>>>> --
>>>>>> Regards
>>>>>>
>>>>>> Abdul Jabbar Azam
>>>>>> twitter: @ajazam
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Haosdent Huang
>>>>>
>>>> --
>>>> Regards
>>>>
>>>> Abdul Jabbar Azam
>>>> twitter: @ajazam
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
Re: mesos 0.24.1 and 0.25.0 offers web ui not appearing to work
Posted by Tomek Janiszewski <ja...@gmail.com>.
Thanks, I'll upgrade ASAP.
śr., 13.01.2016 o 11:04 użytkownik haosdent <ha...@gmail.com> napisał:
> This one should be fixed since 0.25
> https://issues.apache.org/jira/browse/MESOS-3282
>
> On Wed, Jan 13, 2016 at 5:59 PM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
>> Hi
>>
>> I've got problem with web UI after upgrading from 0.22.1 to 0.23.1
>> (checked on VM with 0.25 and problem still exists). Task table is not
>> populated with data. I try to find an issue for this but I only found this
>> email where I see same problem on Abdul's screens (I attached one to show
>> my problem).
>> I've checked difference between /master/state.json from version 0.22.1
>> and 0.23.1 and it looks like failed/killed/lost/stage/started_tasks entries
>> are missing? Am I right? Where I can find them now?
>>
>> Thanks
>> Tomek
>>
>> śr., 4.11.2015 o 21:09 użytkownik Abdul Jabbar Azam <aj...@gmail.com>
>> napisał:
>>
>>> Hello,
>>> Thanks for that. That means that the offers that arent appearing are
>>> being used or being held by something. I'll look in the logs to see if
>>> that's the case.
>>>
>>> On Wed, 4 Nov 2015, 17:31 haosdent <ha...@gmail.com> wrote:
>>>
>>>> Oh, yes. But so far the offer should in webui is outstanding offers
>>>> which not yet be accepted. I create the rename ticket here
>>>> https://issues.apache.org/jira/browse/MESOS-3817
>>>>
>>>> On Tue, Nov 3, 2015 at 5:56 AM, Abdul Jabbar Azam <aj...@gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> I found out about the metrics snapshot screen(
>>>>> http://172.16.2.60:5050/metrics/snapshot) and got the result at the
>>>>> bottom of the email
>>>>>
>>>>> I can see that the offers stuff is working, even though it must have
>>>>> worked before, because I was running multiple instances of a test bash
>>>>> script.
>>>>>
>>>>> As a beginner I do find the offers screen a bit confusing though. I
>>>>> would prefer to see offers and state changes over time.
>>>>>
>>>>> {
>>>>>
>>>>> - allocator/event_queue_dispatches: 0,
>>>>> - master/cpus_percent: 0,
>>>>> - master/cpus_revocable_percent: 0,
>>>>> - master/cpus_revocable_total: 0,
>>>>> - master/cpus_revocable_used: 0,
>>>>> - master/cpus_total: 12,
>>>>> - master/cpus_used: 0,
>>>>> - master/disk_percent: 0,
>>>>> - master/disk_revocable_percent: 0,
>>>>> - master/disk_revocable_total: 0,
>>>>> - master/disk_revocable_used: 0,
>>>>> - master/disk_total: 2084062,
>>>>> - master/disk_used: 0,
>>>>> - master/dropped_messages: 4,
>>>>> - master/elected: 1,
>>>>> - master/event_queue_dispatches: 21,
>>>>> - master/event_queue_http_requests: 0,
>>>>> - master/event_queue_messages: 0,
>>>>> - master/frameworks_active: 1,
>>>>> - master/frameworks_connected: 1,
>>>>> - master/frameworks_disconnected: 0,
>>>>> - master/frameworks_inactive: 0,
>>>>> - master/invalid_framework_to_executor_messages: 0,
>>>>> - master/invalid_status_update_acknowledgements: 0,
>>>>> - master/invalid_status_updates: 0,
>>>>> - master/mem_percent: 0,
>>>>> - master/mem_revocable_percent: 0,
>>>>> - master/mem_revocable_total: 0,
>>>>> - master/mem_revocable_used: 0,
>>>>> - master/mem_total: 12632,
>>>>> - master/mem_used: 0,
>>>>> - master/messages_authenticate: 0,
>>>>> - master/messages_deactivate_framework: 0,
>>>>> - master/messages_decline_offers: 4,
>>>>> - master/messages_exited_executor: 0,
>>>>> - master/messages_framework_to_executor: 0,
>>>>> - master/messages_kill_task: 0,
>>>>> - master/messages_launch_tasks: 0,
>>>>> - master/messages_reconcile_tasks: 0,
>>>>> - master/messages_register_framework: 0,
>>>>> - master/messages_register_slave: 0,
>>>>> - master/messages_reregister_framework: 1,
>>>>> - master/messages_reregister_slave: 3,
>>>>> - master/messages_resource_request: 0,
>>>>> - master/messages_revive_offers: 1,
>>>>> - master/messages_status_update: 0,
>>>>> - master/messages_status_update_acknowledgement: 0,
>>>>> - master/messages_unregister_framework: 0,
>>>>> - master/messages_unregister_slave: 0,
>>>>> - master/messages_update_slave: 3,
>>>>> - master/outstanding_offers: 0,
>>>>> - master/recovery_slave_removals: 0,
>>>>> - master/slave_registrations: 0,
>>>>> - master/slave_removals: 0,
>>>>> - master/slave_removals/reason_registered: 0,
>>>>> - master/slave_removals/reason_unhealthy: 0,
>>>>> - master/slave_removals/reason_unregistered: 0,
>>>>> - master/slave_reregistrations: 3,
>>>>> - master/slave_shutdowns_canceled: 0,
>>>>> - master/slave_shutdowns_completed: 0,
>>>>> - master/slave_shutdowns_scheduled: 0,
>>>>> - master/slaves_active: 3,
>>>>> - master/slaves_connected: 3,
>>>>> - master/slaves_disconnected: 0,
>>>>> - master/slaves_inactive: 0,
>>>>> - master/tasks_error: 0,
>>>>> - master/tasks_failed: 0,
>>>>> - master/tasks_finished: 0,
>>>>> - master/tasks_killed: 0,
>>>>> - master/tasks_lost: 0,
>>>>> - master/tasks_running: 0,
>>>>> - master/tasks_staging: 0,
>>>>> - master/tasks_starting: 0,
>>>>> - master/uptime_secs: 21.317382912,
>>>>> - master/valid_framework_to_executor_messages: 0,
>>>>> - master/valid_status_update_acknowledgements: 0,
>>>>> - master/valid_status_updates: 0,
>>>>> - registrar/queued_operations: 0,
>>>>> - registrar/registry_size_bytes: 746,
>>>>> - registrar/state_fetch_ms: 22.148096,
>>>>> - registrar/state_store_ms: 10.608128,
>>>>> - registrar/state_store_ms/count: 4,
>>>>> - registrar/state_store_ms/max: 16.499968,
>>>>> - registrar/state_store_ms/min: 10.608128,
>>>>> - registrar/state_store_ms/p50: 15.01504,
>>>>> - registrar/state_store_ms/p90: 16.4582656,
>>>>> - registrar/state_store_ms/p95: 16.4791168,
>>>>> - registrar/state_store_ms/p99: 16.49579776,
>>>>> - registrar/state_store_ms/p999: 16.499550976,
>>>>> - registrar/state_store_ms/p9999: 16.4999262976,
>>>>> - system/cpus_total: 2,
>>>>> - system/load_15min: 0.07,
>>>>> - system/load_1min: 0.77,
>>>>> - system/load_5min: 0.22,
>>>>> - system/mem_free_bytes: 7682621440,
>>>>> - system/mem_total_bytes: 8372236288
>>>>>
>>>>> }
>>>>>
>>>>> On Mon, 2 Nov 2015 at 12:39 Guangya Liu <gy...@gmail.com> wrote:
>>>>>
>>>>>> Just echo Alex, yes, once the outstanding offer is accepted by
>>>>>> framework, the master will remove the offer. Thanks!
>>>>>>
>>>>>> On Mon, Nov 2, 2015 at 8:13 PM, Alex Rukletsov <al...@mesosphere.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Haosdent,
>>>>>>>
>>>>>>> I don't remember exactly (and I'm from my phone now), but I think
>>>>>>> offers mean outstanding offers. Which means once it's accepted, it's no
>>>>>>> longer an offer. Could you please verify that and file a rename ticket?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Alex
>>>>>>> On 2 Nov 2015 6:24 am, "haosdent" <ha...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hmm, after check current code. Mesos would removeOffer after the
>>>>>>>> framework accept offer.
>>>>>>>>
>>>>>>>> On Mon, Nov 2, 2015 at 11:08 AM, haosdent <ha...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Could you create a ticket in
>>>>>>>>> https://issues.apache.org/jira/browse/MESOS ? I think Mesos have
>>>>>>>>> some problems in state.json endpoint. I am digging into this.
>>>>>>>>>
>>>>>>>>> On Mon, Nov 2, 2015 at 6:01 AM, Abdul Jabbar Azam <
>>>>>>>>> ajazam@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I'm new to mesos. Over the past few days I setup a mesos cluster.
>>>>>>>>>> I can send it a test job and can see that it is working by looking at
>>>>>>>>>> master web ui[image: Screen Shot 2015-11-01 at 21.44.16.png]
>>>>>>>>>> Ignore the LOST and FAILED states. They were tasks that were
>>>>>>>>>> running when I was using mesos 0.25.0. I didn't clear zookeeper before
>>>>>>>>>> running mesos 0.24.1 on the same cluster.
>>>>>>>>>>
>>>>>>>>>> My problem is that the Offers screen isn't showing anything. I
>>>>>>>>>> don't know whether there is something wrong. Has anybody experienced this
>>>>>>>>>> before?
>>>>>>>>>>
>>>>>>>>>> I've attached the other screens as well.
>>>>>>>>>>
>>>>>>>>>> I'm using Ubuntu Server 14.04.3 LTS,mesos-0.24.1, zookeeper
>>>>>>>>>> 3.4.6, marathon-0.11.1, JDK 8u66
>>>>>>>>>>
>>>>>>>>>> Total nodes is 5 where 4 are agents/slaves and 1 is the mesos
>>>>>>>>>> master, zookeeper and marathon node. I'm not allowed to have any more
>>>>>>>>>> servers at home ;)
>>>>>>>>>>
>>>>>>>>>> I created an ansible script so reinstalling with different
>>>>>>>>>> version number combinations is not a problem.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> Abdul Jabbar Azam
>>>>>>>>>> twitter: @ajazam
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Best Regards,
>>>>>>>>> Haosdent Huang
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Haosdent Huang
>>>>>>>>
>>>>>>> --
>>>>> Regards
>>>>>
>>>>> Abdul Jabbar Azam
>>>>> twitter: @ajazam
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Haosdent Huang
>>>>
>>> --
>>> Regards
>>>
>>> Abdul Jabbar Azam
>>> twitter: @ajazam
>>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: mesos 0.24.1 and 0.25.0 offers web ui not appearing to work
Posted by haosdent <ha...@gmail.com>.
This one should be fixed since 0.25
https://issues.apache.org/jira/browse/MESOS-3282
On Wed, Jan 13, 2016 at 5:59 PM, Tomek Janiszewski <ja...@gmail.com>
wrote:
> Hi
>
> I've got problem with web UI after upgrading from 0.22.1 to 0.23.1
> (checked on VM with 0.25 and problem still exists). Task table is not
> populated with data. I try to find an issue for this but I only found this
> email where I see same problem on Abdul's screens (I attached one to show
> my problem).
> I've checked difference between /master/state.json from version 0.22.1 and
> 0.23.1 and it looks like failed/killed/lost/stage/started_tasks entries are
> missing? Am I right? Where I can find them now?
>
> Thanks
> Tomek
>
> śr., 4.11.2015 o 21:09 użytkownik Abdul Jabbar Azam <aj...@gmail.com>
> napisał:
>
>> Hello,
>> Thanks for that. That means that the offers that arent appearing are
>> being used or being held by something. I'll look in the logs to see if
>> that's the case.
>>
>> On Wed, 4 Nov 2015, 17:31 haosdent <ha...@gmail.com> wrote:
>>
>>> Oh, yes. But so far the offer should in webui is outstanding offers
>>> which not yet be accepted. I create the rename ticket here
>>> https://issues.apache.org/jira/browse/MESOS-3817
>>>
>>> On Tue, Nov 3, 2015 at 5:56 AM, Abdul Jabbar Azam <aj...@gmail.com>
>>> wrote:
>>>
>>>>
>>>> I found out about the metrics snapshot screen(
>>>> http://172.16.2.60:5050/metrics/snapshot) and got the result at the
>>>> bottom of the email
>>>>
>>>> I can see that the offers stuff is working, even though it must have
>>>> worked before, because I was running multiple instances of a test bash
>>>> script.
>>>>
>>>> As a beginner I do find the offers screen a bit confusing though. I
>>>> would prefer to see offers and state changes over time.
>>>>
>>>> {
>>>>
>>>> - allocator/event_queue_dispatches: 0,
>>>> - master/cpus_percent: 0,
>>>> - master/cpus_revocable_percent: 0,
>>>> - master/cpus_revocable_total: 0,
>>>> - master/cpus_revocable_used: 0,
>>>> - master/cpus_total: 12,
>>>> - master/cpus_used: 0,
>>>> - master/disk_percent: 0,
>>>> - master/disk_revocable_percent: 0,
>>>> - master/disk_revocable_total: 0,
>>>> - master/disk_revocable_used: 0,
>>>> - master/disk_total: 2084062,
>>>> - master/disk_used: 0,
>>>> - master/dropped_messages: 4,
>>>> - master/elected: 1,
>>>> - master/event_queue_dispatches: 21,
>>>> - master/event_queue_http_requests: 0,
>>>> - master/event_queue_messages: 0,
>>>> - master/frameworks_active: 1,
>>>> - master/frameworks_connected: 1,
>>>> - master/frameworks_disconnected: 0,
>>>> - master/frameworks_inactive: 0,
>>>> - master/invalid_framework_to_executor_messages: 0,
>>>> - master/invalid_status_update_acknowledgements: 0,
>>>> - master/invalid_status_updates: 0,
>>>> - master/mem_percent: 0,
>>>> - master/mem_revocable_percent: 0,
>>>> - master/mem_revocable_total: 0,
>>>> - master/mem_revocable_used: 0,
>>>> - master/mem_total: 12632,
>>>> - master/mem_used: 0,
>>>> - master/messages_authenticate: 0,
>>>> - master/messages_deactivate_framework: 0,
>>>> - master/messages_decline_offers: 4,
>>>> - master/messages_exited_executor: 0,
>>>> - master/messages_framework_to_executor: 0,
>>>> - master/messages_kill_task: 0,
>>>> - master/messages_launch_tasks: 0,
>>>> - master/messages_reconcile_tasks: 0,
>>>> - master/messages_register_framework: 0,
>>>> - master/messages_register_slave: 0,
>>>> - master/messages_reregister_framework: 1,
>>>> - master/messages_reregister_slave: 3,
>>>> - master/messages_resource_request: 0,
>>>> - master/messages_revive_offers: 1,
>>>> - master/messages_status_update: 0,
>>>> - master/messages_status_update_acknowledgement: 0,
>>>> - master/messages_unregister_framework: 0,
>>>> - master/messages_unregister_slave: 0,
>>>> - master/messages_update_slave: 3,
>>>> - master/outstanding_offers: 0,
>>>> - master/recovery_slave_removals: 0,
>>>> - master/slave_registrations: 0,
>>>> - master/slave_removals: 0,
>>>> - master/slave_removals/reason_registered: 0,
>>>> - master/slave_removals/reason_unhealthy: 0,
>>>> - master/slave_removals/reason_unregistered: 0,
>>>> - master/slave_reregistrations: 3,
>>>> - master/slave_shutdowns_canceled: 0,
>>>> - master/slave_shutdowns_completed: 0,
>>>> - master/slave_shutdowns_scheduled: 0,
>>>> - master/slaves_active: 3,
>>>> - master/slaves_connected: 3,
>>>> - master/slaves_disconnected: 0,
>>>> - master/slaves_inactive: 0,
>>>> - master/tasks_error: 0,
>>>> - master/tasks_failed: 0,
>>>> - master/tasks_finished: 0,
>>>> - master/tasks_killed: 0,
>>>> - master/tasks_lost: 0,
>>>> - master/tasks_running: 0,
>>>> - master/tasks_staging: 0,
>>>> - master/tasks_starting: 0,
>>>> - master/uptime_secs: 21.317382912,
>>>> - master/valid_framework_to_executor_messages: 0,
>>>> - master/valid_status_update_acknowledgements: 0,
>>>> - master/valid_status_updates: 0,
>>>> - registrar/queued_operations: 0,
>>>> - registrar/registry_size_bytes: 746,
>>>> - registrar/state_fetch_ms: 22.148096,
>>>> - registrar/state_store_ms: 10.608128,
>>>> - registrar/state_store_ms/count: 4,
>>>> - registrar/state_store_ms/max: 16.499968,
>>>> - registrar/state_store_ms/min: 10.608128,
>>>> - registrar/state_store_ms/p50: 15.01504,
>>>> - registrar/state_store_ms/p90: 16.4582656,
>>>> - registrar/state_store_ms/p95: 16.4791168,
>>>> - registrar/state_store_ms/p99: 16.49579776,
>>>> - registrar/state_store_ms/p999: 16.499550976,
>>>> - registrar/state_store_ms/p9999: 16.4999262976,
>>>> - system/cpus_total: 2,
>>>> - system/load_15min: 0.07,
>>>> - system/load_1min: 0.77,
>>>> - system/load_5min: 0.22,
>>>> - system/mem_free_bytes: 7682621440,
>>>> - system/mem_total_bytes: 8372236288
>>>>
>>>> }
>>>>
>>>> On Mon, 2 Nov 2015 at 12:39 Guangya Liu <gy...@gmail.com> wrote:
>>>>
>>>>> Just echo Alex, yes, once the outstanding offer is accepted by
>>>>> framework, the master will remove the offer. Thanks!
>>>>>
>>>>> On Mon, Nov 2, 2015 at 8:13 PM, Alex Rukletsov <al...@mesosphere.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Haosdent,
>>>>>>
>>>>>> I don't remember exactly (and I'm from my phone now), but I think
>>>>>> offers mean outstanding offers. Which means once it's accepted, it's no
>>>>>> longer an offer. Could you please verify that and file a rename ticket?
>>>>>>
>>>>>> Thanks,
>>>>>> Alex
>>>>>> On 2 Nov 2015 6:24 am, "haosdent" <ha...@gmail.com> wrote:
>>>>>>
>>>>>>> Hmm, after check current code. Mesos would removeOffer after the
>>>>>>> framework accept offer.
>>>>>>>
>>>>>>> On Mon, Nov 2, 2015 at 11:08 AM, haosdent <ha...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Could you create a ticket in
>>>>>>>> https://issues.apache.org/jira/browse/MESOS ? I think Mesos have
>>>>>>>> some problems in state.json endpoint. I am digging into this.
>>>>>>>>
>>>>>>>> On Mon, Nov 2, 2015 at 6:01 AM, Abdul Jabbar Azam <ajazam@gmail.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I'm new to mesos. Over the past few days I setup a mesos cluster.
>>>>>>>>> I can send it a test job and can see that it is working by looking at
>>>>>>>>> master web ui[image: Screen Shot 2015-11-01 at 21.44.16.png]
>>>>>>>>> Ignore the LOST and FAILED states. They were tasks that were
>>>>>>>>> running when I was using mesos 0.25.0. I didn't clear zookeeper before
>>>>>>>>> running mesos 0.24.1 on the same cluster.
>>>>>>>>>
>>>>>>>>> My problem is that the Offers screen isn't showing anything. I
>>>>>>>>> don't know whether there is something wrong. Has anybody experienced this
>>>>>>>>> before?
>>>>>>>>>
>>>>>>>>> I've attached the other screens as well.
>>>>>>>>>
>>>>>>>>> I'm using Ubuntu Server 14.04.3 LTS,mesos-0.24.1, zookeeper 3.4.6,
>>>>>>>>> marathon-0.11.1, JDK 8u66
>>>>>>>>>
>>>>>>>>> Total nodes is 5 where 4 are agents/slaves and 1 is the mesos
>>>>>>>>> master, zookeeper and marathon node. I'm not allowed to have any more
>>>>>>>>> servers at home ;)
>>>>>>>>>
>>>>>>>>> I created an ansible script so reinstalling with different version
>>>>>>>>> number combinations is not a problem.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> Abdul Jabbar Azam
>>>>>>>>> twitter: @ajazam
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Haosdent Huang
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Haosdent Huang
>>>>>>>
>>>>>> --
>>>> Regards
>>>>
>>>> Abdul Jabbar Azam
>>>> twitter: @ajazam
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>> --
>> Regards
>>
>> Abdul Jabbar Azam
>> twitter: @ajazam
>>
>
--
Best Regards,
Haosdent Huang