The web UI came with Hadoop provides some useful information about each
server: for example, jmx, metrics, stacks, log level, conf, and so on.

I was wondering should we add a web UI to REST and Thrift too, as we do for
master and region server.

REST is a little different.  It already hasa web server.  In working on
HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
server.
We have to add several knobs to avoid path mapping conflicts between the
new servlets and the existing REST paths.  I was wondering should we
use a separate web server on a different port for example 8085. For Thrift,
we can use 9095.  That's default port, can be configured.

The benefit to have another web server in REST is that we can get all
Hadoop http server features easily, and will never worry about path mapping
conflicts.  The cons is that it needs another port.

Thanks,
Jimmy

On Sun, Feb 3, 2013 at 8:46 AM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:

> The web UI came with Hadoop provides some useful information about each
> server: for example, jmx, metrics, stacks, log level, conf, and so on.
>
> I was wondering should we add a web UI to REST and Thrift too, as we do for
> master and region server.
>
>
Would be useful I'd say.

> REST is a little different.  It already hasa web server.  In working on
> HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> server.
>

Did it work?  Can you mount the servlets into a new context or as a new
webapp?

> We have to add several knobs to avoid path mapping conflicts between the
> new servlets and the existing REST paths.
Mount the hadoop stuff on to '/this' or '/proc' or '/ui' or '/insight'
or....
>  I was wondering should we
> use a separate web server on a different port for example 8085. For Thrift,
> we can use 9095.  That's default port, can be configured.
>
>
I suppose it makes sense having separate port for thrift (unless we want to
do some hackery) but would be interested in why we'd need to do similar
when we already have a web context going on the REST server?

> The benefit to have another web server in REST is that we can get all
> Hadoop http server features easily, and will never worry about path mapping
> conflicts.  The cons is that it needs another port.
>
Could the context you mount the hadoop servlets on be something that makes
no sense as a REST query?

St.Ack

I never thought it necessary to add a UI to a REST gateway. If you want to
do it, I suggest using a separate configurable service port to the REST
service. Actually, we should add that separate listener/context and move
the /metrics and /jmx servlets that you just added to that.
On Sun, Feb 3, 2013 at 8:46 AM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:

> The web UI came with Hadoop provides some useful information about each
> server: for example, jmx, metrics, stacks, log level, conf, and so on.
>
> I was wondering should we add a web UI to REST and Thrift too, as we do for
> master and region server.
>
> REST is a little different.  It already hasa web server.  In working on
> HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> server.
> We have to add several knobs to avoid path mapping conflicts between the
> new servlets and the existing REST paths.  I was wondering should we
> use a separate web server on a different port for example 8085. For Thrift,
> we can use 9095.  That's default port, can be configured.
>
> The benefit to have another web server in REST is that we can get all
> Hadoop http server features easily, and will never worry about path mapping
> conflicts.  The cons is that it needs another port.
>
> Thanks,
> Jimmy
>

--
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

I filed HBASE-7757.   We can discuss further over there.

Thanks,
Jimmy

On Sun, Feb 3, 2013 at 4:24 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:

> I never thought it necessary to add a UI to a REST gateway. If you want to
> do it, I suggest using a separate configurable service port to the REST
> service. Actually, we should add that separate listener/context and move
> the /metrics and /jmx servlets that you just added to that.
>
>
> On Sun, Feb 3, 2013 at 8:46 AM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:
>
> > The web UI came with Hadoop provides some useful information about each
> > server: for example, jmx, metrics, stacks, log level, conf, and so on.
> >
> > I was wondering should we add a web UI to REST and Thrift too, as we do
> for
> > master and region server.
> >
> > REST is a little different.  It already hasa web server.  In working on
> > HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> > server.
> > We have to add several knobs to avoid path mapping conflicts between the
> > new servlets and the existing REST paths.  I was wondering should we
> > use a separate web server on a different port for example 8085. For
> Thrift,
> > we can use 9095.  That's default port, can be configured.
> >
> > The benefit to have another web server in REST is that we can get all
> > Hadoop http server features easily, and will never worry about path
> mapping
> > conflicts.  The cons is that it needs another port.
> >
> > Thanks,
> > Jimmy
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

