A node includes storage that stores a portion of high accessibility data corresponding to a shard that is divided into revisions. The portion of the high accessibility data is managed based on an activity state model including a writing state, a resolving state, a metadata update state, and a reading state. The node further includes a repository manager that obtains a cross-shard read request for the high accessibility data; makes a determination that the portion of the high accessibility data is not in the reading state; in response to the determination, adds the cross-shard read request to a delayed action queue at the revision of a last delayed action in the delayed action queue; and after processing the last delayed action in the delayed action queue and while in the resolving state: converts the cross-shard read request to a read request; and processes the read request.

NUMA-aware reader-writer locks may leverage lock cohorting techniques that introduce a synthetic level into the lock hierarchy (e.g., one whose nodes do not correspond to the system topology). The synthetic level may include a global reader lock and a global writer lock. A writer thread may acquire a node-level writer lock, then the global writer lock, and then the top-level lock, after which it may access a critical section protected by the lock. The writer may release the lock (if an upper bound on consecutive writers has been met), or may pass the lock to another writer (on the same node or a different node, according to a fairness policy). A reader may acquire the global reader lock (whether or not node-level reader locks are present), and then the top-level lock. However, readers may only hold these locks long enough to increment reader counts associated with them.

A streaming data reading method based on an embedded file system, including: receiving a request for reading streaming data, when the requested streaming data exists in a disk, creating a new reading task for the request, allocating a storage space to the newly created reading task, and initializing relevant parameters; decomposing the reading task into a plurality of sub-tasks, each sub-task being responsible for reading a piece of physically continuous data, and caching same; extracting the data from the sub-task cache, packaging same according to a streaming data format, submitting the data to a caller of this reading task once one block of data is packaged, and releasing this sub-task and triggering the next sub-task after submission; and when all sub-tasks are successfully completed, reporting the normal completion of the task to the task caller, and waiting for the task caller to end the current reading task.

Described herein is a computer implemented method. The method comprises receiving, from a user device, a selected workflow message identifying a selected workflow; accessing the selected workflow from a workflow data store; evaluating, using runtime context information received from the user device, one or more secondary triggers associated with the selected workflow to determine an applicable branch of the selected triggered workflow; communicating, to the user device, branch information in respect of the applicable branch, the branch information including information in respect of one or more operations that would be performed if the selected workflow was executed.

Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

A computer-implemented method for translating file system operations to object store operations may include necessary steps to receive a plurality of file system operations for operating files in a file system; determine corresponding objects and object store operations in an object store for the files and the file system operations; determine an order of the object store operations based on time of the file system operations received in the file system; determine dependency of the object store operations, and assign the object store operations to a first queue based on the order and dependency; determine priority of the object store operations, and transfer an entry containing an object store operation with the priority from the first queue to a second queue; and execute the object store operations in parallel and asynchronously based on organization of the object store operations in the first and second queues.

The present technology pertains to a organization directory hosted by a synchronized content management system. The corporate directory can provide access to user accounts for all members of the organization to all content items in the organization directory on the respective file systems of the members' client devices. Members can reach any content item at the same path as other members relative to the organization directory root on their respective client device. In some embodiments novel access permissions are granted to maintain path consistency.

An aspect of the invention relates to a method for a plurality of clients to access a file in a distributed file system, the file being replicated on at least one other server, the method comprising the steps of: Receiving, by an access management device, a request to access the part of the file sent by a first client from the plurality of clients, Selecting a first server based on at least one parameter, Authorization the first client to access the file stored by the first server Receiving, following authorization, a request to access the same file sent by a second client, the second client being different from the first client, Selecting a second server based on the parameter, the second server being different from the first server, Authorizing the second client to access the file stored by the second server.

Systems, apparatus, and methods are disclosed for performing scalable operations in a file system. Metadata entries in a namespace or directory tree are sharded across multiple file metadata servers. An augmented enumeration operation, such as listing a directory, is parallelized across the multiple file metadata servers, transparently to clients. Exemplary augmentation features can include filtering and sorting. Augmentation features can be executed concurrently with enumeration, prior to enumeration, after enumeration, or as a combination of these, and can utilize pre-built index structures or holding structures for intermediate results. Augmented enumeration operations can also include no-output operations such as changing file attributes or deleting a file, and cumulative operations such as counting total disk space usage. The parallelization is compatible with tree-level parallelization and storage-level parallelization. Disclosed technologies can be applied to other fields requiring scalable enumeration, such as database and network applications.

Systems for web-based collaboration systems. Two or more users can operate concurrently on objects stored in a cloud-based environment that hosts shared objects. Concurrent editing is facilitated by components in the cloud-based environment that serve to grant a first user, a first permission to modify a first instance of an object to be edited with a first editing tool, then grant to a second user, a second permission to modify a second instance of the same object to be edited with a second editing tool instance. The occurrence of a modification event that presents a conflict is detected, and steps are taken for determining a range of possible remediation tool options that can be used to address the modification conflict. Remediation tool options include remediation tool options that are natively supported within the editing tools. A set of applicable remediation tool options are presented in a user interface.