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
The locking approach used in hashstore appears to support in process threading but not multi-process or multi-application locking. The portalocker library provides a cross platform solution for locking that works with multiple application instances and (when using redis), multi-system locking.
The approach of having a single lock per instance and a class variable of locked PIDs seems ok for a single instance, but would likely be problematic with multiple processes or instances. Perhaps using portalocker the PID could be used to derive the filename of the desired lock?
The text was updated successfully, but these errors were encountered:
Thank you for your suggestion, reviewing hashstore and providing feedback @datadavev! I really appreciate it and will investigate the portalocker library (and implement the suggestions in your other enhancement tickets).
The locking approach used in hashstore appears to support in process threading but not multi-process or multi-application locking. The portalocker library provides a cross platform solution for locking that works with multiple application instances and (when using redis), multi-system locking.
The approach of having a single lock per instance and a class variable of locked PIDs seems ok for a single instance, but would likely be problematic with multiple processes or instances. Perhaps using portalocker the PID could be used to derive the filename of the desired lock?
The text was updated successfully, but these errors were encountered: