You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Haripriya Ayyalasomayajula <ah...@gmail.com> on 2015/12/02 21:17:52 UTC

mesos ui best practise - mesos cluster in HA

Hi all,

I am having a mesos cluster  (version 0.25.0) running in with 3 masters. I
am getting back to the community regarding the best practise that can be
adopted.

-I want to access the UI from a login node. How can I use haproxy in this
case? I have the following HAProxy configuration file on the login node
which has access to the three nodes running masters (servers with ip1, ip2,
ip3).

#---------------------------------------------------------------------

# Proxy for the mesos-master console

#---------------------------------------------------------------------


listen mesos-master 0.0.0.0:5050

    mode http

    option forwardfor



        server server1 ip1:5050 check

        server server2 ip2:5050 check

        server server3 ip3:5050 check

---

I'd greatly appreciate any inputs here.

Thanks!

-- 
Regards,
Haripriya Ayyalasomayajula

Re: mesos ui best practise - mesos cluster in HA

Posted by Haripriya Ayyalasomayajula <ah...@gmail.com>.
Jeremy,

This works for me!! Thanks a lot!

All,

Thanks for suggesting the possible ways I can do it.

On Wed, Dec 2, 2015 at 6:50 PM, Jeremy Olexa <jo...@spscommerce.com> wrote:

> This is what we use in haproxy:
>
> backend master_cluster
>   option httpclose
>   option forwardfor
>   mode http
>   option     httpchk GET /metrics/snapshot
>   http-check expect string master\/elected":1
>   server master-0 ip1:5050 check
>   server master-1 ip2:5050 check
>   server master-2 ip3:5050 check
>
> Hope it helps,
> Jeremy
>
> ________________________________________
> From: Laurie Clark-Michalek <la...@qubit.com>
> Sent: Wednesday, December 2, 2015 4:30 PM
> To: user@mesos.apache.org
> Subject: Re: mesos ui best practise - mesos cluster in HA
>
> You can check which is the current master by looking for the number of
> active slaves in state.json; if it's not zero, then the node is the
> current master. I'm away from a computer atm, but I can provide a full
> haproxy health check config if that'd be useful.
>
> That said, it'd be really great if we could get a /is_master endpoint
> or something for this use; trying to do this with nginx has driven me
> to the brink of madness.
>
> On 2 December 2015 at 20:48, Rodrick Brown <ro...@orchard-app.com>
> wrote:
> > There's really no use mesos-dns and just point your browser to
> > http://leader.mesos:5050 to reach the active master.
> >
> >> On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula
> >> <ah...@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I am having a mesos cluster  (version 0.25.0) running in with 3
> masters. I
> >> am getting back to the community regarding the best practise that can be
> >> adopted.
> >>
> >> -I want to access the UI from a login node. How can I use haproxy in
> this
> >> case? I have the following HAProxy configuration file on the login node
> >> which has access to the three nodes running masters (servers with ip1,
> ip2,
> >> ip3).
> >>
> >> #---------------------------------------------------------------------
> >>
> >> # Proxy for the mesos-master console
> >>
> >> #---------------------------------------------------------------------
> >>
> >>
> >> listen mesos-master 0.0.0.0:5050
> >>
> >>     mode http
> >>
> >>     option forwardfor
> >>
> >>
> >>
> >>         server server1 ip1:5050 check
> >>
> >>         server server2 ip2:5050 check
> >>
> >>         server server3 ip3:5050 check
> >>
> >> ---
> >>
> >> I'd greatly appreciate any inputs here.
> >>
> >> Thanks!
> >>
> >>
> >> --
> >> Regards,
> >> Haripriya Ayyalasomayajula
> >>
> >
> > NOTICE TO RECIPIENTS: This communication is confidential and intended for
> > the use of the addressee only. If you are not an intended recipient of
> this
> > communication, please delete it immediately and notify the sender by
> return
> > email. Unauthorized reading, dissemination, distribution or copying of
> this
> > communication is prohibited. This communication does not constitute an
> offer
> > to sell or a solicitation of an indication of interest to purchase any
> loan,
> > security or any other financial product or instrument, nor is it an
> offer to
> > sell or a solicitation of an indication of interest to purchase any
> products
> > or services to any persons who are prohibited from receiving such
> > information under applicable law. The contents of this communication may
> not
> > be accurate or complete and are subject to change without notice. As
> such,
> > Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard")
> > makes no representation regarding the accuracy or completeness of the
> > information contained herein. The intended recipient is advised to
> consult
> > its own professional advisors, including those specializing in legal, tax
> > and accounting matters. Orchard does not provide legal, tax or accounting
> > advice.
>
>
>
> --
> Laurie Clark-Michalek
> Infrastructure Engineer
>
> Qubit – Deliver your big ideas
> 35 King Street,
> Covent Garden
> London, WC2E 8JG
>



