Job not restarting after restart of a worker (in a single-worker scenatio) about rqueue HOT 6 CLOSED

Thanks for reporting the bug, what did you mean by "Cut the worker" and "Restart the worker"? Worker would be started automatically unless I'm missing something. If you shutdown your application during execution than the said message would come back to queue once visibility timeout has expired.

from rqueue.

https://javadoc.io/doc/com.github.sonus21/rqueue-core/latest/com/github/sonus21/rqueue/annotation/RqueueListener.html

from rqueue.

Hello Sonus,
I have already played a little with the visibility timeout, but it seems to not work on my side (well, with a single-worker scenario anyway).

In my case, I am using Kubernetes, which restarts my pods containing my workers on new versions (its the intended workflow) and, when rebooted, event after the visibility timeout is expired, the job is never re-added to the queue, which means that the jobs seems to be completely lost in my case

Regards

from rqueue.

That's strange, if you have dashboard access please check dashboard, it is available at host/rqueue, it does not require any authentication you're supposed to protect dashboard from evils.

If you don't have access to dashboard, please run these commands to see if entries exist in Redis.

LRANGE __rq::queue::{<queueName>} 0 -1
ZRANGE __rq::d-queue::{<queueName>} 0 -1
ZRANGE __rq::p-queue::{<queueName>} 0 -1

For example if your queue name is test-queue then you need to run following set of commands

LRANGE __rq::queue::{test-queue} 0 -1
ZRANGE __rq::d-queue::{test-queue} 0 -1
ZRANGE __rq::p-queue::{test-queue} 0 -1

from rqueue.

This test verifies this feature

It only verifies for continuous polling not shutdown and boostrap

from rqueue.

Hi Alex
This does not seem to be a Rqueue bug, closing this. Please feel free to open this bug if you have more details or you can provide a reproducible code snippet.

from rqueue.