[
https://issues.apache.org/jira/browse/HBASE-23551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allan Espinosa updated HBASE-23551:
-----------------------------------
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.
was:
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.
> random high ports not reported properly in the UI
> -------------------------------------------------
>
> Key: HBASE-23551
> URL: https://issues.apache.org/jira/browse/HBASE-23551
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 2.2.2
> Reporter: Allan Espinosa
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
