Techniques of data flow control are disclosed herein. One example technique includes upon receiving a notification indicating a change to a content item in a source shard, parsing the content item to extract data representing attributes of the content item and identifying a partition of the system-wide index based on the extracted data representing the attributes of the content item. The example technique can also include transmitting, to a token issuer, a request for a token that represents a permission to write to the identified partition of the system-wide index and upon receiving a token issued by the token issuer in response to the transmitted request, transmitting the extracted data representing the attributes of the content item along with the received token to write the extracted data in the partition of the system-wide index.

Examples described herein are generally directed towards file share access, and more specifically towards a mechanism to connect file shares at the protocol level in a distributed file server environment. In operation, a first FSVM hosting a first file share may receive a request by a client to access a location in a name space. The first FSVM may determine the location is at a second file share linked to the first file share. The first FSVM may provide access to the second file share to the client. In some examples, the first file share and the second file share may be linked at the directory level.

The invention concerns a storage method for storing, on data servers (3, 4), data file (5, 61 to 64) slices (51 to 58) from the execution of a plurality of processes (65 to 68) of one or more applications (83, 85), comprising: distributing the stored data file (5, 61 to 64) slices (51 to 58) over different data servers (3, 4), characterized in that: this distribution is carried out in such a way that the data file (5, 61 to 64) slices (51 to 58) likely to be subsequently accessed simultaneously by different application (83, 85) processes (65 to 68) are stored on different data servers (3, 4) so as to reduce the subsequent access, to each of all or part of these data servers (3, 4) by too many application (83, 85) processes (65 to 68) simultaneously, and in that: the determination of the data file (5, 61 to 64) slices (51 to 58) likely to be subsequently accessed simultaneously by different application (83, 85) processes (65 to 68) has been carried out, during a prior phase of executing these application (83, 85) processes (65 to 68), by observing the behavior of these application (83, 85) processes (65 to 68) in order to access these stored data file (5, 61 to 64) slices (51 to 58) over time.

A file system manager implemented at a provider network identifies a storage device of a first group of storage devices of a provider network as an initial location of a file system object. Based on an access metric associated with the object, the file system manager initiates a transfer of contents of the object to a second storage device of a different storage device group, without receiving a client request specifying the transfer. In response to an access request received via a file system programmatic interface, contents of the object are provided from the second storage device. Based on a second access metric, the object is transferred back to the first group of storage devices.

Example methods and systems are directed to a multitenant application server using a union file system. Each tenant has one or more users and a tenant layer in the union file system. Each user has a user layer in the union file system. The union file system provides a logical file system to each user based on the user layer, the tenant layer, and a base layer comprising a set of application layers. A first user shares an application template file with other users of the same tenant by moving the file from the first user's user layer to the tenant layer. After the file is moved, all users of the tenant have access to the application defined by the application template file. The moving of the file is achieved by modifying metadata for the file.

In some implementations, a subscriber to an online content management system can share content items that are external to the subscriber's content library. A computing device can include managed content items associated with the subscriber's content library. The computing device can include unmanaged content items that are stored externally to the subscriber's content library. The subscriber can provide input associated with an unmanaged content item to generate a link (e.g., URL, file path, location reference, etc.) for the unmanaged content item. When generating the link, the unmanaged content item can be uploaded to the online content management system and stored separately from the subscriber's content library. The generated link can be shared with recipient user (e.g., subscriber or non-subscriber). The generated link can be used by the recipient to access the unmanaged content item uploaded to and stored by the online content management system.

The disclosed technology relates to a system configured to detect a modification to a node in a tree data structure. The node is associated with a content item managed by a content management service as well as a filename. The system may append the filename and a separator to a filename array, determine a location of the filename in the filename array, and store the location of the filename in the node.

A block of data intended for a set of receiving computer systems comprising a first system and a second system is divided into a set of equal-size portions. A first portion of the set of portions is transmitted from a first file server storing the block of data to the first system. The first portion is relayed from the first file server to a second file server concurrently with the transmitting. The first portion of the set of portions is transmitted from the second file server to the second system.

The method of some embodiments provides values from a server over a network connection. The method, for each of multiple values (i) creates a file including the value on a random access memory filing system (RAMFS), (ii) receives a request to receive the value, and (iii) sends the file via a sendfile system call.

Disclosed are mechanisms for sharing content through content consumption systems. A sharing module publishes content in a share and metadata associated therewith to a content consumption system external to a managed repository. The share represents a folder or directory in the managed repository. The publication can be made through application programming interface (API) calls handled by a first sharing module API, a repository API, a second sharing module API, and a content consumption system API. These APIs together provide a one-to-one mapping of communications protocols used by the managed repository and the external system. The share in the managed repository and the share published to the content consumption system are synced and any conflict between the two is detected and resolved. The shared content can be repatriated back to the managed repository and the shared version deleted from the content consumption system.