Management method of XXL distributed task scheduling system and related device

Abstract

The invention discloses a management method of an XXL distributed task scheduling system and a related device. The method is applied to xxljob comprising an address offline interface, an address online interface, a JWT interceptor and an authentication interface. When the method provided by the embodiment of the invention is executed, the JWT interceptor can intercept the address offline request sent by the user through the address offline interface, and performs identity verification on the user sending the request through the authentication interface. And if the identity verification passes the JWT interceptor, the address offline interface is released. And finally, in the executor associated with the target application, deleting the target offline address included in the released address offline request. Through the interface and the interceptor, the system can automatically process the address offline request, the requirement of manual operation is reduced, and the working efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a management method and related devices for an XXL distributed task scheduling system. Background Art

[0002] During application updates and troubleshooting, timely isolation of affected applications is a key step to ensure the stability and reliability of the system running the applications. When an application needs to be updated or encounters a failure, it is usually necessary to manually take the schedulable addresses of the relevant executors offline one by one. This process is not only time-consuming, but also prone to omissions, that is, some offline addresses may be forgotten and fail to go offline in time. This manual operation method leads to low offline efficiency.

[0003] Therefore, how to implement an automated and efficient address offline mechanism to improve the efficiency of application updates and troubleshooting, thereby reducing human errors and omissions, is a technical problem that technical personnel in this field urgently need to solve. Summary of the invention

[0004] Based on the above problems, the present application provides a management method and related devices for an XXL distributed task scheduling system, which can realize an automated and efficient address offline mechanism to improve the efficiency of application updates and fault handling, thereby reducing human errors and omissions.

[0005] The embodiments of the present application disclose the following technical solutions:

[0006] A management method of an XXL distributed task scheduling system is applied to the XXL distributed task scheduling system xxljob, wherein the xxljob includes an address offline interface, an address online interface, a JSON network token JWT interceptor and an authentication interface, and the method includes:

[0007] In response to an address offline request sent by a user through the address offline interface, the JWT interceptor intercepts the address offline request in the address offline interface; the address offline request includes a target offline address; the target offline address is determined by the user when the target application is updated or a fault occurs; the target offline address is determined by the user when the target application completes the update or the fault disappears; the target offline address is in the form of a uniform resource locator URL;

[0008] The authentication interface authenticates the user who sends the address offline request;

[0009] If the identity authentication is passed, the JWT interceptor releases the address offline request in the address offline interface;

[0010] In an executor associated with the target application, a target offline address included in the released address offline request is deleted.

[0011] In a possible implementation, the method further includes:

[0012] In response to an address online request sent by a user through the address online interface, the JWT interceptor intercepts the address online request in the address online interface; the address online request includes a target online address; the target online address is determined by the user when the target application completes the update or the fault disappears; the target online address is in the form of a URL;

[0013] The authentication interface authenticates the user who sends the address online request;

[0014] If the identity authentication is passed, the JWT interceptor releases the address online request in the address online interface;

[0015] In the executor associated with the target application, a target online address included in the released address online request is added.

[0016] In a possible implementation, the method further includes:

[0017] In response to a user importing a scheduled task file through the file batch import interface of the xxljob, the authentication interface authenticates the user who imports the scheduled task file; the scheduled task file is filled in by the user according to the Excel template; the format of the scheduled task file is Excel format; the Excel template includes information for guiding the deployment, maintenance or update of the target application;

[0018] If the identity authentication is passed, then check whether the format of the scheduled task file is consistent with the format of the Excel template;

[0019] If they are consistent, convert the scheduled task file into entity class objects line by line;

[0020] Generate corresponding scheduled task configuration parameters according to the entity class object;

[0021] Import the scheduled task configuration parameters in batches into the scheduled task management system.

[0022] In a possible implementation, the method further includes:

[0023] In response to the Excel template request sent by the user through the template request interface of the xxljob, the authentication interface authenticates the user who sent the Excel template request;

[0024] If the identity authentication is passed, the Excel template is exported to the user who sent the Excel template request through the template request interface.

[0025] In a possible implementation manner, the method further includes: storing the target offline address to be deleted in a hash set HashSet.

