Sure, will do that. Thanks, Jimmy
On Mon, Feb 4, 2013 at 11:17 AM, Aleksandr Shulman <al...@cloudera.com>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 >
