Leaked keys in version 5.0.10

[alisherry]

Describe the bug
Our app is currently on version 5.0.10 of the gem, and we're currently in the process of removing it. We've attempted to upgrade to the latest version, but that caused infrastructure issues during deployment so we had to revert that.

We recently noticed that in our redis, there's a very large amount of keys in the uniquejobs hash. The current size is in the hundreds of millions, taking up almost 8GB of our Redis storage space. Those keys aren't used as the actual sidekiq queues are empty, and those locks should have been released.

We've removed the uniqueness locks in that particular redis so we aren't dependant on locks anymore, but now comes in the issue of deleting them.

One solution we're exploring is to set that hash to expire in a small period of time

 Redis.current.with do |conn|
      conn.expire("uniquejobs", 5.seconds)
 end

As mentioned above, we've previously tried bumping to 6.0.21 but we saw a massive CPU spike and had to revert. Outside of upgrading the gem, is that a viable solution to remove those keys (if we're not concerned about the uniqueness from those keys)

[alisherry]

Update to this conn.unlink was the solution I ended up going with and it cleared the keys without any other errors. Closing this issue