×

System and method for augmenting consensus election in a distributed database

  • US 10,496,669 B2
  • Filed: 07/01/2016
  • Issued: 12/03/2019
  • Est. Priority Date: 07/02/2015
  • Status: Active Grant
First Claim
Patent Images

1. A computer implemented method for managing a distributed database, the method comprising acts of:

  • establishing at least one primary node within a plurality of nodes, wherein the plurality of nodes comprise a distributed database system and the distributed database system provides responses to database requests from database clients;

    restricting processing of write operations received from the database clients to the at least one primary node;

    establishing at least one secondary node configured to host a replica of data hosted at the at least one primary node;

    establishing at least one arbiter node configured to;

    host an operation log of operations executed by the at least one primary node, andlimit participation in replication operations at the at least one arbiter node to updating the operation log without replication of the operations on respective data;

    wherein the at least one arbiter node does not host a replica of the data hosted by the at least one primary node;

    replicating from the at least one primary node at least one log entry reflecting the write operations executed by the at least one primary node to the at least one secondary node and the at least one arbiter node; and

    confirming a safe write operation received from a database client in response to determining that the safe write operation has been executed at a threshold number of the plurality of nodes based on a count of nodes determined to have executed the safe write operation, wherein determining that the safe write operation has been executed at the threshold number includes acts of;

    determining that the safe write operation has been executed at a respective one of the at least one arbiter node when the respective arbiter node has entered a log entry reflecting the safe write operation into the operation log hosted by the respective arbiter node, wherein execution at the respective arbiter node does not require replication of the safe write operation on respective data; and

    determining that the safe write operation has been executed at a respective one of the at least one secondary node when the respective secondary node has replicated the safe write operation in a replica of the data of the at least one primary node hosted by the respective secondary node.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×