chenboat opened a new issue #4525: Pinot server replacement in Cloud where we have no control over hostname URL: https://github.com/apache/incubator-pinot/issues/4525 Pinot server instance ids are formatted as Server_<host>_<port>. These ids are then used in places like table external_view and idealstate. When Pinot brokers construct the routing tables for a query, they use the above instance ids to reconstruct the host/port info to send the Pinot query via HTTP protocol. Right now we try to deploy Pinot in cloud here in Uber. When we replace a machine, we can not get the same hostname of the replaced one. By the current impl, the server instance id will also change due to the changed hostname. That implies the new machine can not be a replacement for the old instance even it has all the data copied to it. We wonder how machine replacement is done in a cloud environment. One proposal we think of is to decouple the server instance id with the underlying communication protocol (e.g., HTTP used for now). In this design, the broker should NOT use the server instance id directly and instead using it to look up from Zookeeper to find out the actual server address. In fact right now these are stored in zk as HELIX_HOST and HELIX_PORT but they are apparently not used in routing table construction. @fx19880617 @mcvsubbu
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
