-
Notifications
You must be signed in to change notification settings - Fork 32
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
Sometimes Server objects locks on is_measuring=True #14
Comments
You're right, it happened to me too... Or maybe add a button somewhere to unlock 'is_measuring' on all servers. |
Maybe use cache to limit rate? But it still won't help if sensor never exits... |
The mechanism here should ideally be a 'queue', pushing 'sensor jobs' in it. Pros : Cons : Queue should be able to process 1 to n jobs in parallel (should be a configuration variable). |
I think celery and pythonrq are overkill. I think it won't complicate code of skwissh because celery makes executing tasks simplier, but it would really complicate application stack needed to run skwissh :) |
After some thinking I'd say it would be nice to have clery or pythonrq as optional tasks backends. It will require some new managment commads and code refactorization because now skwissh is relying on how kronos collects and installs tasks. |
This makes skwissh stop collecting data for this server. Additionally there is no way to fix this except using django shell.
I suppose that when cron job is killed or exits unexpectedly nothing more can change
is_measuring
field back toFalse
. Maybe using timestamp here would be better - it will ensure that even if cron job is killed server will (in some point of time) return to it's prevoius state.The text was updated successfully, but these errors were encountered: