[GitHub] [bookkeeper] ivankelly commented on issue #2214: BP-38 Publish Bookie Service Info on Metadata Service

[GitBox <gi...@apache.org>]

ivankelly commented on issue #2214: BP-38 Publish Bookie Service Info on Metadata Service
URL: https://github.com/apache/bookkeeper/pull/2214#issuecomment-578811354
 
 
   > @eolivelli  If we had a rest endpoint on the bookies, it becomes a lot more cachable.
   We would end up in storing the HTTP endpoint of the bookie and so we won't be able to move the bookie to another DNS name
   
   Sorry, I wasn't clear. I meant (and it's out of scope for this), that we have a http rest endpoint on each bookie, something like /bookies which returns the list of bookies available and all their available endpoints. When a client is creating a ledger, it doesn't need to query ZK (1 + n times), it just hits this endpoint to get the list. The client shouldn't have to know the actual individual bookie DNS addresses. This would be behind a VIP of some kind (like a loadbalancer pointing to a statefulset in k8s).
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services