I just noticed that the ql:tracked set in my productive Qless installation contained ~ 450.000 entries while there are only < 8.000 jobs this Qless installation is still aware off.
Digging into it a little is seems to me jids are only removed from the ql:tracked key when they are explicitly untracked. The jid is not removed from the ql:tracked set when the job is canceled. This leads to an ever growing ql:tracked sorted set which breaks the qless webui as soon as the tracked lua script takes longer then 5 seconds to loop through the set.
I'm still running on qless 0.9.3 but having a quick glimse at the current master of qless-core it seems to me this problem still exists.
I just noticed that the
ql:trackedset in my productive Qless installation contained ~ 450.000 entries while there are only < 8.000 jobs this Qless installation is still aware off.Digging into it a little is seems to me jids are only removed from the
ql:trackedkey when they are explicitly untracked. The jid is not removed from theql:trackedset when the job is canceled. This leads to an ever growingql:trackedsorted set which breaks the qless webui as soon as the tracked lua script takes longer then 5 seconds to loop through the set.I'm still running on qless 0.9.3 but having a quick glimse at the current master of qless-core it seems to me this problem still exists.