[0026] In a possible implementation, in the executor associated with the target application, the target online address included in the address online request that is newly released includes:

[0027] When the target online address is newly added in the executor associated with the target application, the target offline address stored in the HashSet that is consistent with the target online address is added to the executor associated with the target application.

[0028] A xxljob, the xxljob comprising:

[0029] A JWT interceptor, in response to an address offline request sent by a user through the address offline interface, is used to intercept the address offline request in the address offline interface; the address offline request includes a target offline address; the target offline address is determined by the user when the target application is updated or fails; the target offline address is in a unified URL format;

[0030] An authentication interface, used to authenticate the identity of the user who sent the offline request for the address;

[0031] If the identity authentication is passed, the JWT interceptor is also used to release the address offline request in the address offline interface;

[0032] The address deleting unit is used to delete, in an executor associated with the target application, a target offline address included in the address offline request in the released address offline interface.

[0033] In a possible implementation, the xxljob further includes: an address online interface and an address adding unit;

[0034] In response to an address online request sent by a user through the address online interface, the JWT interceptor is further used to intercept the address online request in the address online interface; the address online request includes a target online address; the target online address is determined by the user when the target application completes the update or the fault disappears; the target online address is in the form of a URL;

[0035] The authentication interface is also used to authenticate the user who sends the address online request;

[0036] If the identity authentication is passed, the JWT interceptor is also used to release the address online request in the address online interface;

[0037] In the executor associated with the target application, the address adding unit is used to add a target online address included in the released address online request.

[0038] A management device for an XXL distributed task scheduling system comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the management method for the XXL distributed task scheduling system as described above is implemented.

[0039] A computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device executes the management method of the XXL distributed task scheduling system as described above.

[0040] Compared with the prior art, this application has the following beneficial effects:

[0041] The present application provides a management method and related devices for a XXL distributed task scheduling system. Specifically, when executing the management method for the XXL distributed task scheduling system provided by the embodiment of the present application, task management can be performed first through the address offline interface and the address online interface, and the JSON Web Token (JSON Web Token, JWT) interceptor and the authentication interface are used to ensure security. When a user sends an offline request through the address offline interface, the JWT interceptor intercepts the request. The offline request contains a target address, which is determined by the user when the application is updated or fails. The authentication interface verifies the user's identity. If the verification is successful, the JWT interceptor allows the request to pass, and then deletes the specified offline address in the executor associated with the target application. This process ensures the security and effectiveness of task scheduling. In the present application, the address offline request can be processed immediately after being received in the xxljob with the address offline interface, which greatly improves the response speed, and the xxljob with the address offline interface can ensure that each specified offline address is effectively executed, avoiding problems caused by human negligence. At the same time, by integrating the JWT interceptor for identity authentication, it can be ensured that only authorized users can perform offline or online operations. This not only enhances the security of the system, but also prevents unauthorized access and manipulation. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0043] Figure 1 A method flow chart of a management method of an XXL distributed task scheduling system provided in an embodiment of the present application;

[0044] Figure 2 A method flow chart of another method for managing an XXL distributed task scheduling system provided in an embodiment of the present application;

[0045] Figure 3 A method flow chart of another method for managing an XXL distributed task scheduling system provided in an embodiment of the present application;

[0046] Figure 4 A structural schematic diagram of xxljob provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the background technology involved in the embodiments of the present application will be described below.

[0048] When applications are updated or encounter failures, quickly isolating the affected applications is critical to maintaining the stability and reliability of the systems running the applications. This operating mode has obvious disadvantages:

[0049] Inefficiency: In large-scale deployment scenarios, especially when faced with hundreds or thousands of possible service nodes, manual operations one by one are not only time-consuming and cumbersome, but also greatly increase the burden of operation and maintenance;

[0050] Risk of missed execution: During manual management, operators may neglect or forget to remove a specific node from the system in a timely manner. This omission is not only a waste of resources, but may also become a hidden danger to system stability, affecting subsequent update deployment or fault recovery operations;

