cisaacson commented on issue #47083: URL: https://github.com/apache/arrow/issues/47083#issuecomment-3100214314
Further details on what we want to do. We now would like to use `envoyproxy` to do the load balancing. We may be able to add a custom header to the message using `FlightSqlServiceClient.set_header` so that `envoy` will recognize that header and use sticky routing based on this. We would call `set_header` right before `FlightSqlServiceClient.execute(sql...)`. Then we can have `envoy` use that header to hash the value in the header to ensure it goes to the same server instance. Related to this, the example `auth` logic will not work with a load balancer, as the authentication check for each call will not work unless the same server is called. I probably need to change this logic so that the authentication check will work with all of our server instances (using JWT or another mechanism). Any issues with this approach? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
