hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michał Podsiadłowski <podsiadlow...@gmail.com>
Subject Re: Combining hadoop dataNode process with hbase into single JVM process
Date Thu, 10 Dec 2009 23:59:56 GMT
2009/12/11 Edward Capriolo <edlinuxguru@gmail.com>

> As for lumping all the daemons together, it is technically, possible,
> but they were designed to run separately so that they are easier
> manage. It would probably would make troubleshooting harder. Which sub
> process is causing high cpu. Just because the TaskTracker fails does
> not mean that the DataNode should be down. It is a cool idea though.
> If you want some monitoring hints I'll plug my presentation
> http://www.slideshare.net/cloudera/hw09-monitoring-best-practices
> http://www.cloudera.com/blog/2009/11/09/hadoop-world-monitoring-best-practices-from-ed-capriolo/

Thanks for answer.
We are not planning to use TaskTrackers (no MR jobs only Hbase) so I don't
know if there is a any reason to run it. Can you think of any problems that
can occur? Jetty instances clash between DataNode and Hbase RegionServer for

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message