On a brand new installation without a tunnel, I get the same
behavior on AWS builds (external IP to users of GUI, internal IP between
the members of the cluster). I believe the solution is to reconfigure
the IP and hostname files so that the external IP is recognized for the
GUI and the internal IP communication between master and slave nodes and
zookeeper, but unsure how to do this correctly. Everything else appears
to function correctly.
I agree this behavior never happened on earlier versions as stated.
What you see is all the correct information on all screen of the Mesos
GUI, but you have that circular progressive backoff retry popup every
2^N {( 1 to 8) ==> (2 to 256)} seconds) repeat.
Do you add multiple IPs to those files? Or change it to external IP
only? Do you just change Mesos or Zookeeper and Marathon and Slaves as well?
Thanks in advance .... for a place in documentation to look for that
kind of correct setup.
On 9/11/2017 10:44 PM, Aaron Wood wrote:
Hey Ben,
There was a change sometime after Mesos 1.0.x (I think) that altered how
the leader state was obtained
https://github.com/apache/mesos/blob/master/src/webui/master/static/js/controllers.js#L362-L364
This seems to be an intended change but this causes UI error modals to
continually pop up stating that the leader could not be reached when
accessing the UI over a tunnel. The errors also show when you try to access
agent info among other things throughout the angular app.
I'm curious, how many people using Mesos access the UI over a tunnel? Is
there any harm in reverting this functionality to how it was in the 1.0.x
days? I'm sure there was some important reason as to why this change was
made, I'm just not aware of it. From my understanding many of the ops folks
in our org use the UI but almost always over a tunnel. Once more groups in
the org upgrade to newer versions of Mesos they will be facing this issue
almost on a daily basis.
Thanks,
Aaron
On Mon, Sep 11, 2017 at 2:59 PM, Benjamin Mahler <bmah...@apache.org> wrote:
Hi folks,
Over time the webui has lagged behind for some of the features that have
been added. I'm currently tracking what's required to catch it up here:
https://issues.apache.org/jira/browse/MESOS-6440
If you know of other features that make sense to display in the webui, feel
free to file a ticket under this epic (or link it as related if it falls
under a different epic) and let me know. For example, I just filed another
one within it for displaying task health information.
Also feel free to make contributions to the webui even if you don't feel
that you're knowledgable on the frontend side of things. The majority of
webui changes are very easy and provide a lot of value to users who
interact with it on a regular basis!
If you'd like to contribute to the webui, there are a lot of easy tickets
to get started with, here is one example that I would be happy to assist
with: https://issues.apache.org/jira/browse/MESOS-7962
Thanks!
Ben
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