[0051] The isolation time is too long: It takes a long time to completely complete the offline operation of all nodes, which may not only cause service interruptions, but also have a negative impact on the overall performance of the system, manifested as response delays and reduced service stability.

[0052] In addition, the process of putting the application into formal use (i.e., production) usually includes deploying the developed system to the production environment so that it can provide services to users. During the production process, some configuration and settings may be required, such as adding scheduled tasks, to ensure the normal operation of the system. However, when it is put into production, it is necessary to manually add scheduled tasks according to the Excel provided by each center. Adding them one by one is troublesome, the production time is long, and manually adding scheduled tasks is prone to errors.

[0053] In order to solve this problem, a management method and related devices of a XXL distributed task scheduling system are provided in an embodiment of the present application. The method is applied to xxljob, and xxljob includes multiple key components, such as an address offline interface, an address online interface, a JWT interceptor, and an authentication interface. The specific process is: when a user sends an address offline request through the address offline interface, the JWT interceptor intercepts the request. The request contains the target offline address determined by the user, which is usually specified when the target application is updated or fails, and is confirmed by the user again after the corresponding problem is resolved. The target offline address is presented in the form of a uniform resource locator (URL). Then, the authentication interface authenticates the sender of the request, and only users who pass the authentication can continue to perform the offline operation. If the authentication is successful, the JWT interceptor will release the request, and then delete the target offline address specified in the released address offline request in the executor related to the target application. By implementing an automated offline mechanism, the present application can automatically respond to user requests and quickly perform offline operations when the target application is updated or fails. Compared with manual processing, automation greatly improves efficiency and reduces the possibility of human error. In addition, the use of JWT interceptors combined with authentication interfaces for user identity authentication ensures that only authorized users can initiate offline requests. This mechanism increases the security of the system and prevents unauthorized external access and misoperation.

[0054] In response to the technical problem that "at the time of production, it is necessary to manually add scheduled tasks according to the Excel provided by each center. It is troublesome to add one by one, the production time is long, and manually adding scheduled tasks is prone to errors", this application first authenticates the user who imports the file through the authentication interface. The user needs to fill in the scheduled task file according to the Excel template provided. The file is in Excel format and contains the information required to deploy, maintain or update the target application. If the identity authentication is successful, the system will check whether the format of the scheduled task file meets the requirements of the Excel template. Once the format is consistent, the system will convert the scheduled task file line by line into entity class objects, and generate corresponding scheduled task configuration parameters based on these objects, and finally import these configuration parameters into the scheduled task management system in batches, thereby realizing batch import. Through batch import, users can add multiple scheduled tasks at one time, significantly shorten the production time, and avoid the tedious process of manually adding one by one. See steps B1-B5 for details.

[0055] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0056] See also Figure 1 , which is a method flow chart of a management method of an XXL distributed task scheduling system provided by an embodiment of the present application, and the method is applied to xxljob (i.e., XXL distributed task scheduling system) including an address offline interface, an address online interface, a JWT interceptor, and an authentication interface. xxljob is a distributed task scheduling framework, which is usually used to manage and schedule scheduled tasks. It provides a simple way to execute various tasks on a scheduled basis, and is suitable for use in large-scale distributed systems.

[0057] like Figure 1 As shown, the management method of the XXL distributed task scheduling system may include steps S101-S104:

[0058] S101: In response to an address offline request sent by a user through the address offline interface, the JWT interceptor intercepts the address offline request in the address offline interface.

[0059] When a user sends an address offline request through the address offline interface, the request contains the target offline address. This target address is determined by the user in the case of target application updates or failures, in order to effectively manage and maintain system stability.

[0060] In this process, the role of the JWT interceptor is to intercept the request sent to ensure that only authenticated users can perform address offline operations. This means that after receiving the request, the system will first check the user's identity information to ensure that they have the corresponding permissions. If the identity authentication is successful, the JWT interceptor will release the request and allow it to continue to the subsequent processing stage.

[0061] It should be noted that the target offline address is presented in the form of a URL, so that the system can accurately identify and process the relevant address information. The entire process is designed to improve the security and flexibility of the system, while ensuring that the system can run smoothly when applying updates or troubleshooting.

