scala - Squeryl - HikariCP - mySql - Distributing Read Traffic to Slaves -
i'm trying follow steps listed @ http://dev.mysql.com/doc/connector-j/en/connector-j-master-slave-replication-connection.html states
to enable functionality, use com.mysql.jdbc.replicationdriver class when configuring application server's connection pool
from https://github.com/brettwooldridge/hikaricp - says
hikaricp attempt resolve driver through drivermanager based solely on jdbcurl
so configuration thats needed?
db.default.url=jdbc:mysql:replication ...
squeryl has has number of db adapters; understanding these unrelated? http://squeryl.org/api/index.html#org.squeryl.adapters.mysqlinnodbadapter
sorry key word loading - i'm not sure need focus
thanks brent
squeryl offers different mysql adapters because innodb supports referential keys, while myisam not. seems your'e doing should handled @ connection pool level, don't think squeryl configuration have affect.
i've never configured hikari replicated mysql, if requires alternative jdbc driver i'd surprised if can provide jdbc url , works. i'm guessing hikari's default functionality pick plain vanilla mysql jdbc driver unless tell otherwise. luckily, hikari has quite few config options including ability set specific driverclassname
.
Comments
Post a Comment