Hi, I truly appreciated the support we are getting from the community.
As of now we don't have a re-producer, The above issue basically comes once in a while. The server is up and running, *Note*: The ignite cluster has been installed in azure kubernetes cluster as statefulset pods. We have other application pods they frequently talk to ignite. While analyzing we understood that the application pod which creating problem, is running with ignite 2.6.0 where as the Ignite server is 2.8.1 for us We followed below steps and deployed in production 1- Changed version of Hikari to 3.4.5 2- Ignite core changed to 2.8.1 3- Spring boot was auto configuring jdbc templates (with hikari), we disabled auto configuration and configured manually. We deployed the application and we are monitoring, and will publish the result. Thanks, Sanjaya On Tue, Nov 3, 2020 at 8:28 PM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > Are you sure that the Ignite cluster is in fact up? :) > > If it is, maybe your usage patterns of this pool somehow assign the > connection to two different threads, which try to do queries in parallel. > In theory, this is what connection pools are explicitly created to avoid, > but maybe there's some knob you have to turn to actually make them > thread-exclusive. > > Also, does it happen every time? How soon would it happen? > > Regards, > -- > Ilya Kasnacheev > > > пн, 2 нояб. 2020 г. в 12:31, Sanjaya <sahoo.sku...@gmail.com>: > >> Hi All, >> >> we are trying to use HIkari connection pooling with ignite JdbcThinDriver. >> we are facing issue as >> >> >> Any idea what is the supported connection pooling mechanism work with >> IgniteThinDriver >> >> >> ERROR LOG >> ================== >> >> WARN com.zaxxer.hikari.pool.ProxyConnection.157 sm-event-consumer prod >> sm-event-consumer-v1-55f4db767d-2kskt - HikariPool-1 - Connection >> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection@68f0e2a1 marked >> as >> broken because of SQLSTATE(08006), ErrorCode(0) >> >> java.sql.SQLException: Failed to communicate with Ignite cluster. >> >> at >> >> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:760) >> >> at >> >> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.executeBatch(JdbcThinStatement.java:651) >> >> at >> >> com.zaxxer.hikari.pool.ProxyStatement.executeBatch(ProxyStatement.java:128) >> >> at >> >> com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeBatch(HikariProxyPreparedStatement.java) >> >> at >> >> org.springframework.jdbc.core.JdbcTemplate.lambda$batchUpdate$2(JdbcTemplate.java:950) >> >> at >> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:617) >> >> at >> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:647) >> >> at >> >> org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:936) >> >> at >> >> org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.batchUpdate(NamedParameterJdbcTemplate.java:366) >> >> at >> >> com.ecoenergy.cortix.sm.event.cache.SMIgniteCacheManager.updateObjectStates(SMIgniteCacheManager.java:118) >> >> at >> >> com.ecoenergy.cortix.sm.event.notifcator.SMIgniteNotificator.notify(SMIgniteNotificator.java:69) >> >> at >> >> com.ecoenergy.cortix.sm.event.eventhandler.ObjectEventHandler.notify(ObjectEventHandler.java:100) >> >> at >> >> com.ecoenergy.cortix.sm.event.eventhandler.ObjectEventHandler.receiveEvents(ObjectEventHandler.java:86) >> >> at >> >> com.ecoenergy.cortix.sm.event.consumer.ObjectEventConsumer.processObjectEvents(ObjectEventConsumer.java:60) >> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
