Distributed database for one search key

• US 20050097105A1
• Filed: 02/06/2002
• Published: 05/05/2005
• Est. Priority Date: 02/06/2002
• Status: Abandoned Application

• Current Assignee: Tecnomen Lifetree Oyj
• Original Assignee: Tecnomen Lifetree Oyj
• Inventors: Ranta, Jari
• Application Number:
  US10/502,165
• Publication Number:
  US 20050097105A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2255 Hash tables

Abstract

Method and arrangement for storing information in data network into a network element in accordance with a hash value of the search key; and a method adding a new element using overlapping hash values for the primary and secondary element to keep the service available during the element adding process and in case of hardware failure.

Claims

1. A distributed database using multiple network nodes and a search key referring user data, characterised in that the search key is used as an argument for a hash function to generate a pseudo-random key for pointing to an individualised node for storing the data in the network.

2. A distributed database according to claim 1, characterised in that each record is stored automatically in at least one primary node and in at least one secondary node, the said hash function values being used to point to primary and secondary nodes, so that data is accessed from the secondary node in case of failure to access the data from the primary node.

3. A distributed database according to claim 2, characterised in that each record is automatically stored in nodes with successive hash values.

4. A distributed database according to any of the preceding claims, characterised in that each node acts as a primary and as a secondary node at same time for different search keys.

5. A distributed database according to any of the preceding claims 2 to 4, characterised in that the changed data is automatically copied between the primary and secondary nodes by the servers in the nodes.

6. A distributed database according to any of the preceding claims 2 to 5, characterised in that the data stored the primary and secondary nodes contains pointers to elements in the network for storing user files and copies of user files.

7. A distributed database according to any of the preceding claims 2 to 6, characterised in that adding a node in the system is done by moving the records with a changed hash value for a primary or secondary node to the location according to the new hash value, and the primary node and secondary node together maintain the service available for both new and old hash value searches by using overlapping primary and secondary server hash values to ensure access for clients during the move, and the nodes keep a list of changes that could not be updated in either primary or secondary copy of the record in the corresponding node.

8. A method for storing and accessing information in a multi-computer environment, characterised in the steps of calculating the hash function of the search key for the information;

determining the node with the hash function value of the search key;

determining a secondary node from the said hash function value for determining a secondary node for backup;

storing the information in the servers in the primary and secondary node;

accessing the information by calculating the hash value of the search key and accessing the node with the hash value or with the secondary hash value.

9. A method for adding a server in a system functioning according to claim 8, characterised in the steps of calculating new hash values for servers, calculating new and old hash values for each file to be possibly moved;

moving the files which should be in a different server according to the new hash value.

10. A method for accessing the files during the server adding operation according to claim 9, characterised in the use of hash values which overlap for primary and secondary servers'"'"' addresses for new and old configurations in such a way that always either the primary or the secondary server is found with the old hash value, even if the data has already been moved to the new server.