PQS (really, Avatica[1]) doesn't have a health-check endpoint.
We would need to figure out what it means for Avatica to check its own
health, and export such an endpoint.
[1] https://calcite.apache.org/avatica/docs/
On 8/7/19 4:19 PM, jesse wrote:
After further investigation, I figured there
After further investigation, I figured there are two types of clients: thin
client and thick client.
- thin client talks to PQS, only ELB or PQS http address is supported
- thick client supports ZK
I don't know the PQS heath url yet, not documented anywhere. Any one knows?
On Wed, Aug 7,
I didn't try this personally, but according to the documentation
https://phoenix.apache.org/server.html it has possibility to have ZK-based
load-balancing. Please refer to the "Load balancing" section at the bottom.
On Wed, Aug 7, 2019 at 9:14 PM jesse wrote:
> Thank you all, very helpful
Thank you all, very helpful information.
1) for server side ELB, what is the PQS health check url path?
2) Does Phoenix client library support client-side load-balancing? i. e
client gets list of PQS addresses from ZK, and performs load balancing.
Thus ELB won't be needed.
On Wed, Aug 7,
Great answer, Aleksandr!
Also worth mentioning there is only ever one active HBase Master at a
time. If you have multiple started, one will be active as the master and
the rest will be waiting as a standby in case the current active master
dies for some reason (expectedly or unexpectedly).
Hello.
- Phoenix libs should be installed only on RegionServers.
- QueryServer - it's up to you, PQS can be installed anywhere you want
- No. QueryServer is using ZK quorum to get everything it needs
- If you need to balance traffic with multiply PQSs - then yes, but again -
it's up to you. It is
Our cluster used to have one hbase master, now a secondary is added. For
phonenix, what changes should we make?
- do we have to install new hbase libraries on the new hbase master node?
- do we need to install new query server on the hbase master?
- any configuration changes should we make?
- do