This would be really great to see Jimmy! We would need to provide a
sensible default webUI port to avoid conflicts upon upgrade. We should also
make it a command-line parameter like we do now with the service port.

-Aleks S.

On Sunday, February 3, 2013, Jimmy Xiang wrote:

> The web UI came with Hadoop provides some useful information about each
> server: for example, jmx, metrics, stacks, log level, conf, and so on.
>
> I was wondering should we add a web UI to REST and Thrift too, as we do for
> master and region server.
>
> REST is a little different.  It already hasa web server.  In working on
> HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> server.
> We have to add several knobs to avoid path mapping conflicts between the
> new servlets and the existing REST paths.  I was wondering should we
> use a separate web server on a different port for example 8085. For Thrift,
> we can use 9095.  That's default port, can be configured.
>
> The benefit to have another web server in REST is that we can get all
> Hadoop http server features easily, and will never worry about path mapping
> conflicts.  The cons is that it needs another port.
>
> Thanks,
> Jimmy
>
--
Best Regards,

Aleks Shulman
847.814.5804
Cloudera

Sure, will do that.

Thanks,
Jimmy

On Mon, Feb 4, 2013 at 11:17 AM, Aleksandr Shulman <[EMAIL PROTECTED]>wrote:

> This would be really great to see Jimmy! We would need to provide a
> sensible default webUI port to avoid conflicts upon upgrade. We should also
> make it a command-line parameter like we do now with the service port.
>
> -Aleks S.
>
> On Sunday, February 3, 2013, Jimmy Xiang wrote:
>
> > The web UI came with Hadoop provides some useful information about each
> > server: for example, jmx, metrics, stacks, log level, conf, and so on.
> >
> > I was wondering should we add a web UI to REST and Thrift too, as we do
> for
> > master and region server.
> >
> > REST is a little different.  It already hasa web server.  In working on
> > HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> > server.
> > We have to add several knobs to avoid path mapping conflicts between the
> > new servlets and the existing REST paths.  I was wondering should we
> > use a separate web server on a different port for example 8085. For
> Thrift,
> > we can use 9095.  That's default port, can be configured.
> >
> > The benefit to have another web server in REST is that we can get all
> > Hadoop http server features easily, and will never worry about path
> mapping
> > conflicts.  The cons is that it needs another port.
> >
> > Thanks,
> > Jimmy
> >
>
>
> --
> Best Regards,
>
> Aleks Shulman
> 847.814.5804
> Cloudera
>

Perhaps beyond the scope of this discussion, but have you guys played with
Elasticsearch-head [0]? It's not perfect, but it goes a long way to
understanding the basic on-goings of that system. Definitely something to
consider for HBase.

-n

[0]: http://mobz.github.com/elasticsearch-head/

On Sun, Feb 3, 2013 at 8:46 AM, Jimmy Xiang <[EMAIL PROTECTED]> wrote:

> The web UI came with Hadoop provides some useful information about each
> server: for example, jmx, metrics, stacks, log level, conf, and so on.
>
> I was wondering should we add a web UI to REST and Thrift too, as we do for
> master and region server.
>
> REST is a little different.  It already hasa web server.  In working on
> HBASE-7738, I tried to add jmx/metrics servlet to the existing REST web
> server.
> We have to add several knobs to avoid path mapping conflicts between the
> new servlets and the existing REST paths.  I was wondering should we
> use a separate web server on a different port for example 8085. For Thrift,
> we can use 9095.  That's default port, can be configured.
>
> The benefit to have another web server in REST is that we can get all
> Hadoop http server features easily, and will never worry about path mapping
> conflicts.  The cons is that it needs another port.
>
> Thanks,
> Jimmy
>