[
https://issues.apache.org/jira/browse/MESOS-7908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846604#comment-16846604
]
Rohit Singh commented on MESOS-7908:
------------------------------------
This issue is seen in 1.8.x, Made changes to the code but still UI keeps on
refreshing. Commenting out the code as mentioned above works in 1.6.x but in
1.8.x its not working.
{code:java}
diff --git a/src/webui/app/controllers.js b/src/webui/app/controllers.js
index 42a9fb657..2974abee1 100644
--- a/src/webui/app/controllers.js
+++ b/src/webui/app/controllers.js
@@ -64,13 +64,13 @@
}
function leadingMasterURLPrefix(leader_info) {
- if (leader_info) {
- return '//' + leader_info.hostname + ':' + leader_info.port;
- }
-
+ //if (leader_info) {
+ // return '//' + leader_info.hostname + ':' + leader_info.port;
+ //}
+ var address = '//' + location.hostname + ':' + location.port;
// If we do not have `leader_info` available (e.g. the first
// time we are retrieving state), fallback to the current master.
- return '';
+ return address;
}
// Invokes the pailer, building the endpoint URL with the specified urlPrefix
{code}
I have added the following code. Need some help as 1.6 has some vulnerabilites,
need to upgrade to 1.8.x asap
> Mesos UI Keeps refreshing
> -------------------------
>
> Key: MESOS-7908
> URL: https://issues.apache.org/jira/browse/MESOS-7908
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0, 1.3.1
> Reporter: Lax
> Priority: Major
> Attachments: mesos_ui_refresh.png
>
>
> I tried to upgrade mesos from 1.0.1 to latest and suddenly I see Mesos UI
> keeps refreshing every few seconds. I can say the issue remains at least from
> version 1.1.x onwards.
> The UI refresh will be seen only when you access Mesos thru proxy ports
> (other than 5050) or custom DNS.
> Root cause for this appears to be to be how mesos ui is constructing the end
> point in here:
> https://github.com/apache/mesos/blob/master/src/webui/master/static/js/controllers.js#L362-L365.
> It basically learning mesos host and port from mesos state API response and
> using that to load in the UI. But what you learn will be the internal host
> name(pretty much node name) and port (5050) and it wont work in cases where
> user proxy's the mesos port eg: 9443 in my case and also have custom DNS
> format eg: *mesos-laxmesos4.dev.io*
> So basically when I load mesos ui with URI:
> https://mesos-laxmesos4.dev.io:9443, above pointed API is returning
> https://[my node name]:5050/metrics/... while expected path is
> https://mesos-laxmesos4.dev.io:9443/metrics/...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
