9

I am getting the following messages running a task in spring cloud data flow.

DEBUG 13167 --- [spring_batch146] com.zaxxer.hikari.pool.HikariPool        : HikariPool-2 - Add connection elided, waiting 1, queue 2

I can't find any information on it.

Sam Donato
  • 471
  • 6
  • 12

2 Answers2

11

The log message indicates that your application experienced a sudden burst of traffic and database connection requests triggered asynchronously were "merged".

You can find additional information relating to this feature in the Welcome to the Jungle document.

Johno Crawford
  • 478
  • 1
  • 6
  • 16
  • 2
    "In point of fact, as soon as the pool hit zero available connections, right around 800μs into the run, HikariCP began requesting connections to be added to the pool asynchronously. If the metrics had continued to be collected past the end of the spike -- out beyond 150ms -- you would observe that an additional connection is indeed added to the pool. But only one, because HikariCP employs elision logic; at that point HikariCP would also realize that there is actually no more pending demand, and the remaining connection acquisitions would be elided." – Sam Donato Oct 13 '20 at 14:09
  • 2
    I have not got your answer. I am facing the same issue. Will you elaborate your answer a more please? – Mukit09 Jan 12 '21 at 06:30
0

I have the same case, opening many at once in parallel threads. And in the cloud environment, timeout failures are occurring.

Anyone with any help?

"Add connection elided, waiting 17, queue 18"