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 2021/11/29 23:29:49 UTC
[GitHub] [pinot] dongxiaoman opened a new issue #7837: PrestoDB/Trino connector cannot connect to Pinot after Pinot cluster updates its instance hostname
dongxiaoman opened a new issue #7837:
URL: https://github.com/apache/pinot/issues/7837
If the Pinot cluster adopts https://github.com/apache/pinot/pull/7064 to update its Helix hostname to Pinot Helix Instance, the PrestoDB/Trino connector will not be able to connect to Pinot any more.
The main reason is inside PrestoDB/Trino code, that it tries to derive `hostname:port` connection string to each Pinot server instance by using the traditional naming convention.
For example, if our server instance name in Pinot is `Server_fw-1.service.consul_8099`, PrestoDB/Trino directly regex parse the name to find out that it should connect via `fw-1.service.consul:8099`. This works fine if the Pinot Server registers itself to DNS FQDN name as `fw-1.service.consul:8099`; however, if we adopt https://github.com/apache/pinot/pull/7064 to update Helix instance `Server_fw-1.service.consul_8099` to point to `"hostname":"pinotserver--a073de1ef0.awsinstance.io", "port":"8099"`, PrestoDB/Trino will **NOT** query Helix instance to get that `hostname:pinotserver--a073de1ef0.awsinstance.io:8099`, let alone connect to the updated hostname:port.
We need to update PrestoDB/Trino connector code to properly query Pinot controller to resolve the host name and then later connect to the resolved host.
A bit extra note after failed attempt on "quick fix" Trino connector:
Trino queries routing table for a table, and then for each segment, it gets ServerName for that segment, and then RegEx to parse out the hostname:port to connect directly.
cc @xiangfu0 @jadami10
--
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.
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
[GitHub] [pinot] xiangfu0 commented on issue #7837: PrestoDB/Trino connector cannot connect to Pinot after Pinot cluster updates its instance hostname
Posted by GitBox <gi...@apache.org>.
xiangfu0 commented on issue #7837:
URL: https://github.com/apache/pinot/issues/7837#issuecomment-982141908
cc @elonazoulay
--
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.
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org