NelsonJeppesen commented on issue #5183: URL: https://github.com/apache/druid/issues/5183#issuecomment-737378697
> @himanshug I still get this error [#5183 (comment)](https://github.com/apache/druid/issues/5183#issuecomment-353203960). Not facing this issue when only one broker is up and running. But when we increase the replica count to 2, queries from our BI tool(looker, connects using jdbc) fail with **Connection already open** error. Ran into this issue as well @himanshug >"Druid's JDBC server does not share connection state between Brokers. This means that if you're using JDBC and have multiple Druid Brokers, you should either connect to a specific Broker, or use a load balancer with sticky sessions enabled. The Druid Router process provides connection stickiness when balancing JDBC requests, and can be used to achieve the necessary stickiness even with a normal non-sticky load balancer." I tried sticky, didnt help but sending looker to the router process did help ---------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
