Abstract: Lease transfer between master and slave replicas is described. A master replicator determines that an initial master replica lease takes effect. On determining that a master replica transfer needs to be performed, sending a transfer preparation message to a target replicator prior to expiration of a current master replica lease. The target replicator locally starts and calculates a new master replica lease and returns a readiness response to the master replicator. The master replicator sends a lease extension message to remaining slave replicators to extend local corresponding leases. After receiving lease extension success responses of a majority of the slave replicators, the master replicator terminates the local master replica lease of the master replicator in advance, and sends a transfer confirmation message to the target replicator. The target replicator validates the new master replica lease to make the target replicator a new master replicator.

Abstract: Methods, systems, electronic devices and computer-readable media for database transaction processing are provided. In an example, after determining to perform primary-secondary switching of a copy, a first server records a context of a database transaction that is currently being executed, sends the context to a second server, and switches a primary copy stored in the first server to a secondary copy. The second server switches a secondary copy stored in the second server to a primary copy, and continues execution of the database transaction based on the context after completing the switching.

Abstract: Embodiments of the present specification provide a method for updating a database by using a two-phase commit distributed transaction. The method is applied to a coordinator, and includes: sending a first-phase prepare request message to each participant to end a current transaction, the current transaction being configured to update a target database record; and after receiving write lock advance release requests sent by all participants, returning a write lock advance release response to each participant to instruct each participant to unlock a target database record of the participant, the write lock advance release requests being sent by the participants after the participants successfully write a log of an update operation of the current transaction to a log buffer.

Abstract: Embodiments of the present specification provide a method for updating a database by using a two-phase commit distributed transaction. The method is applied to a coordinator, and includes: sending a first-phase prepare request message to each participant to end a current transaction, the current transaction being configured to update a target database record; and after receiving write lock advance release requests sent by all participants, returning a write lock advance release response to each participant to instruct each participant to unlock a target database record of the participant, the write lock advance release requests being sent 1w the participants after the participants successfully write a log of an update operation of the current transaction to a log buffer.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.

Abstract: A same voting time, a same vote counting time, and a same leader node tenure is configured by a host for all nodes. Time configuration information including the same configured voting time, the same vote counting time, and the same leader node tenure, is sent to all the nodes. The nodes are operable to vote during the same voting time, count the number of votes during the same vote counting time, and elect a leader node according to a vote counting result. The nodes are enabled to perform periodic node election according to the same leader node tenure.