When using HikariCP or DBCP2 connection pool with Dremio jdbc, the error log is printed as : ‘[dremioHikariCP connection adder-EventThread] ConnectionState - Authentication failed’
The jdbc driver is : 4.1.2-201912280006010755-014eceed-mapr. The hikaricp versio is 2.6.3. Also tried apache dbcp2 with version 2.2.1 but same issue.
Java code to initialize the db connection pool:
HikariConfig config = new HikariConfig();
config.setJdbcUrl(propstoreProperties.getDremioUrl());
config.setUsername(propstoreProperties.getDremioUsername());
config.setPassword(propstoreProperties.getDremioPassword());
config.setDriverClassName(“com.dremio.jdbc.Driver”);
config.setMaximumPoolSize(10);
config.setMaxLifetime(1800000);
config.setPoolName(“dremioHikariCP”);
config.setConnectionTimeout(30000);
config.setConnectionTestQuery(“SELECT 1 FROM INFORMATION_SCHEMA.CATALOGS”);
config.setValidationTimeout(30000);
config.setRegisterMbeans(false);
HikariDataSource dataSource = new HikariDataSource(config);
Can any one please help advise on the exception of ‘ConnectionState - Authentication failed’ when using the db connection pool with Dremio? Thanks!
I’m assuming you have no additional stack trace from the Authentication failure (usually the reasons are kept intentionally vague). Or do you have more info on that?
Apologies if this is an obvious question with and obvious answer, but did you double check the credentials?
What kind of user authentication are you using with Dremio?
The authentication type is LDAP. In the connection pool configuration, it’s using the service account. This account is available to log on the dremio portal and set up the jdbc connection for dremio query by jdbc zookeeper.url.
Here is the log when turning log level to trace for hikaricp and com.dremio:(init 10 connections in the pool) without any other stack trace. Please check.
Actually the connection pool looks like perform properly but the ‘Authentication failed’ error log is annoying and confusing. It isn’t sown from local windows os. But on Linux server it is always showing these error logs repeatly.
PS this error is also shown if the connection pool changes to apache DBCP2.