You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2014/04/15 02:03:22 UTC

[jira] [Commented] (HBASE-10874) Use just one Jetty server for master web UI

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

Jimmy Xiang commented on HBASE-10874:
-------------------------------------

There seems to be a way to do it with the current HttpServer. Let me give it a try.

> Use just one Jetty server for master web UI
> -------------------------------------------
>
>                 Key: HBASE-10874
>                 URL: https://issues.apache.org/jira/browse/HBASE-10874
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, UI
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>
> In HBase-10815, we introduced a separate Jetty server to redirect requests to original master web UI port to the new shared info server. The reason for the new Jetty server is because our InfoServer extends from the deprecated hadoop HttpServer that doesn't support listening to multiple ports. We should either have our own info server, or use the new version of HttpServer (if it supports listening to multiple ports). So that we have just one Jetty server for web UI.



--
This message was sent by Atlassian JIRA
(v6.2#6252)