FarhadF opened a new issue, #15638: URL: https://github.com/apache/druid/issues/15638
After Mysql (aws aurora) failover, druid is still connected to the same instace (now readonly instance) ### Affected Version 27.0.0 ### Description - Cluster size: 15 node - Configurations in use: using mysql metastore with aws aurora, the URL is the writer url of the aurora database cluster which will be switched to the current writer instance (the ip address will be updated when failover happens). - Steps to reproduce the problem: druid cluster with mysql metadatastore deployed. aurora mysql with at least 2 instances. Use the writer endpoint in druid configurations. Then fail over the cluster to the second node. - The error message or stack traces encountered. Providing more context, such as nearby log messages or even entire logs, can be helpful.  I believe there should be a catch for this exception that renews the mysql connection pool. This will allow druid to always connect to the writer instance on highly available environments. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
