Faktory crashing on startup. about faktory HOT 7 CLOSED

Somehow you got a job into Faktory which has no retry attribute at all. Both PUSH and PUSHB add retry if it's not there so I have no idea how this could happen.

from faktory.

Is there a way we can clear the job out?

from faktory.

Yes. If you start Redis by pointing it to the datafile, you can fire up redis-cli. One of the entries in the working zset is the bad job. You'll want to ZREM the entry which does not have a retry attribute.

redis-server faktory-redis.conf --path /path/to/faktory/db

Here's the faktory-redis.conf:

Make sure you remove all entries without retry.

from faktory.

Not seeing any with no retry, but we have a few with a retry of -1. Would a retry of -1 cause this?

from faktory.

nm, there is one with null "retry":null

from faktory.

The job with the null retry is created is the result of on on_success batch. However, it runs every 20 minutes since Monday of last week, and has succeeded quite a few times in the past week without this problem occurring.

from faktory.

Yes, that's a bug that has been fixed but not released. I will release 1.6.2 this week. In the meantime, try to explicitly set "retry" if possible in your client code where you define the callback.

from faktory.