Patent classifications
H04L67/1095
Asynchronous replication of linked parent and child records across data storage regions
Disclosed in some examples are methods, systems, and machine readable mediums for efficient asynchronous replication of hierarchical records across data storage locations. Methods and systems are also described for efficiently updating replicated records. Disclosed also in some examples are improved storage, replication, and distribution of data related to network-based meetings (e.g., media) in hierarchical records. Data for one or more components of the meeting (e.g., media) may be stored in a child record (called a component record). The network-based meeting may be described by a parent record with links to, and in some examples descriptions of, the meeting component records (the child records).
Maintaining failure independence for storage of a set of encoded data slices
A method includes detecting a storage error associated with a first memory device of a storage unit of a set of storage units, where data is error encoded into a set of encoded data slices and stored in a plurality of memory devices of the set of storage units, and where the plurality of memory devices includes the first memory device. The method further includes determining attributes associated with the first memory device and determining attributes of other memory devices of the plurality of memory devices. The method further includes selecting a memory device from the other memory devices based on the attributes of the memory device comparing favorably to the attributes associated with the first memory device. The method further includes rebuilding an encoded data slice associated with the storage error and storing the rebuilt encoded data slice in the selected memory device.
System and method for highly available database service
A highly available database system includes a first instance of a database server on a first cluster of a virtual computing system, a second instance of the database server on a second cluster of the virtual computing system, a first instance of an administration database on the first cluster, and a second instance of the administration database on the second cluster. The first instance of the database server and the second instance of the database server form a highly available database server, the first instance of the administration database and the second instance of the administration database form a highly available administration database, and the first instance of the database server, the second instance of the database server, the first instance of the administration database, and the second instance of the administration database are configured to manage at least one customer database.
PREVENTING DATA OVERFLOW IN EDGE COMPUTING SYSTEMS
Data overflows can be prevented in edge computing systems. For example, an edge computing system (ECS) can include a memory buffer for storing incoming data from client devices. The ECS can also include a local storage device. The ECS can determine that an amount of available storage space in the local storage device is less than a predefined threshold amount. Based on determining that the amount of available storage space is less than the predefined threshold amount, the ECS can prevent the incoming data from being retrieved from the memory buffer. And based on determining that the amount of available storage space is greater than or equal to the predefined threshold amount, the ECS can retrieve the incoming data from the memory buffer and store the incoming data in the local storage device. This may prevent data overflows associated with the local storage device.
Distributed database with replica placement control
A distributed database management system comprises database nodes located in a plurality of availability zones. The system receives a request to store a table, and determines to store a number of replicas of the table in one or more availability zones. The system obtains information indicating that one of the availability zones has been designated as preferred. The system identifies a set of database nodes in the preferred availability zone, where the number of database nodes in the subset is sufficient to determine quorum among the replicas. The replicas are stored on the identified set of database nodes.
Updating a remote tree for a client synchronization service
The disclosed technology relates to a system configured to receive operations data from a content management system, wherein the operations data comprises a log of operations, execute the log of operations, and update, based on execution of the log of operations, a remote tree representing a server state for content items stored on the content management system.
Updating a remote tree for a client synchronization service
The disclosed technology relates to a system configured to receive operations data from a content management system, wherein the operations data comprises a log of operations, execute the log of operations, and update, based on execution of the log of operations, a remote tree representing a server state for content items stored on the content management system.
In-memory database-managed container volume replication
In an example embodiment, a solution is used to provide container volume replication via a container storage replication log and volume buffer synchronization, which is built on top of a container cloud platform whose container metadata and replication runtime configuration are all managed by a storage manager (a service orchestrated by its job scheduler and service orchestrator). This container volume replication ensures the data security for a long-running service in the container. In the case of any disaster, the in-memory database and application data inside of the container can be recovered via volume replication. This provides container volume replication for long-running containerized applications whose states keep changing.
Stacked computer network devices having multiple master nodes
An electronic device is described. The electronic device includes a stack of computer network devices, such as a stack of switches and/or routers. This stack of computer network devices includes data planes and ports for directing packets or frames in a wireless network based at least in part on destinations of the packets or frames. Moreover, the electronic device may include multiple controllers (such as processors) that operate as master nodes and that perform network functions for the stack of computer network devices using a database. This database may include a common database that is accessible by the multiple controllers or multiple instances of the database in the multiple controllers, where the multiple instances of the database are synchronized.
Stacked computer network devices having multiple master nodes
An electronic device is described. The electronic device includes a stack of computer network devices, such as a stack of switches and/or routers. This stack of computer network devices includes data planes and ports for directing packets or frames in a wireless network based at least in part on destinations of the packets or frames. Moreover, the electronic device may include multiple controllers (such as processors) that operate as master nodes and that perform network functions for the stack of computer network devices using a database. This database may include a common database that is accessible by the multiple controllers or multiple instances of the database in the multiple controllers, where the multiple instances of the database are synchronized.