-- 
Regards,
Haripriya Ayyalasomayajula

Re: mesos ui best practise - mesos cluster in HA

Posted by Jeremy Olexa <jo...@spscommerce.com>.
This is what we use in haproxy:

backend master_cluster
  option httpclose
  option forwardfor
  mode http
  option     httpchk GET /metrics/snapshot
  http-check expect string master\/elected":1
  server master-0 ip1:5050 check
  server master-1 ip2:5050 check
  server master-2 ip3:5050 check

Hope it helps,
Jeremy

________________________________________
From: Laurie Clark-Michalek <la...@qubit.com>
Sent: Wednesday, December 2, 2015 4:30 PM
To: user@mesos.apache.org
Subject: Re: mesos ui best practise - mesos cluster in HA

You can check which is the current master by looking for the number of
active slaves in state.json; if it's not zero, then the node is the
current master. I'm away from a computer atm, but I can provide a full
haproxy health check config if that'd be useful.

That said, it'd be really great if we could get a /is_master endpoint
or something for this use; trying to do this with nginx has driven me
to the brink of madness.

On 2 December 2015 at 20:48, Rodrick Brown <ro...@orchard-app.com> wrote:
> There's really no use mesos-dns and just point your browser to
> http://leader.mesos:5050 to reach the active master.
>
>> On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula
>> <ah...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I am having a mesos cluster  (version 0.25.0) running in with 3 masters. I
>> am getting back to the community regarding the best practise that can be
>> adopted.
>>
>> -I want to access the UI from a login node. How can I use haproxy in this
>> case? I have the following HAProxy configuration file on the login node
>> which has access to the three nodes running masters (servers with ip1, ip2,
>> ip3).
>>
>> #---------------------------------------------------------------------
>>
>> # Proxy for the mesos-master console
>>
>> #---------------------------------------------------------------------
>>
>>
>> listen mesos-master 0.0.0.0:5050
>>
>>     mode http
>>
>>     option forwardfor
>>
>>
>>
>>         server server1 ip1:5050 check
>>
>>         server server2 ip2:5050 check
>>
>>         server server3 ip3:5050 check
>>
>> ---
>>
>> I'd greatly appreciate any inputs here.
>>
>> Thanks!
>>
>>
>> --
>> Regards,
>> Haripriya Ayyalasomayajula
>>
>
> NOTICE TO RECIPIENTS: This communication is confidential and intended for
> the use of the addressee only. If you are not an intended recipient of this
> communication, please delete it immediately and notify the sender by return
> email. Unauthorized reading, dissemination, distribution or copying of this
> communication is prohibited. This communication does not constitute an offer
> to sell or a solicitation of an indication of interest to purchase any loan,
> security or any other financial product or instrument, nor is it an offer to
> sell or a solicitation of an indication of interest to purchase any products
> or services to any persons who are prohibited from receiving such
> information under applicable law. The contents of this communication may not
> be accurate or complete and are subject to change without notice. As such,
> Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard")
> makes no representation regarding the accuracy or completeness of the
> information contained herein. The intended recipient is advised to consult
> its own professional advisors, including those specializing in legal, tax
> and accounting matters. Orchard does not provide legal, tax or accounting
> advice.



--
Laurie Clark-Michalek
Infrastructure Engineer

Qubit – Deliver your big ideas
35 King Street,
Covent Garden
London, WC2E 8JG

