You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.
Right now it's possible for two jobs of the same media to be processed at the same time, it is also possible for two instances to get the same job (unack -> broker dies -> unack on new + old). We should have a locking system that acts on both type id and job id.
This would be done in the tritonmedia/core repository, in the ampq.js file. This is used by all applications for AMQP connections.
The text was updated successfully, but these errors were encountered:
Right now it's possible for two jobs of the same media to be processed at the same time, it is also possible for two instances to get the same job (unack -> broker dies -> unack on new + old). We should have a locking system that acts on both type id and job id.
This would be done in the tritonmedia/core repository, in the
ampq.js
file. This is used by all applications for AMQP connections.The text was updated successfully, but these errors were encountered: