You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use play-hikaricp plugin to pool database connection with Vertica. Vertica supports automatic switchover to one of the nodes in the cluster if the primary node goes down through the jdbc property BackupServerNode. However, play-hikaricp plugin doesn't seem to honour the custom connection property and hence we are not able to fallback to a different node in the cluster if the node mentioned in db.default.url property goes down. Is there a way to make this property work with HikariCP? We have verified that if we actually create a java.util.Properties and use that to create a JDBC Connection using HikariCP, it works.
We use play-hikaricp plugin to pool database connection with Vertica. Vertica supports automatic switchover to one of the nodes in the cluster if the primary node goes down through the jdbc property BackupServerNode. However, play-hikaricp plugin doesn't seem to honour the custom connection property and hence we are not able to fallback to a different node in the cluster if the node mentioned in db.default.url property goes down. Is there a way to make this property work with HikariCP? We have verified that if we actually create a java.util.Properties and use that to create a JDBC Connection using HikariCP, it works.
db.default.url="jdbc://postgresql://IP-Address:Port/DBName"
db.default.BackupServerNode="node2-domain,node3-domain"
The text was updated successfully, but these errors were encountered: