You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "longfei (JIRA)" <ji...@apache.org> on 2018/02/01 09:20:00 UTC

[jira] [Updated] (MESOS-8523) Webui does not show frameworks/executor when hostname is unreachable

     [ https://issues.apache.org/jira/browse/MESOS-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

longfei updated MESOS-8523:
---------------------------
    Description: 
Here is my case: I have a  machine with an IP 10.115.13.142, whose hostname is n115-013-142.byted.org. However, it is a cloud machine in a foreign region. And I can only visit it with IP, but not hostname.

  !image-2018-02-01-16-59-24-093.png!

As a result,  I can't see any frameworks/executors from the Webui since the /state and /monitor/statistics APIs are all called with {color:#333333}hostnames{color}.

!image-2018-02-01-17-13-59-420.png!

I {color:#ff0000}replaced hostnames with IPs in controllers.js{color} and it worked fine.

!image-2018-02-01-17-08-54-897.png!

So I'm wondering what's the advantage of using hostnames over IPs. 

  was:
Here is my case: I have a  machine with an IP 10.115.13.142, whose hostname is n115-013-142.byted.org. However, it is a cloud machine in a foreign region. And I can only visit it with IP, but not hostname.

  !image-2018-02-01-16-59-24-093.png!

As a result,  I can't see any frameworks/executors from the Webui since the /state and /monitor/statistics APIs are all called with {color:#333333}hostnames{color}.

!image-2018-02-01-17-13-59-420.png!

I {color:#FF0000}replaced hostnames with IPs{color} and it worked fine.

!image-2018-02-01-17-08-54-897.png!

So I'm wondering what's the advantage of using hostnames over IPs. 


> Webui does not show frameworks/executor when hostname is unreachable
> --------------------------------------------------------------------
>
>                 Key: MESOS-8523
>                 URL: https://issues.apache.org/jira/browse/MESOS-8523
>             Project: Mesos
>          Issue Type: Bug
>          Components: webui
>    Affects Versions: 1.3.1, 1.4.1, 1.5.2
>         Environment: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux
>            Reporter: longfei
>            Priority: Major
>              Labels: Hostname, WebUI
>         Attachments: image-2018-02-01-16-59-24-093.png, image-2018-02-01-17-08-54-897.png, image-2018-02-01-17-13-59-420.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Here is my case: I have a  machine with an IP 10.115.13.142, whose hostname is n115-013-142.byted.org. However, it is a cloud machine in a foreign region. And I can only visit it with IP, but not hostname.
>   !image-2018-02-01-16-59-24-093.png!
> As a result,  I can't see any frameworks/executors from the Webui since the /state and /monitor/statistics APIs are all called with {color:#333333}hostnames{color}.
> !image-2018-02-01-17-13-59-420.png!
> I {color:#ff0000}replaced hostnames with IPs in controllers.js{color} and it worked fine.
> !image-2018-02-01-17-08-54-897.png!
> So I'm wondering what's the advantage of using hostnames over IPs. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)