RACE CONDITION HANDLING IN A SYSTEM WHICH INCREMENTALLY UPDATES CLIENTS WITH EVENTS THAT OCCURRED IN A CLOUD-BASED COLLABORATION PLATFORM

• US 20140188798A1
• Filed: 01/02/2014
• Published: 07/03/2014
• Est. Priority Date: 01/02/2013
• Status: Active Grant

• Current Assignee: Box Incorporated
• Original Assignee: Box Incorporated
• Inventors: Mackenzie, David, Spielberg, Miles
• Granted Patent: US 9,396,245 B2
• Time in Patent Office: Days
• US Class Current: 707/625
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

Techniques are disclosed for race condition handling in a system which incrementally updates clients with what occurred in a cloud-enabled platform. In one embodiment, a method comprises, in response to an event received at a synchronization client which indicates a modification to an item, comparing a sequence identifier of the item in the event with a current sequence identifier of the item. The sequence identifier of the item can be numeric and can monotonically increase as a state of the item changes. The method further comprises, if the sequence identifier in the event is larger than the current sequence identifier of the item, determining a difference between the item'"'"'s state as represented in the event and a current state of the item; and, based on the difference, generating at least one synchronization step to update the current state of the item to the item'"'"'s state as represented in the event.

Claims

1. A method for resolving race conditions when updating remote clients with what occurred in a cloud-based platform, the method comprising:

in response to an event received which indicates a modification to an item, comparing a sequence identifier of the item in the event with a current sequence identifier of the item, wherein the sequence identifier of the item is numeric and monotonically increases as a state of the item changes;

if the sequence identifier in the event is larger than the current sequence identifier of the item, determining a difference between a state of the item as represented in the event and a current state of the item; and

based on the difference, generating at least one synchronization step to update the current state of the item to the item'"'"'s state as represented in the event.

2. The method of claim 1, further comprising:

if the sequence identifier in the event is not larger than the current sequence identifier of the item, discarding the event.

3. The method of claim 1, further comprising:

if the difference does not exist, updating the current sequence identifier of the item to the sequence identifier of the item in the event.

4. The method of claim 1, further comprising:

if the modification is deletion and if the item does not exist, generating a creation event for the item with a mark which indicates the item as deleted.

5. The method of claim 4, wherein the creation event triggers no file system operation but allows persisting of the sequence identifier of the item at a moment when it is deleted.

6. The method of claim 1, further comprising:

if the item is a folder and the modification results in the folder entering or leaving a synchronization scope, performing a scan of a tree structure of synchronized folders.

7. The method of claim 6, wherein the scan includes information regarding all items deleted within a select time period of the scan.

8. The method of claim 6, wherein the scan includes information regarding all unsynchronized folders which are located inside a synchronized folder.

9. The method of claim 6, further comprising:

identifying a timestamp of the scan; and

discarding all events which occurred before the scan.

10. The method of claim 6, further comprising:

generating a synchronization event for a lowest partially synchronized folder in a path when a last fully synchronized folder is moved out from the path to a new path.

11. The method of claim 6, further comprising:

if there exists nested collaborations and if the modification results in removal of a top-level collaboration, initiating scans on both a former top-level collaborated folder and a current top-level collaborated folder.

12. The method of claim 6, further comprising:

detecting duplicate folder move, copy, synchronization, or unsynchronization events; and

initiating scans only on a first event received.

13. The method of claim 12, wherein the detecting is based on an event identifier other than the sequence identifier.

14. The method of claim 6, wherein the modification is a folder move, wherein the scan is not performed for moves between folders which are already synchronized, and wherein the folder move is logged recursively.

15. The method of claim 6, wherein the scan is not performed for unsynchronization events, and wherein an order in which synchronization and unsynchronization events are executed on the tree is preserved.

16. The method of claim 6, wherein the scan is not performed for echoback move events.

17. The method of claim 1, wherein the item is a file or a folder.

18. The method of claim 1, wherein the state of the item changes when a name, a parent folder, or a checksum of the item changes.

19. The method of claim 1, wherein the platform is a collaboration environment shared among a user and collaborators of the user.

30. The system of claim 6, wherein the processor is further caused to:

if there exists nested collaborations and if the modification results in removal of a top-level collaboration, initiate scans on both a former top-level collaborated folder and a current top-level collaborated folder.

31. The system of claim 6, wherein the processor is further caused to:

detect duplicate folder move, copy, synchronization, or unsynchronization events; and

initiate scans only on a first event received.

32. The system of claim 12, wherein the detecting is based on an event identifier other than the sequence identifier.

33. The system of claim 6, wherein the modification is a folder move, wherein the scan is not performed for moves between folders which are already synchronized, and wherein the folder move is logged recursively.

34. The system of claim 6, wherein the scan is not performed for unsynchronization events, and wherein an order in which synchronization and unsynchronization events are executed on the tree is preserved.

35. The system of claim 6, wherein the scan is not performed for echoback move events.

36. The system of claim 1, wherein the item is a file or a folder.

37. The system of claim 1, wherein the state of the item changes when a name, a parent folder, or a checksum of the item changes.

38. The system of claim 1, wherein the platform is a collaboration environment shared among a user and collaborators of the user.

20. A system for resolving race conditions when incrementally updating remote clients with what occurred in a cloud-based platform, the system comprising:

a processor;

a memory having stored thereon instructions which, when executed by the processor, cause the processor to;

in response to an event received which indicates a modification to an item, compare a sequence identifier of the item in the event with a current sequence identifier of the item, wherein the sequence identifier of the item is numeric and monotonically increases as a state of the item changes;

if the sequence identifier in the event is larger than the current sequence identifier of the item, determine a difference between a state of the item as represented in the event and a current state of the item; and

based on the difference, generate at least one synchronization step to update the current state of the item to the item'"'"'s state as represented in the event.

21. The system of claim 20, wherein the processor is further caused to:

if the sequence identifier in the event is not larger than the current sequence identifier of the item, discard the event.

22. The system of claim 20, wherein the processor is further caused to:

if the difference does not exist, update the current sequence identifier of the item to the sequence identifier of the item in the event.

23. The system of claim 20, wherein the processor is further caused to:

if the modification is deletion and if the item does not exist, generate a creation event for the item with a mark which indicates the item as deleted.

24. The system of claim 23, wherein the creation event triggers no file system operation but allows persisting of the sequence identifier of the item at a moment when it is deleted.

25. The system of claim 20, wherein the processor is further caused to:

if the item is a folder and the modification results in the folder entering or leaving a synchronization scope, perform a scan of a tree structure of synchronized folders.

26. The system of claim 25, wherein the scan includes information regarding all items deleted within a select time period of the scan.

27. The system of claim 25, wherein the scan includes information regarding all unsynchronized folders which are located inside a synchronized folder.

28. The system of claim 25, wherein the processor is further caused to:

identify a timestamp of the scan; and

discard all events which occurred before the scan.

29. The system of claim 25, wherein the processor is further caused to:

generate a synchronization event for a lowest partially synchronized folder in a path when a last fully synchronized folder is moved out from the path to a new path.

39. A system, comprising:

means for, in response to an event received which indicates a modification to an item, comparing a sequence identifier of the item in the event with a current sequence identifier of the item, wherein the sequence identifier of the item is numeric and monotonically increases as a state of the item changes;

means for, if the sequence identifier in the event is larger than the current sequence identifier of the item, determining a difference between a state of the item as represented in the event and a current state of the item; and

means for, based on the difference, generating at least one synchronization step to update the current state of the item to the item'"'"'s state as represented in the event.