EngineConn History Features

    1.2 Goals

    • Complete the storage of EC information and resource information persistent to DB
    • Supports viewing and searching of historical EC information through the restful interface
    • Support to view logs of EC that has ended

    2. Overall Design

    The main changes in this feature are the RM and AM modules under LinkisManager, and an information record table has been added.

    2.1 Technical Architecture

    Because this implementation needs to record EC information and resource information, and resource information is divided into three concepts, such as requesting resources, actually using resources, and releasing resources, and all of them need to be recorded. Therefore, the general plan for this implementation is: based on the EC in the life cycle of the ResourceManager to implement, and when the EC completes the above three stages, the update operation of the EC information is added. The overall picture is shown below:

    This feature is mainly to complete the information recording of historical ECs and support the log viewing of historical technical ECs. The modules designed by the function point are as follows:

    Core execution flow

    • [Input] The input is mainly for the requested resource when the engine is created, the real used resource reported after the engine is started, and the information input when the resource is released when the engine exits, mainly including the requested label, resource, EC’s unique ticketid, resource type etc.
    • [Processing process] Information recording service, which processes the input data, and parses the corresponding engine information, user, creator, and log path through tags. Confirm the resource request, use, and release by the resource type. Then talk about the information stored in the DB.

    The call sequence diagram is as follows:

    4. Data structure:

    6. Non-functional design

    6.1 Security

    No security issues are involved, the restful interface requires login authentication

    Less impact on engine life cycle performance

    6.3 Capacity

    6.4 High Availability

    not involving