High availability events in a layered architecture

Patent metadata

Field	Value
Publication number	US-11340967-B2
Application number	US-202017016476-A
Country	US
Kind code	B2
Filing date	Sep 10, 2020
Priority date	Sep 10, 2020
Publication date	May 24, 2022
Grant date	May 24, 2022

Abstract

Techniques are provided for high availability events in a layered architecture. In an example two computing nodes coordinate to provide a computing service, where each node has a base operating system configured to fence the other base operating system, and an application configured to fence the other application. In some examples, fencing requests by an application are routed through its base operating system, which coordinates application-level fencing requests and operating system-level fencing requests.

First claim

What is claimed is:

1. A system, comprising:
a processor; and
a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
operating a first container on a first base operating system of a first node, and operating a second container on a second node, wherein the second container is a provider of a first computer service, and wherein the first container is configured to cause the second container to cease operation independent of operation of the first base operating system;
determining, by the first container, that a heartbeat message has not been received from the second container, the heartbeat indicating a normal operation of the second container;
requesting, by the first container and of the first base operating system, that the first base operating system cause the second container to cease being the provider of the first computer service; and
in response to receiving, by the first container and from the first base operating system, an indication that the second container is no longer providing the first computer service, becoming, by the first container, the provider of the first computer service.

2. The system of claim 1 , wherein the receiving of the indication that the second container is no longer providing the first computer service comprises:
determining, by the first base operating system, that the second container has ceased providing the first computer service without additional action by the first base operating system.

3. The system of claim 1 , wherein the receiving of the indication that the second container is no longer providing the first computer service comprises:
terminating, by the first base operating system of the first node, the second container of the second node.

4. The system of claim 1 , wherein the ending of the second container from being the provider of the first computer service comprises:
requesting, by the first base operating system, that a second base operating system of the second node terminate the second container.

5. The system of claim 1 , wherein the receiving of the indication that the second container is no longer providing the first computer service comprises:
instructing, by the first base operating system, that the second base operating system power cycle.

6. The system of claim 1 , wherein the receiving of the indication that the second container is no longer providing the first computer service comprises:
in response to determining that the second container has yet to cease being the provider of the first computer service, requesting, by the first base operating system, that a second base operating system of the second node terminate the second container.

7. The system of claim 6 , wherein the operations further comprise:
in response to determining that the second base operating system failed to terminate the second container, requesting, by the first base operating system, that the second base operating system undergo a power cycle.

8. A method, comprising:
operating, by a system comprising a processor, a first container on a first operating system of a first node, and operating a second container on a second node, the second container being a provider of a first computer service;
determining, by the first container, that a message has not been received from the second container that indicates a normal operation of the second container;
requesting, by the first container and of the first operating system, that the first base operating system cause the second container to cease being the provider of the first computer service; and
in response receiving an indication, by the first container and from the first operating system, that the second container is no longer providing the first computer service, becoming, by the first container, the provider of the first computer service.

9. The method of claim 8 , wherein the first container is configured to cause the second container to cease operation independent of operation of the first operating system, and wherein the second container is configured to cause the first container to cease operation independent of operation of a second operating system of the second node.

10. The method of claim 8 , further comprising:
based on determining, by the first operating system, that the request to end the second container from being the provider of the first computer service is being processed, determining not to process a request from a second operating system of the second node to end the first container from being the provider of a second computer service.

11. The method of claim 10 , wherein the first container is configured to communicate via a first network address, wherein the first operating system is configured to communicate via a second network address, and wherein the requesting, by the first container and of the first operating system, to end the second container from being the provider of the first computer service comprises:
establishing, by the first container, a network communications channel between the first container via the first network address and the first operating system via the second network address, the requesting being performed via the network communications channel.

12. The method of claim 11 , wherein the first container receives the indication that the second container is no longer providing the first computer service via the network communications channel.

13. The method of claim 8 , further comprising:
after the first container performs the becoming of the provider of the first computer service, requesting, by the first container and of the first operating system, to resume the operating of the second container.

14. The method of claim 13 , further comprising:
in response to the requesting, by the first container and of the first operating system, to resume the operating of the second container, requesting, by the first operating system and to a second operating system of the second node, to resume the operating of the second container.

15. A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising a processor to perform operations, comprising:
determining, by a first application of a first node, that a heartbeat message has not been received from a second application of a second node, the second application being an enabler of a first computer service; and
requesting, by the first application and of a first operating system of the first node, that the first operating system cause the second application to cease being the enabler of the first computer service.

16. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:
in response receiving an indication, by the first application and from the first operating system, that the second application is no longer enabling the first computer service, becoming, by the first application, the enabler of the first computer service.

17. The non-transitory computer-readable medium of claim 15 , wherein the heartbeat message indicates a normal operation of the second application.

18. The non-transitory computer-readable medium of claim 15 , wherein the heartbeat message is part of a first group of heartbeat messages, wherein the first application periodically sends one of a second group of heartbeat messages to the second application, and wherein the second application periodically sends one of the first group of heartbeat messages to the first application.

19. The non-tr

Assignees

• Emc Ip Holding Co Llc

Inventors

• Talukdar Rohit
• Singh Pankaj

Classifications

• G06F9/544

  Buffers; Shared memory; Pipes · CPC title

• G06F11/2028 Primary

  eliminating a faulty processor or activating a spare · CPC title

• G06F11/203

  using migration · CPC title

• G06F9/542 Primary

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• G06F9/545

  where tasks reside in different layers, e.g. user- and kernel-space · CPC title