了解/删除Azure File Service上的文件锁 [英] Understanding / removing a file lock on Azure File Service

问题描述

我正在开发一个用于将常用文件共享到blob存储的应用程序(即，工作角色A将更新这些文件，工作角色B将读取这些文件).

I'm working on an application that used to share common files to blob storage (i.e. Worker Role A would update those files and Worker Role B would read those).

由于此应用程序并不重要，因此即使它仍然是预览版，我们最近也已将其转换为Azure File Service共享.

As this application is non critical we recently transitioned to Azure File Service share, even though it's still a preview.

直到最近，即使在尝试删除所有可能在这些文件上具有句柄的实例之后，也不会在共享上释放文件锁，它的工作情况还不错.尝试删除重命名文件时始终显示相同的消息:

It was working just fine until recently when a file lock wouldn't be released on the share, even after trying to delete all the instances that could possibly have a handle on those files. Always the same message when trying to remove of rename a file:

我记得使用SMB时遇到过这类问题，但是解决方案是登录到共享服务器并删除锁...这显然是Azure文件服务无法做到的.

I remember having those kind of issues when using SMB, but then the solution would be to log to the share server and remove the locks... which we obviously can't do with azure file service.

您对如何释放这种锁有想法吗?

Would you have an idea on how to release such locks?

推荐答案

感谢Charles提出了这一点.我们看了您的示例，在某些罕见情况下，我们似乎过于保守地关闭了句柄.

Thanks Charles for bringing this up. We looked at your example, and looks like we are being too conservative in closing the handles in certain rare circumstances.

我们已经进行了改进，可以检测到这种情况，并将很快推出.

We have made an improvement to detect this case and will be rolling this out soon.

目前，我们已经减轻了压力，因此您的共享应该删除了锁.如果您再次遇到此问题，请告诉我们.

For now we have mitigated on our end, so your share should have the locks deleted. Please let us know if you hit this issue again.

这篇关于了解/删除Azure File Service上的文件锁的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！