[0062] S102: The authentication interface performs identity authentication on the user who sends the address offline request.

[0063] The authentication interface is responsible for authenticating the user who sends the address offline request to ensure that only authorized users can perform such operations.

[0064] Specifically, the authentication interface collects the user's login information, including username and password, through the interface or front-end page. After the user submits this information, the system will verify it: first, the login username and password entered by the user are compared with the correct credentials stored in the database. If the two match, the system will consider the authentication to be successful and allow the user to continue the address offline operation; otherwise, the request will be rejected and the user will be prompted to re-enter. This process ensures the security of the system and prevents unauthorized users from interfering with or modifying the task scheduling system, thereby maintaining the reliability and security of the overall operation.

[0065] S103: If the identity authentication is passed, the JWT interceptor releases the request in the address offline request in the address offline interface.

[0066] Once the user is authenticated successfully, the JWT interceptor will allow the request to proceed through the address offline interface.

[0067] Specifically, when a user sends an address offline request, xxljob will first authenticate through the JWT interceptor to confirm whether the user has sufficient permissions to perform this operation. If the result of the authentication is passed, it means that the user is considered legitimate and has the right to make an offline request, then the JWT interceptor will "release" the request, that is, it will no longer block or reject the request, but pass it to the subsequent processing module of the system. This mechanism ensures that only authenticated users can affect the state of the system, thereby maintaining the security and stability of the system. In actual operation, the release process usually involves passing the request data to the next processing link, such as executing related business logic or calling other services to complete the ultimate goal of the user's request.

[0068] S104: In an executor associated with the target application, the target offline address included in the released address offline request is deleted.

[0069] In an executor associated with a specific target application, it is necessary to remove the target offline address specified in the address offline request that is allowed to continue processing after authentication.

[0070] Specifically, after the user's request is authenticated and released by the JWT interceptor, the system will pass the request to the executor associated with the target application. In the executor, the target address that needs to be offline is identified based on the information in the request, and then the corresponding operation is performed to delete it from the executor's management list. This process usually involves updating the internal data structure of the executor, such as removing records related to the target offline address from the database or cache to ensure that the system no longer processes the address to prevent misleading requests or traffic. At the same time, this deletion operation may also trigger some subsequent processing processes, such as notifying related components or system status updates to ensure the stability and consistency of the entire system. Through such a mechanism, the system can effectively manage resources, respond to user needs in a timely manner, and maintain overall operating efficiency.

[0071] In a possible implementation manner, the method further includes: storing the target offline address to be deleted in a hash set HashSet.

[0072] Storing the target offline address to be deleted in a hash set (HashSet) means managing and recording the offline addresses in the system for subsequent query and operation.

[0073] Specifically, when a user initiates an address offline request and passes identity authentication, the system will add the target offline address contained in the request to a hash set. A hash set is a data structure based on a hash table with efficient storage and search performance. A hash set can effectively manage a large number of offline addresses, ensuring that this information can be quickly accessed when needed, such as when restoring services or troubleshooting.

[0074] See also Figure 2 , Figure 2 A method flow chart of another method for managing an XXL distributed task scheduling system provided in an embodiment of the present application can be implemented specifically through steps A1-A4:

[0075] A1: In response to an address online request sent by a user through the address online interface, the JWT interceptor intercepts the address online request in the address online interface.

[0076] When a user wants to restore an application or service in the system, the user will initiate a request through the "address online interface". The target online address mentioned here is the address of the network location of the application or service to be restarted or restored, usually presented in the form of a URL. This means that after the application update is completed or the fault is fixed, the user will explicitly specify the URL of the application to return to the network environment so that the system can accurately identify and process it. The key operation here is to ensure that the application is only allowed to reconnect to the system when the application status meets specific conditions (such as the update has been completed or the fault has been resolved), thereby achieving effective management and control of the application online process.

[0077] A2: The authentication interface authenticates the user who sends the address online request.

[0078] By calling the "authentication interface" to verify the user's identity, unauthorized users can be prevented from trying to put unready applications online in the system, thereby protecting the system from potential security threats. Authentication usually involves checking whether the user's credential information is valid, such as a password, to confirm that the requester is indeed a role or user in the system who is authorized to perform this operation.

