You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Stavros Kontopoulos (JIRA)" <ji...@apache.org> on 2017/03/04 19:24:45 UTC
[jira] [Comment Edited] (MESOS-4992) sandbox uri does not work
outisde mesos http server
[ https://issues.apache.org/jira/browse/MESOS-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895832#comment-15895832 ]
Stavros Kontopoulos edited comment on MESOS-4992 at 3/4/17 7:24 PM:
--------------------------------------------------------------------
[~bmahler] If you check the code after the lines you mentioned: https://github.com/apache/mesos/blob/8dc71da12c9b91edd2fa6c7b9a0a088b7dbb0ad3/src/webui/master/static/js/controllers.js#L762-L773, certain type of information must be collected inorder this to be successful . Some of this info is in the url but we cannot get any state. We do depend on master state plus we need to fetch the executor dir. Thus, coming from a non mesos page you need to reconstruct the state. Probably there is a method for that eg, when you first enter mesos web ui. Will have a look.
was (Author: skonto):
[~bmahler] If you check the code after those lines: https://github.com/apache/mesos/blob/8dc71da12c9b91edd2fa6c7b9a0a088b7dbb0ad3/src/webui/master/static/js/controllers.js#L762-L773, certain type of information must be collected inorder this to be successful . Some of this info is in the url but we cannot get any state. We do depend on master state plus we need to fetch the executor dir. Thus, coming from a non mesos page you need to reconstruct the state. Probably there is a method for that eg, when you first enter mesos web ui. Will have a look.
> sandbox uri does not work outisde mesos http server
> ---------------------------------------------------
>
> Key: MESOS-4992
> URL: https://issues.apache.org/jira/browse/MESOS-4992
> Project: Mesos
> Issue Type: Bug
> Components: webui
> Affects Versions: 0.27.1
> Reporter: Stavros Kontopoulos
> Assignee: haosdent
> Labels: mesosphere
>
> The SandBox uri of a framework does not work if i just copy paste it to the browser.
> For example the following sandbox uri:
> http://172.17.0.1:5050/#/slaves/50f87c73-79ef-4f2a-95f0-b2b4062b2de6-S0/frameworks/50f87c73-79ef-4f2a-95f0-b2b4062b2de6-0009/executors/driver-20160321155016-0001/browse
> should redirect to:
> http://172.17.0.1:5050/#/slaves/50f87c73-79ef-4f2a-95f0-b2b4062b2de6-S0/browse?path=%2Ftmp%2Fmesos%2Fslaves%2F50f87c73-79ef-4f2a-95f0-b2b4062b2de6-S0%2Fframeworks%2F50f87c73-79ef-4f2a-95f0-b2b4062b2de6-0009%2Fexecutors%2Fdriver-20160321155016-0001%2Fruns%2F60533483-31fb-4353-987d-f3393911cc80
> yet it fails with the message:
> "Failed to find slaves.
> Navigate to the slave's sandbox via the Mesos UI."
> and redirects to:
> http://172.17.0.1:5050/#/
> It is an issue for me because im working on expanding the mesos spark ui with sandbox uri, The other option is to get the slave info and parse the json file there and get executor paths not so straightforward or elegant though.
> Moreover i dont see the runs/container_id in the Mesos Proto Api. I guess this is hidden info, this is the needed piece of info to re-write the uri without redirection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)