Help needed: Stuck with "QUEUED": <maxConcurrent>+<highWater>

[aletorrado]

Hi! I have a pretty simple configuration for high traffic websites:

const limiter = new Bottleneck({
	maxConcurrent: 2,
	highWater: 32,
})

Also, every job added is made withOptions, like this:

.withOptions({
	priority: Math.min(Math.max(0, Math.floor(days)), 9),
	expiration: 15000,
})

For some reason, after a few days of high intensity use, the queue is dropping every job with the message This job has been dropped by Bottleneck, and this counts:

{
"RECEIVED": 0,
"QUEUED": 34,
"RUNNING": 0,
"EXECUTING": 0
}

I don't know why I never have any job RUNNING or EXECUTING, but all QUEUED. Because of this, the whole system is getting stuck every few days, requiring a restart.

Any idea why this is happening? Thanks!

[BenPearo]

I'm also dealing with this :( did you ever figure it out?