[0079] The identity authentication method of step A2 is similar to that of step S102 and will not be described again here.

[0080] A3: If the identity authentication is passed, the JWT interceptor releases the address online request in the address online interface.

[0081] Only when the user's identity authentication is successful, the JWT interceptor will decide to "release" the address online request. This means that the online request made by the user who has passed the identity authentication and confirmed to have the corresponding authority will be accepted by the system. This process ensures that only legal and authorized instructions can change the operating status of the system, improving the security and stability of the system.

[0082] A4: In the executor associated with the target application, a target online address included in the released address online request is added.

[0083] Once the address online request is released, it means that the executor in the system (the component responsible for the actual scheduling and management of task execution) needs to operate the target application according to the released request. The operation here may involve reconfiguring the environment, activating or starting a specific service instance, or adjusting its role or permission settings in the system, with the goal of ensuring that the application returns to normal operation according to the preset rules and status. These operations are performed automatically within the system, aiming to efficiently and seamlessly manage the online application and keep the entire system running smoothly.

[0084] In a possible implementation, in the executor associated with the target application, the target online address included in the address online request that is newly released includes:

[0085] When the target online address is newly added in the executor associated with the target application, the target offline address stored in the HashSet that is consistent with the target online address is added to the executor associated with the target application.

[0086] When a new target online address is added to the executor associated with the target application, the process involves adding the target offline address stored in the HashSet that is consistent with the target online address to the same executor. This means that the system will first identify the target online address provided by the user and find out whether there is a corresponding offline address in the hash set. In this way, the system can ensure that while adding new online addresses to the executor, the offline addresses associated with it can be effectively managed and updated. This operation not only helps to keep the addresses in the executor up to date, but also ensures that the relevant offline addresses can be quickly called when switching or rollback is required, thereby improving the flexibility and responsiveness of the system. In addition, this association also facilitates subsequent monitoring and management, allowing the system to operate more efficiently in a dynamically changing environment.

[0087] See also Figure 3 , Figure 3 A method flow chart of another method for managing an XXL distributed task scheduling system provided in an embodiment of the present application can be implemented through steps B1-B5:

[0088] B1: In response to a user importing a scheduled task file through the file batch import interface of the xxljob, the authentication interface performs identity authentication on the user who imports the scheduled task file.

[0089] When a user imports scheduled task files through the file batch import interface of xxljob, xxljob will first call the authentication interface to authenticate the user to ensure that he has sufficient permissions to perform this operation.

[0090] It should be noted that the user needs to fill in the scheduled task file according to the provided Excel template. The scheduled task file conforms to a specific Excel format and contains information about the deployment, maintenance, or update of the target application.

[0091] It should also be noted that the identity authentication method of step B1 is similar to that of step S102, which will not be described in detail here.

[0092] In a possible implementation, the method further includes:

[0093] In response to the Excel template request sent by the user through the template request interface of the xxljob, the authentication interface authenticates the user who sent the Excel template request. If the authentication is successful, the Excel template is exported to the user who sent the Excel template request through the template request interface.

[0094] Specifically, first, the user initiates a request through the template request interface of xxljob to obtain an Excel template. During this process, xxljob will first call the authentication interface to authenticate the user who initiated the request to ensure that they have the corresponding permissions. This step is an important part of ensuring security and preventing unauthorized users from obtaining sensitive information. If the user's authentication is successful, xxljob will continue to process the request and export and send the required Excel template to the user through the template request interface. This process ensures that only verified users can access and download Excel templates, thereby protecting the security of the system and the integrity of the data.

[0095] It should be noted that the identity authentication in this step is similar to the identity authentication in step S102 and will not be described in detail here.

[0096] B2: If the identity authentication is passed, then check whether the format of the scheduled task file is consistent with the format of the Excel template.

