Distributed data management

Patent metadata

Field	Value
Publication number	US-10425475-B2
Application number	US-201715442719-A
Country	US
Kind code	B2
Filing date	Feb 27, 2017
Priority date	Feb 27, 2017
Publication date	Sep 24, 2019
Grant date	Sep 24, 2019

Abstract

In some examples, a system for managing distributed data can include a processor to detect an update notification from a client device to update a managing server, the update notification indicating that a remote server node is unavailable. The processor can also generate a comparison value by comparing a first time stamp to a second time stamp, wherein the first time stamp corresponds to a time at which the system receives the update notification from the client device and the second time stamp corresponds to a time the remote server node transmits a set of renewal data. Furthermore, the processor can determine that the comparison value indicates the remote server node is unavailable and remove the remote server node from the managing server.

First claim

What is claimed is:

1. A system for managing distributed data comprising:
a processor to:
send a distributed data request to a remote server node;
detect that a period of time elapses without receiving the requested distributed data from the remote server node;
update a managing server by sending a server message to the managing server indicating that the remote server node is unavailable, the managing server to generate a comparison value by comparing a first time stamp to a second time stamp, wherein the first time stamp corresponds to a time at which the managing server receives the server message from the system and the second time stamp corresponds to a time the remote server node transmits a set of renewal data to the managing server, wherein the server message by the client device is to take precedence over the set of renewal data by the remote server node in response to the first time stamp and the second time stamp having an equal value; and
send the distributed data request to a second remote server node.

2. The system of claim 1 , wherein the system is a consumer client that is to send the distributed data request to the remote server node via the managing server.

3. The system of claim 1 , wherein the system is to monitor whether the remote server node and the second remote server node are available.

4. The system of claim 1 , wherein the distributed data corresponds to a service provided by the remote server node.

5. The system of claim 1 , wherein the server message indicates an internet protocol address corresponding to the remote server node.

6. The system of claim 1 , wherein the processor is to detect a delete message from the managing server node indicating the requested distributed data has been deleted by the remote server node.

7. The system of claim 1 , wherein the processor is to detect a change to the requested distributed data and transmit an update message to the remote server indicating the change.

8. A system for managing distributed data comprising:
a processor to:
detect an update notification from a client device to update a managing server, the update notification indicating that a remote server node is unavailable;
generate a comparison value by comparing a first time stamp to a second time stamp, wherein the first time stamp corresponds to a time at which the system receives the update notification from the client device and the second time stamp corresponds to a time the remote server node transmits a set of renewal data, wherein the update notification by the client device is to take precedence over the set of renewal data by the remote server node in response to the first time stamp and the second time stamp having an equal value;
determine that the comparison value indicates the remote server node is unavailable in response to a difference between the first time stamp and the second time stamp exceeding a threshold value; and
remove the remote server node from the managing server.

9. The system of claim 8 , wherein the managing server comprises an internet protocol address for a set of remote server nodes.

10. The system of claim 8 , wherein the processor is to identify a second remote server node from a predetermined list.

11. The system of claim 10 , wherein the processor is to determine the second remote server node in response to querying the managing server for the second remote server node.

12. The system of claim 8 , wherein the processor is to remove the remote server node is to prevent additional client devices from attempting to access the remote server node.

13. The system of claim 8 , wherein the processor is to fail the update notification from the client device in response to determining that the remote server node is unavailable.

14. The system of claim 8 , wherein the processor is to detect the set of renewal data at a predetermined frequency.

15. The system of claim 8 , wherein the managing server comprises a database comprising identifying information for a plurality of remote server nodes.

16. A computer program product for managing distributed data, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program instructions executable by a processor to cause the processor to:
detect an update notification from a client device to update a managing server, the update notification indicating that a remote server node is unavailable;
generate a comparison value by comparing a first time stamp to a second time stamp, wherein the first time stamp corresponds to a time at which the system receives the update notification from the client device and the second time stamp corresponds to a time the remote server node transmits a set of renewal data, wherein the update notification by the client device is to take precedence over the set of renewal data by the remote server node in response to the first time stamp and the second time stamp having an equal value;
determine that the comparison value indicates the remote server node is unavailable in response to a difference between the first time stamp and the second time stamp exceeding a threshold value; and
remove the remote server node from the managing server.

17. The computer program product of claim 16 , wherein the program instructions cause the processor to identify a second remote server node from a predetermined list.

18. The computer program product of claim 17 , wherein the program instructions cause the processor to determine the second remote server node in response to querying the managing server for the second remote server node.

19. The computer program product of claim 16 , wherein the managing server comprises an internet protocol address for a set of remote server nodes.

20. The computer program product of claim 16 , wherein the program instructions cause the processor to detect the set of renewal data at a predetermined frequency.

Assignees

• IBM

Inventors

• Cahana Zvi
• Lev-Ran Etai
• Zach Idan

Classifications

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L69/28

  Timers or timing mechanisms used in protocols · CPC title

• H04L43/16

  Threshold monitoring · CPC title

• H04L41/5025

  by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade · CPC title

• H04L43/0805

  by checking availability · CPC title