[ 
https://issues.apache.org/jira/browse/MESOS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735848#comment-14735848
 ] 

Erik Weathers commented on MESOS-2743:
--------------------------------------

hey [~adam-mesos]: can you please provide a brief explanation about why "only 
custom executors are known to the master"?

Prior to that statement, I *was* hopeful that the fix in this ticket 
(MESOS-2743) would also fix the following webui behavior I observed in 
mesos-0.22.1: when I drill into the Executor-view in the UI, I see a blank 
"Executor Name:" value, despite the {{executor_name}} appearing in 
{{http://WORKER_HOST_IP:5051/monitor/statistics.json}}
* FYI, Executor-view UI URL (in mesos-0.22.1):
** 
{{http://MASTER_IP:5050/slaves/SLAVE_ID/frameworks/FRAMEWORK_ID/executors/EXECUTOR_ID}}

I noted that the {{master/state.json}} endpoint that I believe drives the webui 
doesn't include the {{executor_name}} (at least in mesos-0.22.1) and thus this 
ticket (MESOS-2743) seemed like it might fix the problem I observed, since the 
executor name *is* in {{ExecutorInfo}}.  But your statement about "custom 
executors" gave me pause.  So I'm wondering if I need to file a bug for the 
above behavior instead.

Thanks!

> Include ExecutorInfos for custom executors in master/state.json
> ---------------------------------------------------------------
>
>                 Key: MESOS-2743
>                 URL: https://issues.apache.org/jira/browse/MESOS-2743
>             Project: Mesos
>          Issue Type: Improvement
>          Components: json api
>            Reporter: Adam B
>            Assignee: haosdent
>              Labels: mesosphere
>             Fix For: 0.23.0
>
>
> The slave/state.json already reports executorInfos:
> https://github.com/apache/mesos/blob/0.22.1/src/slave/http.cpp#L215-219
> Would be great to see this in the master/state.json as well, so external 
> tools don't have to query each slave to find out executor resources, sandbox 
> directories, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to