[0097] During the import process, once the identity authentication is passed, the system will also check whether the scheduled task file uploaded by the user strictly follows the pre-defined Excel template format. This template usually includes specific column names, data types, and input requirements to ensure that the required information is collected and processed accurately. For example, the template may stipulate that a column must contain the task name, and another column must contain key information such as execution time. This step is an important step to ensure the correctness of the data format. If the file format is consistent, xxljob will read the scheduled task file line by line and convert the data of each line into the corresponding entity class object.

[0098] B3: If they are consistent, convert the scheduled task file into entity class objects line by line.

[0099] If the uploaded scheduled task file meets these format requirements, xxljob will read the data in the file line by line. Each line represents the specific information of a scheduled task, and xxljob will generate a corresponding entity class object based on the data in this line. Entity class objects are a structured data representation that usually contains all the properties related to the scheduled task, such as task name, start time, frequency, etc. This conversion process enables the data originally stored in Excel in text form to be programmatically processed and managed, facilitating subsequent configuration, execution, and monitoring.

[0100] Therefore, format consistency is not only a necessary step to ensure data correctness, but also an important basis for achieving automated management and optimizing scheduled task processing processes.

[0101] B4: Generate corresponding scheduled task configuration parameters according to the entity class object.

[0102] "Generate corresponding scheduled task configuration parameters according to the entity class object" means that xxljob will use the entity class object converted from the scheduled task file to create specific configuration parameters, which will be used to execute and schedule tasks in the scheduled task management system. Each entity class object contains detailed information about the scheduled task, such as task name, execution time, frequency, target application, etc. After this information is extracted, the system maps it to a predefined configuration parameter structure to form a format that can be understood and executed by the system.

[0103] Specifically, the process of generating configuration parameters includes parsing the various attributes in the entity class object and converting them into the parameter format required by the system. For example, the task name may be directly used as a field in the configuration parameters, while the execution time needs to be converted into a time format recognizable by the system. In addition, the frequency parameter may need further processing to ensure that it meets the requirements of the task scheduling mechanism. This process ensures the consistency and accuracy of the data, so that the scheduled tasks can be automatically executed according to the expected settings.

[0104] In this way, xxljob can effectively convert the task information provided by the user into specific execution instructions to ensure that the task proceeds as planned.

[0105] B5: Importing the scheduled task configuration parameters in batches into the scheduled task management system.

[0106] "Importing the scheduled task configuration parameters in batches into the scheduled task management system" means that through the xxljob framework, users can upload and create the configuration parameters of multiple scheduled tasks into the management system at one time. This process allows users to import multiple task settings in one operation without having to add them manually one by one, which significantly improves efficiency.

[0107] Based on the content of B1-B5, it can be seen that by importing multiple scheduled tasks at one time, the time for manual addition is significantly reduced, and the speed of production is improved. At the same time, manual operation is prone to errors, and batch import uses pre-defined Excel templates for format verification to reduce the occurrence of human errors. In addition, using a unified Excel template to ensure that the format of all scheduled tasks is consistent, which helps maintenance and management and reduces problems caused by inconsistencies.

[0108] Based on the contents of S101-S104, it can be known that xxljob controls tasks through the address offline interface and the address online interface, and ensures security in combination with the JWT interceptor and the authentication interface. Users can send offline requests through the address offline interface and specify the target offline address, which is usually a URL and is determined by the user when the target application is updated or fails. The request is first intercepted by the JWT interceptor, and the authentication interface verifies the user's identity. If the verification is successful, the JWT interceptor will release the request. Subsequently, in the executor associated with the target application, the system will delete the target offline address specified in the request, thereby achieving effective management and maintenance of tasks. This application implements automatic processing of address offline requests through the address offline interface, the JWT interceptor, and the authentication interface, reducing the need for manual operations and improving efficiency. The identity authentication mechanism ensures that only authorized users can send offline requests, enhancing the security of xxljob.

[0109] See also Figure 4 , Figure 4 A schematic diagram of the structure of xxljob provided in the embodiment of the present application. Figure 4 As shown, the xxljob includes:

[0110] The JWT interceptor 401 is responsive to an address offline request sent by a user through the address offline interface, and is used to intercept the address offline request in the address offline interface; the address offline request includes a target offline address; the target offline address is determined by the user when the target application is updated or fails; the target offline address is in the form of a unified URL;

[0111] Authentication interface 402, used to authenticate the user who sent the address offline request;

[0112] If the identity authentication is passed, the JWT interceptor 401 is also used to release the address offline request in the address offline interface;

[0113] The address deleting unit 403 is configured to delete, in an executor associated with the target application, a target offline address included in the address offline request in the released address offline interface.

[0114] In a possible implementation, the xxljob further includes: an address online interface and an address adding unit;

[0115] In response to an address online request sent by a user through the address online interface, the JWT interceptor is further used to intercept the address online request in the address online interface; the address online request includes a target online address; the target online address is determined by the user when the target application completes the update or the fault disappears; the target online address is in the form of a URL;

[0116] The authentication interface 402 is also used to authenticate the user who sent the address online request;

[0117] If the identity authentication is passed, the JWT interceptor 401 is also used to release the address online request in the address online interface;

[0118] In the executor associated with the target application, the address adding unit is used to add a target online address included in the released address online request.

[0119] In a possible implementation, the xxljob further includes: a verification unit, a conversion unit, a scheduled task configuration parameter generation unit, and a batch import unit;

[0120] In response to the user importing the scheduled task file through the file batch import interface of the xxljob, the authentication interface 402 is also used to authenticate the user who imported the scheduled task file; the scheduled task file is filled in by the user according to the Excel template; the format of the scheduled task file is Excel format; the Excel template includes information for guiding the deployment, maintenance or update of the target application;

[0121] If the identity authentication is passed, the verification unit is used to verify whether the format of the scheduled task file is consistent with the format of the Excel template;

[0122] If they are consistent, the conversion unit is used to convert the scheduled task file into entity class objects line by line;

[0123] The scheduled task configuration parameter generating unit is used to generate corresponding scheduled task configuration parameters according to the entity class object;

[0124] The batch import unit is used to import the scheduled task configuration parameters in batches into the scheduled task management system.

[0125] In a possible implementation, the xxljob further includes: a sending unit;

[0126] In response to the Excel template request sent by the user through the template request interface of the xxljob, the authentication interface 402 is also used to authenticate the user who sent the Excel template request;

[0127] If the identity authentication is passed, the sending unit is used to export the Excel template to the user who sent the Excel template request through the template request interface.

[0128] In a possible implementation, the xxljob further includes: a storage unit;

[0129] The storage unit is used to store the target offline address to be deleted in a hash set HashSet.

[0130] In a possible implementation, the address adding unit is specifically used for:

[0131] When the target online address is newly added in the executor associated with the target application, the target offline address stored in the HashSet that is consistent with the target online address is added to the executor associated with the target application.

[0132] In addition, an embodiment of the present application also provides a management device for an XXL distributed task scheduling system, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the management method for the XXL distributed task scheduling system as described above is implemented.

[0133] In addition, an embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device executes the management method of the XXL distributed task scheduling system as described above.

[0134] The embodiment of the present application provides a xxljob, which first uses the first acquisition unit 301 to obtain mapping data from the ring buffer as the data to be detected, wherein the mapping data is the system call combination information after rule filtering, rule supplementation and formal mapping, and uses the rule filtering unit 302 to filter the data to be detected to obtain the filtered data. The input unit 303 inputs the filtered data into the pre-built abstract syntax tree to obtain the detection result. Then, the extraction unit 304 is used to extract the data associated with the detection result from the mapping data as supplementary data, so that the output data supplement unit 305 can use the supplementary data to supplement the output data of the detection result to obtain the attack behavior output result. The present application is for xxljob with an address offline interface, which can process the address offline request immediately after receiving it, thereby significantly improving the response speed. At the same time, the interface ensures that each specified offline address is effectively executed, reducing the problems that may be caused by human negligence. In addition, the integrated JWT interceptor implements identity authentication to ensure that only authorized users can perform online and offline operations. This not only enhances the security of the system, but also effectively prevents unauthorized access and operation.

[0135] The above is a detailed introduction to the management method and related devices of an XXL distributed task scheduling system provided by the present application. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can be referenced to each other. For the xxljob disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

