Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

CDH6/CDH7 hbase/bin/start-hbase.sh is missing

avatar
New Contributor

In the cdh6/cdh7 parcels I do not see the lib/hbase/bin/start-hbase.sh script.

In cdh5 we used to use hbase-1.2.0-cdh5.16.1/bin/start-hbase.sh to start hbase in pseudo distributed mode.

Can someone let me know what is the alternative to using hbase in pseudo distributed mode in CDH6/CDH7 ?

 

Thanks,

Sudheendra S.

1 ACCEPTED SOLUTION

avatar
Master Collaborator

Hi @Sudheend,

 

Pseudo-distributed mode means each of the separate processes run on the same server, rather than multiple servers in a cluster. 

 

In CDH6/7, "start-hbase.sh" is not existing anymore, and "service hbase-master start/stop" is also not working anymore. Instead, Cloudera Manager will use multiple scripts to do this. You can check how a HBase role is started in CM by expanding steps and check stderr.log of the running commands. 

 

So the best way is to use Cloudera Manager to install HBase service, you can choose same host to install Master role, RegionServer role. Then you could stop/start the HBase roles via CM > HBase > Instances > Select role > Actions > Stop/Start.

 

Then use jps or ps -ef to check the running processes:

For example:

# jps
7251 DataNode
8019 NodeManager
7253 NameNode
15238 HMaster
11384 HRegionServer
16105 Jps
7085 QuorumPeerMain

 

Regards,

Will

If the answer helps, please accept as solution and click thumbs up.

View solution in original post

2 REPLIES 2

avatar
Master Collaborator

Hi @Sudheend,

 

Pseudo-distributed mode means each of the separate processes run on the same server, rather than multiple servers in a cluster. 

 

In CDH6/7, "start-hbase.sh" is not existing anymore, and "service hbase-master start/stop" is also not working anymore. Instead, Cloudera Manager will use multiple scripts to do this. You can check how a HBase role is started in CM by expanding steps and check stderr.log of the running commands. 

 

So the best way is to use Cloudera Manager to install HBase service, you can choose same host to install Master role, RegionServer role. Then you could stop/start the HBase roles via CM > HBase > Instances > Select role > Actions > Stop/Start.

 

Then use jps or ps -ef to check the running processes:

For example:

# jps
7251 DataNode
8019 NodeManager
7253 NameNode
15238 HMaster
11384 HRegionServer
16105 Jps
7085 QuorumPeerMain

 

Regards,

Will

If the answer helps, please accept as solution and click thumbs up.

avatar
New Contributor

Thanks @willx for sharing a nice idea.

I will setup a real cluster and follow your steps.