METHODS AND APPARATUS FOR IMPLEMENTING A DISTRIBUTED DATABASE

• US 20130151558A1
• Filed: 02/01/2012
• Published: 06/13/2013
• Est. Priority Date: 12/12/2011
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Escribano Bullon, Berta Isabel, CHRCOLES SNCHEZ, Jos Mara
• Application Number:
  US13/363,818
• Publication Number:
  US 20130151558A1
• Time in Patent Office: Days
• US Class Current: 707/770
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

According to a first aspect of the present invention there is provided a node of a distributed database, the node providing database clients with access to the distributed database. The node comprises a receiver configured to receive communications from database clients and other nodes of the distributed database, a transmitter configured to send communications to database clients and other nodes of the distributed database and a processor. The processor is configured to fulfil the data request using a version of the data instance that is stored by a database instance of the distributed database that has been assigned ownership of the data instance.

Claims

1. A node of a distributed database, the node providing database clients with access to the distributed database, the node comprising:

a receiver configured to receive communications from database clients and other nodes of the distributed database;

a transmitter configured to send communications to database clients and other nodes of the distributed database; and

a processor configured to, upon receipt of a data request from a database client, the data request relating to a data instance, determine if a version of the data instance is stored in a database instance that is local to the database client, determine if ownership of the data instance has been or should be assigned to a local database instance, and

where it is determined that either a local database instance is currently assigned ownership of the data instance or that ownership of the data instance should be transferred to a local database instance, to then use the version of the data instance that is stored at the local database instance to fulfil the data request;

where it is determined that a version of the data instance is not stored at a local database instance and that ownership of the data instance should be transferred to a local database instance, to then copy the data instance from a remote database instance and use the copy data instance to fulfil the data request;

where it is determined that a version of the data instance is not stored at a local database instance or that a version of the data instance is stored at a local database instance that is not currently assigned ownership of the data instance, and it is determined that ownership of the data instance should not be transferred to a local database instance that is not the current owner, then use a version of the data instance stored at a remote database instance to fulfil the data request.

2. A node as claimed in claim 1, wherein, if it is determined that a version of the data instance is not stored at a local database instance and that ownership of the data instance should be transferred to a local database instance, the processor is configured to copy an original data instance, the original data instance being the first occurrence of the data instance to be stored in the distributed database.

3. A node as claimed in claim 1, and further comprising a memory configured to store location information, the location information identifying data instances for which a version of the data instance is stored by a local database instance, identifying the local database instance that stores a version of the data instance and identifying if the local database instance been assigned ownership of the data instance, the processor being further configured to check the location information stored in the memory to determine if a version of the data instance is stored in a database instance that is local to the database client and to determine if a local database instance is currently assigned ownership of the data instance.

4. A node as claimed in claim 3, wherein the memory is further configured to store location information that identifies the version of a data instance that is stored by a local database as one of:

an original data instance, an original data instance being the first occurrence of a data instance to be stored in the distributed database;

a replica data instance, a replica data instance being a replica of an original data instance; and

a copy data instance, a copy data instance being a copy of a data instance.

5. A node as claimed in claim 3, wherein, if it is determined that ownership of the data instance should be transferred to a local database instance, the processor is further configured to:

update ownership information that is stored with the original data instance to identify the local database instance as the current owner of the data instance.

6. A node as claimed in claim 1, wherein, in order to determine if ownership of the data instance should be transferred to a local database instance, the processor is further configured to evaluate an ownership policy.

7. A node as claimed in claim 6, and further comprising a memory configure to store the ownership policy that is to be evaluated by the processor, the ownership policy including one or more of:

conditions relating to the data instance;

conditions relating to the current owner database instance;

conditions relating to local database instances; and

conditions relating to the overall status of the distributed database.

9. A distributed database comprising a plurality of database nodes, each of the plurality of database nodes being in accordance with claim 1.

8. A node of a distributed database, the node providing a database instance of the distributed database, the node comprising:

