Skip to content
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

Need stress tests for file locking / concurrency #22

Closed
dotsdl opened this issue May 12, 2015 · 1 comment
Closed

Need stress tests for file locking / concurrency #22

dotsdl opened this issue May 12, 2015 · 1 comment
Milestone

Comments

@dotsdl
Copy link
Member

dotsdl commented May 12, 2015

Despite the advantages of structuring Containers with their stored data at the filesystem level instead of shoving them into a single database, the major disadvantage is that we have to be careful that file locks are working to ensure against concurrency corruption. We need stress tests of the file locking mechanisms for:

  • ContainerFile and its child classes
  • DataFile variants

We also need to test that changes in filesystem elements that occur through Container properties (e.g. #19) are also handled gracefully, though this will almost certainly require the underlying ContainerFile object to use the Foxhound to fetch its new path.

@dotsdl dotsdl changed the title Need stress tests for file locking / concurrency. Need stress tests for file locking / concurrency May 12, 2015
@dotsdl dotsdl added this to the 0.5.0 milestone May 12, 2015
@dotsdl dotsdl modified the milestones: 0.5.0, 0.5.1 Jun 22, 2015
@dotsdl
Copy link
Member Author

dotsdl commented Jul 21, 2015

Moved to datreant: datreant/datreant#6

@dotsdl dotsdl closed this as completed Jul 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant