You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2019/10/30 18:38:07 UTC

[GitHub] [incubator-pinot] kishoreg commented on issue #4525: Pinot server replacement in Cloud where we have no control over hostname

kishoreg commented on issue #4525: Pinot server replacement in Cloud where we have no control over hostname
URL: https://github.com/apache/incubator-pinot/issues/4525#issuecomment-548055689
 
 
   > Here's how we can plan our PRs (based on Ting's recommendation)
   > 
   > 1. PR to decouple using instance name/ID for routing requests (basically don't assume instance name/ID is a valid discoverable host name. Instead use this iD to look up the real host name)
   This can be done asap.
   > 2. PR to change HelixServerStarter to accept a logical instance iD, host and port for starting a server.
   host and port are optional, right?. If the instanceId already exists in Helix, we should change the host/port in the instanceconfig rt.
   > 
   > @kishoreg @mayankshriv any thoughts on this before I proceed ?
   
   

----------------------------------------------------------------
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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org