a receiver configured to receive communications from other nodes of the distributed database;

a transmitter configured to send communications to other nodes of the distributed database;

a memory having a first portion and a second portion, the first portion being reserved for storing original data instances, original data instances being the first occurrence of a data instance that is stored in the distributed database, and the second portion being reserved for storing any replica data instances that have been replicated to the database instance from other database instances and any copy data instances that have been copied to the database instance from other database instances; and

a processor configured to, upon receipt of a data request relating to an original data instance or replica data instance stored in the memory, check ownership information that is stored with the data instance, the ownership information identifying the database instance that is currently assigned ownership of the data instance.

10. A method of operating a node of a distributed database, the node providing database clients with access to the distributed database, the method comprising the steps of:

upon receipt of a data request from a database client, the data request relating to a data instance, determining if a version of the data instance is stored in a database instance that is local to the database client, determining if ownership of the data instance has been or should be assigned to a local database instance, and

where it is determined that a version of the data instance is stored at a local database instance, and that either the local database instance is currently assigned ownership of the data instance or that ownership of the data instance should be transferred to a local database instance, use the version of the data instance that is stored at a local database instance to fulfil the data request;

where it is determined that a version of the data instance is not stored at a local database instance and that ownership of the data instance should be transferred to a local database instance, copy the data instance from a remote database instance and use the copy data instance to fulfil the data request;

where it is determined that a version of the data instance is not stored at a local database instance or that a version of the data instance is stored at a local database instance that is not currently assigned ownership of the data instance, and it is determined that ownership of the data instance should not be transferred to a local database instance that is not the current owner, use a version of the data instance stored at a remote database instance to fulfil the data request.

11. A method as claimed in claim 10, wherein, if it is determined that a version of the data instance is not stored at a local database instance and that ownership of the data instance should be transferred to a local database instance, the method further comprises:

copying the original data instance, the original data instance being the first occurrence of the data instance to be stored in the distributed database.

12. A method as claimed in claim 10, and further comprising storing location information, the location information identifying data instances for which a version of the data instance is stored by a local database instance, identifying the local database instance that stores a version of the data instance and identifying if the local database instance been assigned ownership of the data instance, and checking the location information stored in the memory to determine if a version of the data instance is stored in a database instance that is local to the database client and to determine if a local database instance is currently assigned ownership of the data instance.

13. A method as claimed in claim 12, wherein location information identifies the version of a data instance that is stored by a local database as one of:

an original data instance, an original data instance being the first occurrence of a data instance to be stored in the distributed database;

a replica data instance, a replica data instance being a replica of an original data instance; and

a copy data instance, a copy data instance being a copy of a data instance.

14. A method as claimed in claim 13, wherein, if it is determined that ownership of the data instance should be transferred to a local database instance, the method further comprises:

updating ownership information that is stored with the original data instance to identify the local database instance as the current owner of the data instance.

15. A method as claimed in claim 10, wherein, in order to determine if ownership of the data instance should be transferred to a local database instance, the method further comprises evaluating an ownership policy.

16. A method as claimed in claim 15, wherein the ownership policy that is to be evaluated includes one or more of:

conditions relating to the data instance;

conditions relating to the current owner database instance;

conditions relating to local database instances; and

conditions relating to the overall status of the distributed database.

18. A distributed database comprising a plurality of database nodes, wherein each of the database nodes is configured to implement the method of claim 10.

17. A method of operating a node of a distributed database, the node providing a database instance of the distributed database, the method comprising:

storing original data instances in a first portion of a memory of the node, original data instances being the first occurrence of a data instance that is stored in the distributed database, and

storing any replica data instances that have replicated to the database instance from other databases instance and any copy data instances that have been copied to the database instance from other database instances in a second portion of a memory of the node; and

upon receipt of a data request relating to an original data instance or replica data instance stored in the memory, checking ownership information that is stored with the data instance, the ownership information identifying the database instance that is currently assigned ownership of the data instance.