Abstract:
A method begins by independently executing a first write transaction in a dispersed storage network (DSN) to a particular write verification step of a multiple step write process, wherein the first write transaction has a first transaction identifier. The method continues by independently executing a second write transaction in the DSN to the particular write verification step, wherein the second write transaction has a second transaction identifier, and wherein subject matter of the first write transaction is related to subject matter of the second write transaction. The method continues by dependently finalizing the multiple step write process for each of the first and second write transactions utilizing the first and second transaction identifiers when each of the first and second write transactions have reached the particular write verification step.
Abstract:
A communication device includes: a first communication section, a second communication section, a storage section, a determination section, and a control section. The first communication section communicates with a storage device based on predefined interface communication standards to perform data transfer. The second communication section communicates with an external device in a method other than the interface communication standards to perform data transmission. The storage section stores the selected error code that is previously defined to cause a bit error by noise. The determination section determines whether or not an error code indicated by the error information agrees with the selected error code. The control section, upon determination by the determination section that the error codes agrees with each other, gives the first communication section and the second communication section instructions for cancelling the data transfer and performing data re-transfer.
Abstract:
Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.
Abstract:
A method for byzantine fault tolerant data replication with a plurality of 2f+1 data servers and one or more clients includes storing data in at least f+1 different data servers out of the 2f+1 data servers, and storing metadata of the stored data under a metadata-identifier in a metadata-service (MDS). The stored metadata includes a unique identifier of the stored data, a fingerprint of the stored data, and a list of the at least f+1 different data servers which have stored the data.
Abstract:
A system and method of diagnosing and correcting errors in a server computer. A server computer is coupled by a communication path to a client computer. A storage device stores a diagnostic error detecting and correcting program and the server computer is programmed to implement the diagnostic error detecting and correcting program. The server computer detects several selected operating parameters during operation of the server process and determines if at least a first of the selected operating parameters are outside a pre-determined specification for the selected operating parameters. In response to the selected operating parameters being outside the pre-determined specification, the server computer notifies the client computer of an error with the server process. The server computer can also detect communication errors and attempt to restore communications by modifying communication parameter(s).
Abstract:
A fault-tolerant retry subsystem, method and computer program product are provided in order to automatically retry to deliver a message. In the context of a fault-tolerant retry subsystem, processing circuitry is provided to receive notification that delivery of a message to a subscriber has failed. The processing circuitry also defines a time interval at which delivery of the message is to be retried. The message is to be subjected to a plurality of retry attempts in an instance in which the delivery of the message to the subscriber continues to fail. The time interval is defined in a manner that depends upon which of the plurality of retry attempts is to be performed. As such, the time interval varies between at least some of the retry attempts. The processing circuitry causes the delivery of the message to be retried following expiration the time interval.
Abstract:
Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information synchronously replicated to the secondary replica at a block level, such that the primary and secondary replicas are in sync. In the event that the monitoring component is not able to communicate with one of the replicas, the monitoring component can attempt to determine whether those replicas can communicate with each other, as well as whether the replicas have the same data generation version. Depending on the state information, the monitoring component can automatically perform a recovery operation, such as to failover to the secondary replica or perform secondary replica recovery.
Abstract:
A data generation device 101 transmits communication data bound for a data receiving device 105 from a transmission unit, and a monitoring device 103 receives the communication data. The monitoring device 103 requests retransmission of the communication data to the data generation device 101, and the data generation device 101 retransmits the communication data from a retransmission unit being different from the transmission unit. The monitoring device 103 receives retransmission data retransmitted from the retransmission unit, compares the communication data with the retransmission data. If the communication data and the retransmission data are identical, the monitoring device 103 transmits the communication data to the data receiving device 105. If the communication data and the retransmission data are not identical, the monitoring device 103 transmits a message which notifies that the communication data and the retransmission data are not identical to the data generation device 101.
Abstract:
A system stores at least one item of connection information for each of a plurality of processing systems. The system receives a request from the requesting apparatus and, in response to receiving the request, sets a status related to one item of the connection information stored in the storage unit for connection to one of the processing systems. The system transmits the received request to the one processing system by using the one item of connection information and receives a response denoting a result of the processing from the one processing system. Responsive to receiving the response, the system releases the status related to the one item of connection information, and transmits the response to the requesting apparatus.
Abstract:
In accordance with disclosed embodiments, there are provided methods, systems, and apparatuses for implementing a streaming platform IO pump and regulator including, for example, means for executing an application at the computing device; requesting data for the application from a second computing device communicably interfaced with the first computing device via a public Internet; calculating an estimated arrival time for the data to be returned from the second computing device; determining the data fails to arrive within the estimated arrival time calculated; initiating a new connection to the second computing device; and re-sending the request for the data for the application to the second computing device via the new connection. Other related embodiments are disclosed.