This *looks like* Hbase was started in standalone mode with a semi-empty hbase-site.xml config with only hbase.rootdir set and no external zookeeper setup.
This means zookeeper was started using /tmp/hbase-hbase/zookeeper[...]. At some point /tmp got cleaned up but since zookeeper was running everything ran normally until your restart. Unfortunately I don't know how to recover from such a scenario. On Thu, Sep 26, 2013 at 6:04 AM, Roy23 <[email protected]> wrote: > Hi Michael, > > Thanks for getting back to me. Really appreciate it.. > > so, for port 2181 -- > > $ ps aux | grep :2181 > suman 16607 0.0 0.0 8104 924 pts/0 S+ 12:55 0:00 grep > --color=auto :2181 > > $ sudo netstat -tulp | grep :2181 > $ > > I did make changes to hbase-site.xml between restarts, it might have been > that hbase had not shut down yet when i made changes ? > > Also this line in hbase-env.sh is commented out, so zookeeper should be > restarted manually since hbase wont start it automatically. > # Tell HBase whether it should manage it's own instance of Zookeeper or > not. > #export HBASE_MANAGES_ZK=true > > > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Needed-to-restart-HBase-Now-Master-won-t-start-tp4051241p4051270.html > Sent from the HBase User mailing list archive at Nabble.com. >
