Skip to main content
NetApp Stage KB

Global File Cache: Do Cores co-ordinate file locking between them? (GFC)

Views:
Visibility:
Public
Votes:
0
Category:
global-file-cache
Specialty:
CLOUD
Last Updated:

Applies to

  • Global File Cache (GFC) Core
  • Global File Cache (GFC) Edge

Answer

Question: If there are 2 cores pointing at the same data shares and a number of edges on each.  What prevents two users connecting from  different cores from conflicting on access to a file?

Answer: There will be no conflict because GFC locks happen at the authoritative source – not on the core. The locks will be under the Talon service account and can be seen looking at sessions on the backend file server.

For example:

Core1 and Core2 both connect to BackendA. Assuming we’re taking about MS Word which no collaboration is allowed.

User1 (Edge1) connects to Core 1 – opens file1.doc – file is locked on BackendA for User1

User2 (edge2) connects to Core2 – attempts to open same file1.doc on BackendA. Since this file has already been locked by User1, User2 will get a message saying the file is already been locked for editing.

Additional Information

additionalInformation_text

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
280d554f-777d-429d-a90d-09cd4f175300