Skip to content
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.

Issues while writing and reading from different daemons with flock #208

Open
ABaligar opened this issue Jul 29, 2019 · 0 comments
Open

Issues while writing and reading from different daemons with flock #208

ABaligar opened this issue Jul 29, 2019 · 0 comments

Comments

@ABaligar
Copy link

I understand that with tape I need to use an external lock if I am accessing object queue file from two different daemons. I use flock to lock the file before I do any of the operations (add, peek, remove). My writer daemon produces slower than the reader, so once the reader consumes everything, it reports the queue size as zero and continues to do so even when the writer writes after some mili seconds. If I create the object queue newly, it gets the size right, but object converter doesn't work properly, looks like the file is corrupted somewhat. Any solution you can suggest here?

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

No branches or pull requests

1 participant