Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.2.2
-
None
-
None
Description
We want to run HBase on kubernetes and want to investigate hostNetworking for performance and host purposes. We basically set hbase.<>.port,hbase.<>.info.port=0 in our hbase-site.xml . This will allow us to skip kubernetes networking since hbase-related services will bind to random high ports.
We encountered the following bugs in the HBase UI
Active HBase Master:
- Links to Backup masters points to http://<backup-container-host>:<rpc.port> instead of http://<backup-container-host>:<http.info.port>. The http://<backup-container-host>:<rpc.port> endpoint responds with a proper HTTP 404 from the Jetty instance in the backup master process
Backup HBase master
- Links to Active Master points to http://<backup-container-host>:<rpc.port> instead of http://<backup-container-host>:<http.info.port>. The http://<backup-container-host>:<rpc.port> endpoint responds with a proper HTTP 404 from the Jetty instance in the backup master process
Regionservers
- Regionserver running in the same host network as the active hbase master can register
- Regionserver on different hosts (using host networking) connects to a different RPC port in the active HBase master. I can’t figure out which port is this yet.
Attachments
Issue Links
- relates to
-
HBASE-11768 Register region server in zookeeper by ip address
- Closed