Efficient management of client synchronization updates

Patent metadata

Field	Value
Publication number	US-11500899-B2
Application number	US-202017136849-A
Country	US
Kind code	B2
Filing date	Dec 29, 2020
Priority date	Dec 28, 2017
Publication date	Nov 15, 2022
Grant date	Nov 15, 2022

Abstract

The disclosed technology relates to a system configured to identify a first operation in a first set of operations configured to converge a server state and a file system state, wherein the first operation is not in a second set of operations generated in response to an change to at least one of the server state and the file system state. The system is further configured to cancel the first operation, identify a second operation in both the first set of operations and the second set of operations, and initiate execution of the second operation concurrently with the canceling of the first operation.

First claim

What is claimed is:

1. A computer-implemented method comprising:
monitoring a file system for modifications to the file system;
generating a plan of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device;
receiving an indication of further modifications to the file system;
generating a second plan of operations configured to converge the server state and the file system state based on the further modifications to the file system;
identifying a first task in the plan of operations that is absent from the second plan of operations;
determining that the first task has not been initiated; and
canceling the first task.

2. The computer-implemented method of claim 1 , further comprising:
identifying a second task in the second plan of operations that is not in the plan of operations;
determining that canceling of the first task has completed; and
in response to determining that canceling of the first task has completed, initiating execution of the second task.

3. The computer-implemented method of claim 1 , further comprising executing the plan of operations.

4. The computer-implemented method of claim 1 , wherein each task in the plan of operations is configured to be concurrently executable and each task in the second plan of operations is configured to be concurrently executable.

5. The computer-implemented method of claim 1 , further comprising executing the second plan of operations, wherein executing the second plan of operations comprises:
identifying a script associated with the second plan of operations, wherein the script defines multiple tasks to be performed to complete the second plan of operations; and
executing the script.

6. The computer-implemented method of claim 1 further comprising:
transmitting instructions associated with the second plan of operations to the content management system for execution on the server state.

7. The computer-implemented method of claim 1 , further comprising:
executing the second plan of operations by providing instructions associated with the second plan of operations to the client device for execution on the file system state.

8. The computer-implemented method of claim 1 , further comprising:
identifying a first difference between a sync tree and at least one of a remote tree and a local tree, wherein the sync tree represents a known synced state between the server state and the file system state, the remote tree represents the server state, and the local tree represents the file system state; and
generating, based on the first difference, the plan of operations configured to converge the server state and the file system state.

9. The computer-implemented method of claim 8 , further comprising:
identifying a second difference between the sync tree and at least one of the remote tree and the local tree after a change to at least one of the server state and the file system state; and
generating, based on the second difference, the second plan of operations configured to converge the server state and the file system state.

10. The computer-implemented method of claim 8 , further comprising:
receiving server modification data for content items stored by a content management service; and
updating, based on the server modification data, the remote tree.

11. The computer-implemented method of claim 8 , further comprising:
receiving client modification data for content items stored by the client device; and
updating, based on the client modification data, the local tree.

12. A non-transitory computer-readable medium comprising instructions, the instructions, when executed by a computing system, cause the computing system to:
monitor a file system for modifications to the file system;
generate a plan of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device;
receive an indication of further modifications to the file system;
generate a second plan of operations configured to converge the server state and the file system state based on the further modifications to the file system;
identify a first task in the plan of operations that is absent from the second plan of operations;
determine that the first task has not been initiated; and
initiate canceling the first task.

13. The non-transitory computer-readable medium of claim 12 , wherein the instructions further cause the computing system to:
identify a second task in both the plan of operations and the second plan of operations; and
initiate execution of the second task concurrently with canceling the first task.

14. The non-transitory computer-readable medium of claim 12 , wherein each task in the plan of operations is configured to be concurrently executable and each task in the second plan of operations is configured to be concurrently executable.

15. The non-transitory computer-readable medium of claim 12 further wherein the instructions further cause the computing system to:
transmit instructions associated with the second plan of operations to at least one of the content management system for execution on the server state or the client device for execution on the file system state.

16. The non-transitory computer-readable medium of claim 12 , wherein the instructions further cause the computing system to:
identify a difference between a sync tree and at least one of a remote tree and a local tree, wherein the sync tree represents a known synced state between the server state and the file system state, the remote tree represents the server state, and the local tree represents the file system state; and
generate, based on the difference, the plan of operations configured to converge the server state and the file system state.

17. A system comprising:
one or more processors; and
a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to:
monitor a file system for modifications to the file system;
generate a plan of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device;
receive an indication of further modifications to the file system;
generate a second plan of operations configured to converge the server state and the file system state based on the further modifications to the file system;
identify a first task in the plan of operations that is absent from the second plan of operations;
determine that the first task has not been initiated; and
initiate cancelling the first task.

18. The system of claim 17 , wherein the instructions further cause the one or more processors to:
identify a second task in the second plan of operations that is not in the plan of operations;
determine that canceling of the first task has completed; and
in response to determining that canceling of the first task has completed, initiate execution of the second task.

19. The system of claim 17 , wherein the instructions further cause the one or more processors to:
identify a first difference between a sync tree and at least one of a remote tree and a local tree, wherein the sync tree represents a known synced state between the server state and the file system state, the r

Assignees

• Dropbox Inc

Inventors

• Lai John
• Goldberg Isaac
• Jayakar Sujay

Classifications

• G06F16/185

  Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11) · CPC title

• H04L63/101

  Access control lists [ACL] · CPC title

• G06F2212/1052

  Security improvement · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F16/275

  Synchronous replication · CPC title