Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setOK thread still running even after stopping the worker #17

Open
telenskyt opened this issue Sep 21, 2014 · 0 comments
Open

setOK thread still running even after stopping the worker #17

telenskyt opened this issue Sep 21, 2014 · 0 comments

Comments

@telenskyt
Copy link

I stopped the worker (i.e. the redisWorker function) using the STOP button in Rgui. But the setOK thread is apparently still running in the background:

redisKeys("*")
[1] "jobs:2.alive.4"
redisTTL("jobs:2.alive.4")
[1] 4
redisTTL("jobs:2.alive.4")
[1] 3
redisTTL("jobs:2.alive.4")
[1] 2
redisTTL("jobs:2.alive.4")
[1] 5

Even starting a new worker (in the session where the previous worker was stopped) won't fix the situation:

redisWorker('jobs', redis_server)

Even this sequence (on the master) won't fix the situation:

removeQueue('jobs')
registerDoRedis('jobs', redis_server)

The only working "fix" is to close the whole R session (Rgui) that caused the problem.

This issue potentially might contribute (I say might as I am not sure at all) to unpredictable issues #14 and #15.

I use R 3.1.0, doRedis 1.1.1, rredis 1.6.9 and redis server 2.6.12, all on a single host Windows XP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant