You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@spark.apache.org by elyast <lu...@gmail.com> on 2014/06/12 04:53:56 UTC
History Server renered page not suitable for load balancing
Hi,
Small issue but still.
I run history server through Marathon and balance it through haproxy. The
problem is that links generated by HistoryPage (links to completed
applications) are absolute, e.g. http://some-server:port/history... , but
instead they should relative just /history, so they can be load balanced.
I can open pull request if needed
Best regards
Lukasz Jastrzebski
--
View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/History-Server-renered-page-not-suitable-for-load-balancing-tp7447.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
Re: History Server renered page not suitable for load balancing
Posted by elyast <lu...@gmail.com>.
Done :)
--
View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/History-Server-renered-page-not-suitable-for-load-balancing-tp7447p8550.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
Re: History Server renered page not suitable for load balancing
Posted by Aaron Davidson <il...@gmail.com>.
A pull request would be great!
On Wed, Jun 11, 2014 at 7:53 PM, elyast <lu...@gmail.com>
wrote:
> Hi,
>
> Small issue but still.
>
> I run history server through Marathon and balance it through haproxy. The
> problem is that links generated by HistoryPage (links to completed
> applications) are absolute, e.g. http://some-server:port/history... , but
> instead they should relative just /history, so they can be load balanced.
>
> I can open pull request if needed
>
> Best regards
> Lukasz Jastrzebski
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/History-Server-renered-page-not-suitable-for-load-balancing-tp7447.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>