[0136] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0137] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

Claims

1. A management method for an XXL distributed task scheduling system, characterized in that: Applied to XXL distributed task scheduling system xxljob, the xxljob includes an address offline interface, an address online interface, a JSON network token JWT interceptor and an authentication interface, and the method includes: In response to an address offline request sent by a user through the address offline interface, the JWT interceptor intercepts the address offline request in the address offline interface; the address offline request includes a target offline address; the target offline address is determined by the user when the target application is updated or a fault occurs; the target offline address is determined by the user when the target application completes the update or the fault disappears; the target offline address is in the form of a uniform resource locator URL; The authentication interface authenticates the user who sends the address offline request; If the identity authentication is passed, the JWT interceptor releases the address offline request in the address offline interface; In an executor associated with the target application, a target offline address included in the released address offline request is deleted.

2. The method according to claim 1, characterized in that The method further comprises: In response to an address online request sent by a user through the address online interface, the JWT interceptor intercepts the address online request in the address online interface; the address online request includes a target online address; the target online address is determined by the user when the target application completes the update or the fault disappears; the target online address is in the form of a URL; The authentication interface authenticates the user who sends the address online request; If the identity authentication is passed, the JWT interceptor releases the address online request in the address online interface; In the executor associated with the target application, a target online address included in the released address online request is added.

3. The method according to claim 1, characterized in that The method further comprises: In response to a user importing a scheduled task file through the file batch import interface of the xxljob, the authentication interface authenticates the user who imports the scheduled task file; the scheduled task file is filled in by the user according to the Excel template; the format of the scheduled task file is Excel format; the Excel template includes information for guiding the deployment, maintenance or update of the target application; If the identity authentication is passed, then check whether the format of the scheduled task file is consistent with the format of the Excel template; If they are consistent, convert the scheduled task file into entity class objects line by line; Generate corresponding scheduled task configuration parameters according to the entity class object; Import the scheduled task configuration parameters in batches into the scheduled task management system.

4. The method according to claim 3, characterized in that The method further comprises: In response to the Excel template request sent by the user through the template request interface of the xxljob, the authentication interface authenticates the user who sent the Excel template request; If the identity authentication is passed, the Excel template is exported to the user who sent the Excel template request through the template request interface.

5. The method according to claim 1, characterized in that The method further includes: storing the deleted target offline address in a hash set HashSet.

6. The method according to claim 2, characterized in that The step of adding, in the executor associated with the target application, a target online address included in the address online request that is released, comprises: When the target online address is newly added in the executor associated with the target application, the target offline address stored in the HashSet that is consistent with the target online address is added to the executor associated with the target application.

7. A xxljob, characterized in that: The xxljob includes; A JWT interceptor, in response to an address offline request sent by a user through the address offline interface, is used to intercept the address offline request in the address offline interface; the address offline request includes a target offline address; The target offline address is determined by the user when the target application is updated or fails; the target offline address is in the form of a unified URL; An authentication interface, used to authenticate the identity of the user who sent the offline request for the address; If the identity authentication is passed, the JWT interceptor is also used to release the address offline request in the address offline interface; The address deleting unit is used to delete, in an executor associated with the target application, a target offline address included in the address offline request in the released address offline interface.

8. The xxljob according to claim 7, characterized in that: The xxljob also includes: an address online interface and an address adding unit; In response to an address online request sent by a user through the address online interface, the JWT interceptor is further used to intercept the address online request in the address online interface; the address online request includes a target online address; the target online address is determined by the user when the target application completes the update or the fault disappears; the target online address is in the form of a URL; The authentication interface is also used to authenticate the user who sends the address online request; If the identity authentication is passed, the JWT interceptor is also used to release the address online request in the address online interface; In the executor associated with the target application, the address adding unit is used to add a target online address included in the released address online request.

9. A management device for an XXL distributed task scheduling system, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the management method of the XXL distributed task scheduling system as described in any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on the terminal device, the terminal device executes the management method of the XXL distributed task scheduling system according to any one of claims 1 to 6.

Images