DaanHoogland commented on PR #8896: URL: https://github.com/apache/cloudstack/pull/8896#issuecomment-2047168886
> If you remove the last record (which, in my head is some kind of protection mechanism, but I might be wrong) - don't we run into risk if the following happens: > > * you start 2 usage servers at the same/similar time (systemctl start) > > * both usage servers try to run the job (while only one should be the "owner of the job" and the other one will notice this and, currently, NOT execute the duplicate job - it will never execute the duplicate job as long as there is that last record which indicates that another/first usage server is the owner of the job) > > > ? Yes, this is correct. The issue is when you stop the Usage server owning the job, it will no longer have an owner and no server will ever execute a job anymore. Therefore the owning process should remove their job on exit. In the current situation, you have to delete the record manually and the risk is the same. There is just a manual action needed that you need to be aware off. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
