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

Avoid using storage account tables to keep track of copying process #178

Closed
cppforlife opened this issue Jul 20, 2016 · 1 comment
Closed

Comments

@cppforlife
Copy link
Contributor

Currently we use storage table to keep track of copying operation. In theory there is still a race between query and insert, but probably doesnt happen often. Is it possible to query Azure API to see if any copies are in progress? Alternatively we can use local file system to "lock" copying operation.

Goal is to not have tables to simplify setup and allow default storage account to be on premium storage.

@AbelHu
Copy link
Contributor

AbelHu commented Jul 21, 2016

The race between query and insert is handled in CPI code

Later we can consider to remove the table dependency.

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

2 participants