Re: mesos ui best practise - mesos cluster in HA

Posted by Laurie Clark-Michalek <la...@qubit.com>.
You can check which is the current master by looking for the number of
active slaves in state.json; if it's not zero, then the node is the
current master. I'm away from a computer atm, but I can provide a full
haproxy health check config if that'd be useful.

That said, it'd be really great if we could get a /is_master endpoint
or something for this use; trying to do this with nginx has driven me
to the brink of madness.

On 2 December 2015 at 20:48, Rodrick Brown <ro...@orchard-app.com> wrote:
> There's really no use mesos-dns and just point your browser to
> http://leader.mesos:5050 to reach the active master.
>
>> On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula
>> <ah...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I am having a mesos cluster  (version 0.25.0) running in with 3 masters. I
>> am getting back to the community regarding the best practise that can be
>> adopted.
>>
>> -I want to access the UI from a login node. How can I use haproxy in this
>> case? I have the following HAProxy configuration file on the login node
>> which has access to the three nodes running masters (servers with ip1, ip2,
>> ip3).
>>
>> #---------------------------------------------------------------------
>>
>> # Proxy for the mesos-master console
>>
>> #---------------------------------------------------------------------
>>
>>
>> listen mesos-master 0.0.0.0:5050
>>
>>     mode http
>>
>>     option forwardfor
>>
>>
>>
>>         server server1 ip1:5050 check
>>
>>         server server2 ip2:5050 check
>>
>>         server server3 ip3:5050 check
>>
>> ---
>>
>> I'd greatly appreciate any inputs here.
>>
>> Thanks!
>>
>>
>> --
>> Regards,
>> Haripriya Ayyalasomayajula
>>
>
> NOTICE TO RECIPIENTS: This communication is confidential and intended for
> the use of the addressee only. If you are not an intended recipient of this
> communication, please delete it immediately and notify the sender by return
> email. Unauthorized reading, dissemination, distribution or copying of this
> communication is prohibited. This communication does not constitute an offer
> to sell or a solicitation of an indication of interest to purchase any loan,
> security or any other financial product or instrument, nor is it an offer to
> sell or a solicitation of an indication of interest to purchase any products
> or services to any persons who are prohibited from receiving such
> information under applicable law. The contents of this communication may not
> be accurate or complete and are subject to change without notice. As such,
> Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard")
> makes no representation regarding the accuracy or completeness of the
> information contained herein. The intended recipient is advised to consult
> its own professional advisors, including those specializing in legal, tax
> and accounting matters. Orchard does not provide legal, tax or accounting
> advice.



-- 
Laurie Clark-Michalek
Infrastructure Engineer

Qubit – Deliver your big ideas
35 King Street,
Covent Garden
London, WC2E 8JG

Re: mesos ui best practise - mesos cluster in HA

Posted by Rodrick Brown <ro...@orchard-app.com>.
There's really no use mesos-dns and just point your browser to
http://leader.mesos:5050 to reach the active master.

  

> On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula
&lt;aharipriya92@gmail.com&gt; wrote:  

>

>  

>

> Hi all,

>

>  

>

> I am having a mesos cluster  (version 0.25.0) running in with 3 masters. I
am getting back to the community regarding the best practise that can be
adopted.

>

>  

>

> -I want to access the UI from a login node. How can I use haproxy in this
case? I have the following HAProxy configuration file on the login node which
has access to the three nodes running masters (servers with ip1, ip2, ip3).

>

>  

>

> #---------------------------------------------------------------------

>

> # Proxy for the mesos-master console

>

> #---------------------------------------------------------------------

>

>  

>

> listen mesos-master [0.0.0.0:5050](http://0.0.0.0:5050)

>

>     mode http  
>

>     option forwardfor

>

>  
>

>         server server1 ip1:5050 check  
>

>         server server2 ip2:5050 check

>

>         server server3 ip3:5050 check

>

> \---

>

> I'd greatly appreciate any inputs here.

>

> Thanks!

>

>  

>

> \--  

>

> Regards,  
Haripriya Ayyalasomayajula

>

>  


-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide legal, tax or 
accounting advice.