Skip to main content
Version: 1.3.0

LinkisManager Architecture Design

        As an independent microservice of Linkis, LinkisManager provides AppManager (application management), ResourceManager (resource management), and LabelManager (label management) capabilities. It can support multi-active deployment and has the characteristics of high availability and easy expansion.

1. Architecture Diagram

Architecture Diagram

Noun explanation

  • EngineConnManager (ECM): Engine Manager, used to start and manage engines.
  • EngineConn (EC): Engine connector, used to connect the underlying computing engine.
  • ResourceManager (RM): Resource Manager, used to manage node resources.

2. Introduction to the second-level module

2.1. Application management module linkis-application-manager

        AppManager is used for unified scheduling and management of engines:

Core Interface/ClassMain Function
EMInfoServiceDefines EngineConnManager information query and modification functions
EMRegisterServiceDefines EngineConnManager registration function
EMEngineServiceDefines EngineConnManager's creation, query, and closing functions of EngineConn
EngineAskEngineServiceDefines the function of querying EngineConn

LinkisManager Architecture Design

        As an independent microservice of Linkis, LinkisManager provides AppManager (application management), ResourceManager (resource management), and LabelManager (label management) capabilities. It can support multi-active deployment and has the characteristics of high availability and easy expansion.

1. Architecture Diagram

Architecture Diagram

Noun explanation

  • EngineConnManager (ECM): Engine Manager, used to start and manage engines.
  • EngineConn (EC): Engine connector, used to connect the underlying computing engine.
  • ResourceManager (RM): Resource Manager, used to manage node resources.

2. Introduction to the second-level module

2.1. Application management module linkis-application-manager

        AppManager is used for unified scheduling and management of engines:

Core Interface/ClassMain Function
EMInfoServiceDefines EngineConnManager information query and modification functions
EMRegisterServiceDefines EngineConnManager registration function
EMEngineServiceDefines EngineConnManager's creation, query, and closing functions of EngineConn
EngineAskEngineServiceDefines the function of querying EngineConn
EngineConnStatusCallbackServiceDefines the function of processing EngineConn status callbacks
EngineCreateServiceDefines the function of creating EngineConn
EngineInfoServiceDefines EngineConn query function
EngineKillServiceDefines the stop function of EngineConn
EngineRecycleServiceDefines the recycling function of EngineConn
EngineReuseServiceDefines the reuse function of EngineConn
EngineStopServiceDefines the self-destruct function of EngineConn
EngineSwitchServiceDefines the engine switching function
AMHeartbeatServiceProvides EngineConnManager and EngineConn node heartbeat processing functions

        The process of applying for an engine through AppManager is as follows:
AppManager

2. Label management module linkis-label-manager

        LabelManager provides label management and analysis capabilities.

Core Interface/ClassMain Function
LabelServiceProvides the function of adding, deleting, modifying and checking labels
ResourceLabelServiceProvides resource label management functions
UserLabelServiceProvides user label management functions

The LabelManager architecture diagram is as follows:
ResourceManager

4. Monitoring module linkis-manager-monitor

        Monitor provides the function of node status monitoring.