Service unit off-line method and related device based on micro-service unit architecture

Abstract

An embodiment of the present invention provides a service unit offline method based on a microservice unit architecture and a related device. The method includes: first obtaining a service unit offline command including the name of the service unit to be offline; and then according to the pending The name of the offline service unit determines whether the service unit to be offline is in the running state, and when it is determined that the service unit to be offline is in the running state according to the name of the service unit to be offline, log off the microservice unit architecture The name of the service unit to be offline in the registered service unit list, and start timing at the same time to obtain the offline waiting time; when the offline waiting time of the service unit to be offline meets the service unit to be offline When waiting for the time threshold, log off the service unit to be offline. The service unit offline method and related devices based on the micro-service unit architecture provided by the embodiment of the present invention can ensure that the service unit realizes graceful offline, and avoids the problem of request interruption.

Description

technical field [0001] The embodiments of the present invention relate to the field of computers, and in particular to a method for offline service units based on a micro-service unit architecture and related devices. Background technique [0002] In the distributed architecture of microservice units, it is very important to manage the online and offline of microservice units. [0003] In the native scenario of Kubernetes, although the smallest object of the system is a Pod (microservice unit group), the creation and destruction of Pods (or online and offline) are judged by the Kubernetes system itself, and the operator cannot directly target each Each Pod performs online and offline operations, but uses registration centers such as Eureka for indirect management. [0004] In the existing technology, when Pods are indirectly managed by a registration center such as Eureka, Pods in the Terminating state will be directly removed from the registration list (EndPoint, etc.) of ...

AI Technical Summary

Problems solved by technology

[0003] In the native Kubernetes scenario, although the smallest object of the system is a Pod (microservice unit group), the creation and destruction of Pods (or online and offline) are judged by the Kubernetes system itself, and the operator cannot directly target each Each Pod performs online and offline operations, but uses registration centers such as Eureka for indirect management

[0004] In the existing technology, when using a registration center such as Eureka to indirectly manage Pods, Pods in the Terminating state will be directly removed from the registration list (EndPoint, etc.) of the registration center, resulting in inaccessible requests. The specific Pod will eventually cause the request to be cut off

Images