A cluster information management method

By introducing preset grouping attributes, the independence and version management problems of cluster environment configuration and service version management in the big data platform are solved, and the independence of cluster configuration and version management are achieved, ensuring the normal execution of big data platform tasks is ensured. and system stability.

CN118656122BActive Publication Date: 2024-11-05CHENGDU CELIS TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411154718.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-22
Publication Date
2024-11-05
Estimated Expiration
2044-08-22

AI Technical Summary

Technical Problem

The cluster environment configuration and cluster service version of the existing big data platform lack heterogeneous configuration selection, resulting in configuration modifications that may affect all cluster nodes, resulting in task failure, unable to effectively manage multiple heterogeneous configurations, and improper version management leads to unpredictable errors and Iterating version is difficult.

Method used

By introducing preset grouping attributes, the cluster environment configurations are independent of each other and do not affect each other, and authorized distribution and grayscale upgrade of the cluster service version are carried out according to different users, ensuring the normal execution of big data platform tasks. The specific method includes receiving user operation requests, determining the grouping results related to preset grouping attributes, and performing corresponding operations, such as modifying cluster environment configuration items or service version query, and using properties such as executor group and version merging to achieve configuration isolation and version management. .

Benefits of technology

It realizes the independence of cluster environment configuration, avoids configuration modification errors affecting other cluster tasks, ensures the normal execution of big data platform tasks, and optimizes cluster service version management through grayscale upgrades and authorized distribution, improving the stability and reliability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118656122B_ABST
    Figure CN118656122B_ABST
Patent Text Reader

Abstract

The present application provides a cluster information management method, including: receiving an operation request sent by a user for cluster-related information, if the cluster-related information includes cluster environment configuration, the operation request includes a modification request for cluster environment configuration items, if the cluster-related information includes cluster service version, the operation request includes a cluster service version query request or a cluster service version online request; responding to the operation request, determining a grouping result related to a preset grouping attribute; performing corresponding operations on the grouping result. The technical solution of the embodiment of the present application can make cluster environment configurations independent of each other and not affect each other, and can also authorize and distribute cluster service versions and perform grayscale upgrades according to different users, ultimately ensuring that the big data platform can perform tasks normally.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of automobile battery protection, and in particular to a cluster information management method. Background Art

[0002] The big data platform and the corresponding big data cluster environment configuration are matched one by one, which is a strong binding mode. For example, a big data platform in a production environment has a matching production environment big data cluster environment configuration. This configuration is the only configuration that all cluster slave nodes are bound to when the big data platform is deployed. The big data platform also manages multiple cluster service versions, where cluster services include computing engines and programming language services. Cluster service versions include Spark2.4, Spark3.2, Flink1.12, Flink1.14, Java8, Java17, Python2.7, Python3.7, etc. Generally, multiple versions of computing engines and programming language services are equally open to all users, that is, all users can see all versions of computing engines and programming language services of the big data platform.

[0003] In the prior art, cluster-related information such as the cluster environment configuration and cluster service version of the big data platform lacks heterogeneous configuration options, which may result in the cluster environment configuration being modified and taking effect on all cluster nodes and tasks of the big data platform, which may cause certain tasks to fail to execute, resulting in online failures; in addition, the big data platform is unable to manage multiple big data clusters with heterogeneous configurations, and unpredictable errors may occur after the cluster service version is used incorrectly, and version iteration and upgrade are not targeted. Too many versions make it impossible for users to determine which version to use, causing trouble for users, and ultimately leading to the problem that the big data platform tasks cannot be executed normally.

[0004] In view of this, the present invention is proposed. Summary of the invention

[0005] In view of the above-mentioned defects or deficiencies in the prior art, the present application aims to provide a cluster information management method, which makes the cluster environment configurations independent of each other and do not affect each other by adding preset grouping attributes. Even if the configuration of any cluster is modified incorrectly, it will not affect the normal execution of tasks of other clusters of the same type. In addition, by adding preset grouping attributes, the cluster service version can be authorized and distributed and grayscale upgraded according to different users, ultimately ensuring that the big data platform can perform tasks normally.

[0006] In a first aspect, an embodiment of the present application provides a cluster information management method, including:

[0007] Receive an operation request sent by a user for cluster related information, if the cluster related information includes cluster environment configuration, the operation request includes a modification request for a cluster environment configuration item, if the cluster related information includes a cluster service version, the operation request includes a cluster service version query request or a cluster service version online request;

[0008] In response to the operation request, determine a grouping result related to a preset grouping attribute;

[0009] Perform corresponding operations on the grouping results.

[0010] According to the technical solution provided by the embodiment of the present application, the cluster-related information includes cluster environment configuration, the operation request includes a request to modify the cluster environment configuration item, and the preset grouping attribute includes an actuator group; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes:

[0011] Determine whether an executor group corresponding to the cluster environment configuration item exists, the executor group includes one or more executors, wherein the executor is the executor corresponding to the cluster environment configuration item;

[0012] If it exists, the executor corresponding to the cluster environment configuration item is assigned to the executor group, and correspondingly, corresponding operations are performed on the grouping result, including: based on the environment configuration storage path, modifying the cluster environment configuration item for each executor in the executor group, wherein the environment configuration storage path is stored in a one-to-one correspondence with the executor group, and the environment configuration storage path is used to indicate the storage location of the cluster environment configuration item in the corresponding executor.

[0013] According to the technical solution provided in the embodiment of the present application, after performing a modification operation on the cluster environment configuration item on each executor in the executor group, if the environment configuration storage path has changed, performing a corresponding operation on the grouping result, further comprising:

[0014] Modify the environment configuration storage path.

[0015] According to the technical solution provided by the embodiment of the present application, after determining whether the executor group corresponding to the cluster environment configuration item exists, the method further includes:

[0016] If it does not exist, a new executor group is created, and executors with the same cluster environment configuration items are assigned to the executor group, and the environment configuration storage path corresponding to the executor group is determined.

[0017] According to the technical solution provided in the embodiment of the present application, before performing a modification operation on the cluster environment configuration item on each executor in the executor group, the method further includes:

[0018] Determine whether there is an irrelevant executor in the executor group, wherein the irrelevant executor is an executor that does not require cluster environment configuration item modification;

[0019] If it exists, the irrelevant executor is removed, a new irrelevant executor group is created, the irrelevant executor is assigned to the irrelevant executor group, and the executor group after removing the irrelevant executor is used as the new executor group.

[0020] According to the technical solution provided in the embodiment of the present application, after performing corresponding operations on the grouping results, the method further includes:

[0021] Execute corresponding tasks based on the modified cluster environment configuration;

[0022] If the execution result is as expected, the modification operation is completed;

[0023] If the execution result does not meet expectations, the steps of determining the grouping result related to the preset grouping attribute and performing corresponding operations on the grouping result are repeated until the execution result meets expectations.

[0024] According to the technical solution provided in the embodiment of the present application, the cluster-related information includes a cluster service version, the operation request includes a service version query request, and the preset grouping attributes include version merging, cluster, department, and service version switch; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes:

[0025] Determine the query condition based on the operation request, wherein the operation request includes at least one of a service type, a cluster value, and a department value, wherein the service type includes a specified service type or a full service type, the cluster value includes a specified cluster or a default, and the department value includes a specified department or a default;

[0026] Based on the query conditions, the preset version coverage priority and the service version switch value, the service version grouping result with the preset grouping attribute is determined. The preset version coverage priority is that if the version merge values ​​corresponding to the version merge are the same, the department value coverage priority is higher than the cluster value coverage priority, and the cluster value coverage priority is higher than the default coverage priority. Among them, cluster service versions belonging to the same service type and the same service basic functions have the same version merge value.

[0027] According to the technical solution provided in the embodiment of the present application, based on the query condition, the preset version coverage priority and the service version switch value, determining the service version grouping result with the preset grouping attribute includes:

[0028] If the service type, cluster value, and department value are not specified in the operation request, the query conditions are that the service type is all service types and the cluster value is default and the department value is default;

[0029] If the service type and department value are not specified in the operation request, but the cluster value is specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, department value is the default or all departments under the specified cluster, and service type is all service types, cluster value is the default, and department value is the default;

[0030] If the service type is not specified in the operation request, but the cluster value and department value are specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, and department value is the specified department value; service type is all service types, cluster value is the specified cluster value, and department value is the default; and service type is all service types, cluster value is the default, and department value is the default;

[0031] If the service type is specified in the operation request, but the cluster value and department value are not specified, the query condition is that the service type is the specified service type and the cluster value is the default and the department value is the default;

[0032] If the service type and cluster value are specified in the operation request, but the department value is not specified, the query conditions are: service type is the specified service type, cluster value is the specified cluster value, and department value is the default or all departments under the specified cluster, and service type is the specified service type, cluster value is the default, and department value is the default;

[0033] If the service type, cluster value, and department value are specified in the operation request, the query conditions are: the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the specified department value; the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the default; and the service type is the specified service type, the cluster value is the default, and the department value is the default.

[0034] According to the technical solution provided in the embodiment of the present application, based on the query condition, the preset version coverage priority and the service version switch value, determining the service version grouping result with the preset grouping attribute includes:

[0035] After the initial service version grouping result is queried using the query condition, the grouping result with the service version value of closed in the initial service version grouping result is removed to obtain the pre-processed service version grouping result;

[0036] In the pre-processing service version grouping results, if there is a version merge grouping result with the same version merge value, determine whether there is a first sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a specified department value. If so, retain the first sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the first sub-grouping result. If not, determine whether there is a second sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a default. If so, retain the second sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the second sub-grouping result. If not, retain the version merge grouping result to finally obtain the service version grouping result.

[0037] According to the technical solution provided in the embodiment of the present application, the cluster related information includes the cluster service version, the operation request includes the service version online request, and the preset grouping attributes include version merging, cluster, department, and service version switch; accordingly, in response to the operation request, determining the grouping result related to the preset grouping attribute includes:

[0038] According to the operation request, a grouping result with preset grouping attributes is generated, wherein the version merge value is the service basic function version corresponding to the corresponding service type, the cluster value is the specified cluster value, the department value is the specified department value, and the service version switch is in the on state.

[0039] In summary, the present application proposes a cluster information management method, including: receiving an operation request sent by a user for cluster-related information, if the cluster-related information includes a cluster environment configuration, then the operation request includes a modification request for a cluster environment configuration item, if the cluster-related information includes a cluster service version, then the operation request includes a cluster service version query request or a cluster service version online request; responding to the operation request, determining a grouping result related to a preset grouping attribute; performing corresponding operations on the grouping result. By adding corresponding preset grouping attributes to the cluster environment configuration, the cluster environment configurations are independent of each other and do not affect each other. Even if the configuration modification of any cluster is wrong, it will not affect the normal execution of tasks of other clusters of the same type. In addition, by adding corresponding preset grouping attributes to the cluster service version, the cluster service version can be authorized and distributed according to different users, and gray-scale upgrades can be performed, etc., ultimately ensuring that the big data platform can perform tasks normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 A schematic diagram of a cluster information management method provided in an embodiment of the present application;

[0041] Figure 2 A schematic diagram of a process flow of modifying a cluster environment configuration provided in an embodiment of the present application;

[0042] Figure 3 A schematic diagram of a process flow of querying a cluster service version provided in an embodiment of the present application;

[0043] Figure 4 A schematic diagram of the structure of a cluster information management device provided in an embodiment of the present application;

[0044] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It is also necessary to explain that, for ease of description, only the parts related to the invention are shown in the accompanying drawings.

[0046] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0047] As mentioned in the background technology, in response to the problems in the prior art, the present application proposes a cluster information management method. This embodiment can be applied to situations where it is necessary to modify the cluster environment configuration or to authorize the distribution of the cluster service version and to perform a grayscale upgrade of the new version. The method can be executed by a cluster information management device, which can be implemented in software and / or hardware and can be configured in an electronic device. Figure 1 A flow chart of a cluster information management method provided in an embodiment of the present application is shown as follows: Figure 1 As shown, the method comprises the following steps:

[0048] S110. Receive an operation request sent by a user for cluster related information. If the cluster related information includes cluster environment configuration, the operation request includes a request to modify a cluster environment configuration item. If the cluster related information includes a cluster service version, the operation request includes a cluster service version query request or a cluster service version online request.

[0049] Among them, the cluster environment configuration is the environment configuration parameters and configuration files required for the normal operation of the cluster. The cluster environment configuration may include various cluster environment configuration items. In actual applications, users may need to modify different cluster environment configuration items according to different needs. The modification includes modification methods such as adding, replacing the whole or updating the part. Preferably, the user can send a modification request for the cluster environment configuration item to modify the cluster environment configuration item. The cluster service version may include various versions of the computing engine type and various versions of the programming language service type in the cluster. In actual applications, users may also need to use different versions of the computing engine type and different versions of the programming language service type. Preferably, the user can send a query request for the cluster service version to obtain the cluster service version that he has the right to use; when the user has the need to launch the cluster service version, he can also send an online request for the cluster service version to launch the cluster service version.

[0050] S120: In response to the operation request, determine a grouping result related to a preset grouping attribute.

[0051] In this embodiment, the cluster environment configuration of the big data platform is associated with the big data platform executor for management, so the essence of managing the cluster environment configuration of the big data platform is to manage the executor of the big data platform. Preferably, for the executor corresponding to the cluster environment configuration, a preset grouping attribute can be added as an executor group. An executor must belong to an executor group. An executor group can contain multiple executors. The executor group is a logical concept that describes executors with the same environment configuration items. Cluster environment configuration isolation can be achieved based on the executor group. Exemplarily, if the operation request is a modification request for the cluster environment configuration item, the grouping result related to the preset grouping attribute may include the grouping result of the executor group attribute corresponding to the cluster environment configuration item, wherein the grouping result can preferably be presented in the form of a database table, and the grouping result may include executor group identity identification number, each executor identity identification number, and cluster environment configuration storage path and other related information, wherein the cluster environment configuration storage path is stored in a one-to-one correspondence with the executor group, and the environment configuration storage path is used to indicate the storage location of the cluster environment configuration item in the corresponding executor.

[0052] Preferably, for the cluster service version, the preset grouping attributes such as version merge, cluster, department and service version switch can be added, wherein the version merge is the basic function version merge of the same service type, and the same version merge value can correspond to multiple different function optimization version values. For example, the same version merge value is Spark3.2, which can correspond to different function optimization version values ​​such as Spark3.2.2 and Spark3.2.3. The cluster is the cluster to which the user belongs, and the part is the department to which the user belongs. The service version switch indicates whether the corresponding service version is in the on state or the off state, wherein the on state indicates that the user can use it, and the off state indicates that the user cannot use it. For example, the operation request is a query request for the service type Spark version, and the grouping results related to the preset grouping attributes may include grouping results with attributes such as version merge, cluster, department and service version switch, wherein the grouping results may preferably be presented in the form of a database table, and the grouping results may include version merge, service type, service version (the service version value is the service function optimization version value, such as Spark3.2.2 and Spark3.2.3, etc.), cluster, department and service version switch and other related information. It is understandable that when adding preset grouping attributes such as version merge, cluster, department and service version switch, the system can give priority to authorization and distribution operations of different cluster service versions to different users based on the preset grouping attributes, so that users can determine the grouping results related to the preset grouping attributes based on responding to operation requests.

[0053] S130: Perform corresponding operations on the grouping results.

[0054] Exemplarily, if the cluster-related information includes cluster environment configuration, and the operation request includes a modification request for cluster environment configuration items, then after obtaining the grouping result, performing a corresponding operation on the grouping result may include modifying the cluster environment configuration items in the grouping result. Also exemplarily, if the cluster-related information includes a cluster service version, and the operation request includes a cluster service version query request or a cluster service version online request, then after obtaining the grouping result, performing a corresponding operation on the grouping result may include displaying the grouping result.

[0055] The cluster information management method provided in this embodiment includes: receiving an operation request sent by a user for cluster-related information, if the cluster-related information includes cluster environment configuration, then the operation request includes a modification request for cluster environment configuration items, if the cluster-related information includes cluster service version, then the operation request includes a cluster service version query request or a cluster service version online request; responding to the operation request, determining a grouping result related to a preset grouping attribute; performing corresponding operations on the grouping result. By adding corresponding preset grouping attributes to the cluster environment configuration, the cluster environment configurations are independent of each other and do not affect each other. Even if the configuration modification of any cluster is wrong, it will not affect the normal execution of tasks of other clusters of the same type. In addition, by adding corresponding preset grouping attributes to the cluster service version, the cluster service version can be authorized and distributed and gray-scale upgraded according to different users, ultimately ensuring that the big data platform can perform tasks normally.

[0056] On the basis of the above embodiments, further, the cluster-related information includes cluster environment configuration, the operation request includes a request to modify a cluster environment configuration item, and the preset grouping attribute includes an actuator group; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes:

[0057] Determine whether an executor group corresponding to the cluster environment configuration item exists, the executor group includes one or more executors, wherein the executor is the executor corresponding to the cluster environment configuration item;

[0058] If it exists, the executor corresponding to the cluster environment configuration item is assigned to the executor group, and correspondingly, corresponding operations are performed on the grouping result, including: based on the environment configuration storage path, modifying the cluster environment configuration item for each executor in the executor group, wherein the environment configuration storage path is stored in a one-to-one correspondence with the executor group, and the environment configuration storage path is used to indicate the storage location of the cluster environment configuration item in the corresponding executor.

[0059] Table 1 is a storage table of executor-related data in the existing big data platform. See Table 1. Executor ID (Identity document) is the executor identification number, executor IP (Internet Protocol) is the Internet Protocol of the executor, and the environment configuration stores the actual environment configuration content of the corresponding executor (this storage method wastes storage space). The existing big data cluster environment configuration is configured in each executor, and the value of the environment configuration is the actual configuration item, which is equivalent to the state that the environment configuration is bound to the executor. The problems existing in the existing technology may include: (1) When it is necessary to modify the same environment configuration of certain executors, multiple lines of content need to be modified at one time. If the configuration items are modified incorrectly or omitted, the same task execution may succeed in some executors and fail in others; (2) The same environment configuration items are stored in multiple copies, which will lead to a waste of storage space.

[0060] Table 1

[0061]

[0062] Table 2 is a storage table of executor-related data provided by this embodiment. Referring to Table 2, each row of data adds a preset grouping attribute executor group Id, which is used to divide executors with the same cluster environment configuration items into an executor group. When the cluster environment configuration items need to be modified, only the environment configuration items in the executor group need to be modified, and the environment configurations of all executors associated with this executor group can be modified synchronously, so as to achieve consistency in the modification of the same cluster environment configuration items.

[0063] Table 2

[0064]

[0065] Table 3 is a storage table of the executor group related data provided in this embodiment. See Table 3. This table is used to describe the metadata of the executor group. The environment configuration items in the existing executor table are replaced with the environment configuration storage path to describe the actual storage path of the cluster environment configuration. This method does not need to store the actual values ​​of the cluster environment configuration items, reduces the redundant storage of configuration items, and saves storage space. If you want to modify the cluster environment configuration, you can modify the configuration file under the corresponding executor according to the environment configuration storage path. This can achieve overall replacement or partial update of the configuration. For example, modifying the configuration of type A cluster group 1 will not have any impact on type A cluster group 2. Even if type A cluster group 1 crashes due to misoperation, its scope of influence is only type A cluster group 1. The actual cluster environment configuration items can also be hidden in the executor to achieve safe storage of cluster environment configuration items.

[0066] Table 3

[0067]

[0068] Taking Table 3 as an example, the specific execution process of this embodiment is explained. For example, if the cluster environment configuration item existing in the path / etc / hadoop-001 / core-site.xml needs to be modified, it is determined whether the executor group corresponding to the cluster environment configuration item exists. After querying, it can be determined that the executor group ID corresponding to the cluster environment configuration item is 10. Based on the environment configuration storage path / etc / hadoop-001 / core-site.xml, the cluster environment configuration item is modified for executors 0001 and 0002 under the executor group respectively.

[0069] On the basis of the above embodiments, further, after performing a modification operation on the cluster environment configuration item on each executor in the executor group, if the environment configuration storage path is changed, performing a corresponding operation on the grouping result, further comprising:

[0070] The environment configuration storage path is modified.

[0071] The above technical solution can ensure the uniformity of the executor group and the corresponding executor environment configuration by modifying the environment configuration storage path, and ensure that the big data platform can execute tasks normally.

[0072] For example, to add a new / etc / hadoop-008 / core-site.xml configuration under executor A, you can determine whether the executor group to which executor A wants to belong corresponding to the configuration exists. If it is determined to exist, executor A will be assigned to the executor group, and a new / etc / hadoop-008 / core-site.xml configuration is added under executor A. If the environment configuration storage path corresponding to the executor group exists, there is no need to modify the environment configuration storage path. If the environment configuration storage path corresponding to the executor group does not exist, the environment configuration storage path needs to be modified.

[0073] On the basis of the above embodiments, further, after determining whether the executor group corresponding to the cluster environment configuration item exists, the method further includes:

[0074] If it does not exist, then a new executor group is created, and executors with the same cluster environment configuration items are assigned to the executor group, and the environment configuration storage path corresponding to the executor group is determined. By creating a new executor group, executors with the same cluster environment configuration items can be grouped together, so that the cluster environment configurations are independent of each other and do not affect each other. Even if the configuration of any cluster is modified incorrectly, it will not affect the normal execution of tasks in other clusters of the same type.

[0075] On the basis of the above embodiments, further, before performing the cluster environment configuration item modification operation on each executor in the executor group, the method further includes:

[0076] Determine whether there is an irrelevant executor in the executor group, wherein the irrelevant executor is an executor that does not require cluster environment configuration item modification;

[0077] If it exists, the irrelevant executor is removed, a new irrelevant executor group is created, the irrelevant executor is assigned to the irrelevant executor group, and the executor group after removing the irrelevant executor is used as the new executor group.

[0078] Even in the same executor group, there may still be some irrelevant executors that do not need to modify the cluster environment configuration items. Based on this, the irrelevant executors can be removed from the executor group so that the executor group after removing the irrelevant executors meets the requirements of cluster environment configuration item modification.

[0079] On the basis of the above embodiments, further, after performing corresponding operations on the grouping results, the method further includes:

[0080] Execute corresponding tasks based on the modified cluster environment configuration;

[0081] If the execution result is as expected, the modification operation is completed;

[0082] If the execution result does not meet expectations, the steps of determining the grouping result related to the preset grouping attribute and performing corresponding operations on the grouping result are repeated until the execution result meets expectations.

[0083] In some cases, the cluster environment configuration item modification implemented by adding a preset grouping attribute executor group may not produce the expected cluster environment configuration for task execution. In this case, there may be deviations in the cluster environment configuration item modification process. Therefore, the cluster environment configuration item modification process can be fine-tuned by repeatedly determining the grouping results related to the preset grouping attributes and performing corresponding operations on the grouping results to obtain a cluster environment configuration that can make the execution results meet expectations.

[0084] Figure 2 A flow chart of a cluster environment configuration modification process provided in an embodiment of the present application is shown in FIG. Figure 2When the cluster environment configuration item needs to be modified, determine whether the executor group corresponding to the cluster environment configuration item exists. If so, assign the executor corresponding to the cluster environment configuration item to the executor group. If not, create a new executor group and modify the corresponding cluster environment configuration item. Determine whether the environment configuration storage path corresponding to the executor group needs to be modified. If so, modify it. If not, execute the corresponding task based on the modified cluster environment configuration item and determine whether the execution result meets expectations. If so, complete the modification operation. If not, repeat the above steps until the execution result meets expectations.

[0085] On the basis of the above embodiments, further, the cluster related information includes a cluster service version, the operation request includes a service version query request, and the preset grouping attributes include version merge, cluster, department, and service version switch; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes:

[0086] Determine the query condition based on the operation request, wherein the operation request includes at least one of a service type, a cluster value, and a department value, wherein the service type includes a specified service type or a full service type, the cluster value includes a specified cluster or a default, and the department value includes a specified department or a default;

[0087] Based on the query conditions, the preset version coverage priority and the service version switch value, the service version grouping result with the preset grouping attribute is determined. The preset version coverage priority is that if the version merge values ​​corresponding to the version merge are the same, the department value coverage priority is higher than the cluster value coverage priority, and the cluster value coverage priority is higher than the default coverage priority. Among them, cluster service versions belonging to the same service type and the same service basic functions have the same version merge value.

[0088] Table 4 is a storage table for cluster service version-related data in the existing big data platform. As shown in Table 4, the data structure has no hierarchical relationship and is a flat structure. The table lists the computing engine service versions and programming language service versions that the big data platform can support. All users of the big data platform can see and have the right to use the cluster service versions in Table 4. The problems brought by the existing technical solutions include: (1) For example, if a user is proficient in using Flink 1.12, but Flink opens Flink 1.14 and Flink 1.20 to all users, it may cause the wrong version to be selected due to misoperation or unnecessary trouble due to mixed use of versions. (2) For example, the real-time computing department only uses Flink and Java cluster service versions; the offline computing department only uses Spark cluster service versions. At this time, both departments can see and have the right to use the cluster service versions used by the other department, and effective isolation of cluster service versions cannot be achieved. (3) The cluster service version is constantly iterating, and it is impossible to implement the grayscale launch of the version. For example, when launching Spark 3.5.1, it is currently impossible to support the requirement that only certain departments can see the latest version of Spark 3.5.1.

[0089] Table 4

[0090]

[0091] Table 5 is a storage table for cluster service version related data provided in this embodiment. Referring to Table 5, each row of data has a new preset grouping attribute version merge, and a logical switch field is added to the three dimension fields of cluster and department. Among them, version merge is to merge cluster service versions of the same service type and the same basic service functions. For example, Department A has two cluster service versions of Spark3.2 (basic function version) on Cluster A, namely Spark3.2.2 (performance optimization version) and Spark3.2.4 (performance optimization version). According to the merge strategy, the corresponding version merge value of Department A on Cluster A is Spark3.2. The version merge value is generally the upper level version of the performance optimization version. It can meet the needs of different departments to use different performance optimization versions for the same version merge value. A cluster can contain multiple departments. If the department is not specially set under the cluster, the department value of the cluster is the default, which means that any user can obtain and have the right to use the cluster service version under the cluster. For example, the cluster service versions corresponding to cluster A include Spark3.2.2, Flink1.14, and Java17 (the result of merging the two cases where the cluster value is cluster A and the cluster value is default). Cluster A includes departments A, B, and C. When the department value is default, the obtained cluster service versions include all cluster service versions corresponding to cluster A, which are Spark3.2.2, Flink1.14, and Java17. That is, no matter which department the user belongs to, the cluster service versions obtained are Spark3.2.2, Flink1.14, and Java17. Department is the smallest dimension for cluster and cluster service version management, and also has the highest version coverage priority. For example, for the version merge value Spark3.2, there are two cluster service versions corresponding to cluster A, namely Spark3.2.2 and Spark3.2.4. Among them, the department value corresponding to Spark3.2.2 is default, and the department value corresponding to Spark3.2.4 is Department A. The department value override priority corresponding to park3.2.4 is higher than the default override priority corresponding to Spark3.2.2. Therefore, the Spark3.2 version of cluster A obtained by Department A is Spark3.2.4.

[0092] Table 5

[0093]

[0094] On the basis of the above embodiments, further, based on the query condition, the preset version coverage priority and the service version switch value, determining the service version grouping result with the preset grouping attribute includes:

[0095] If the service type, cluster value, and department value are not specified in the operation request, the query conditions are that the service type is all service types and the cluster value is default and the department value is default;

[0096] If the service type and department value are not specified in the operation request, but the cluster value is specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, department value is the default or all departments under the specified cluster, and service type is all service types, cluster value is the default, and department value is the default;

[0097] If the service type is not specified in the operation request, but the cluster value and department value are specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, and department value is the specified department value; service type is all service types, cluster value is the specified cluster value, and department value is the default; and service type is all service types, cluster value is the default, and department value is the default;

[0098] If the service type is specified in the operation request, but the cluster value and department value are not specified, the query condition is that the service type is the specified service type and the cluster value is the default and the department value is the default;

[0099] If the service type and cluster value are specified in the operation request, but the department value is not specified, the query conditions are: service type is the specified service type, cluster value is the specified cluster value, and department value is the default or all departments under the specified cluster, and service type is the specified service type, cluster value is the default, and department value is the default;

[0100] If the service type, cluster value, and department value are specified in the operation request, the query conditions are: the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the specified department value; the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the default; and the service type is the specified service type, the cluster value is the default, and the department value is the default.

[0101] The above technical solution determines different query conditions according to different operation requests, and fully considers the situation where cluster values ​​and department values ​​are default, so that users can more accurately find the cluster service version for which they have permissions.

[0102] On the basis of the above embodiments, further, based on the query condition, the preset version coverage priority and the service version switch value, determining the service version grouping result with the preset grouping attribute includes:

[0103] After the initial service version grouping result is queried using the query condition, the grouping result with the service version value of closed in the initial service version grouping result is removed to obtain the pre-processed service version grouping result;

[0104] In the pre-processing service version grouping results, if there is a version merge grouping result with the same version merge value, determine whether there is a first sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a specified department value. If so, retain the first sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the first sub-grouping result. If not, determine whether there is a second sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a default. If so, retain the second sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the second sub-grouping result. If not, retain the version merge grouping result to finally obtain the service version grouping result.

[0105] The above version merging principle can help users eliminate some unnecessary cluster service versions, avoiding the problem of task execution failure due to users making wrong selections or using incorrect versions due to too many cluster service versions.

[0106] The above process is described in detail below for several typical query conditions.

[0107] For example, if the user is a guest and has no cluster name and department, the corresponding query condition is cluster=default&department=default. The query result is shown in Table 6. The user can use two cluster service versions, Spark 3.2.2 and Flink 1.14.0.

[0108] Table 6

[0109]

[0110] As another example, the user is a user under cluster B, and he wants to query which cluster service versions he can use under cluster B. The corresponding query conditions are cluster = cluster B, department value = default or all departments under cluster B (whether it is default or any department under cluster B (such as department A or department B), the user has the right to use it), and cluster = default & department = default, and then the two query results are taken as a union. The obtained union is shown in Table 7. Referring to Table 7, there are two query results whose version merge values ​​are the same, namely Flink1.14. At this time, according to the version coverage priority principle, the cluster service versions with lower version coverage priorities can be eliminated. Specifically, the version coverage priority of cluster B is higher than the version coverage priority of the default cluster, so the version of Flink1.14.0 can be eliminated. Finally, it is found that the versions that the user can use include Spark3.2.2, Spark2.4.4, Flink1.12.0 and Flink1.14.3.

[0111] Table 7

[0112]

[0113] Exemplarily, the user is a user of department A under cluster A, and the corresponding query conditions include cluster=default&department=default, cluster=clusterA&department=default and cluster=clusterA&department=departmentA, and then the three query results are taken as a union. The obtained union is shown in Table 8. Referring to Table 8, first delete the query grouping results with the service version switch turned off, that is, Java1.17.0. If the version merge is the same, the coverage priority of cluster=clusterA&department=departmentA is higher than the coverage priority of cluster=clusterA&department=default, and the coverage priority of cluster=clusterA&department=default is higher than cluster=default&department=default. It should be noted that there are two query grouping results corresponding to the version merge value Spark3.2, but the version coverage priority of the department value being department A is greater than the version coverage priority of the department value being default, so the cluster service version with the department value being default, that is, Spark3.2.2, is eliminated. There are also two query grouping results corresponding to the version merge value Flink1.12, but the version override priority of the department value Department A is higher than the default version override priority of the department value, so the default cluster service version of the department value, that is, Flink1.12.0, is eliminated. Finally, the available versions for this user are Spark2.4.4, Spark3.2.4, Flink1.2.2, Flink1.14.0, Java1.8.0, Python2.7.6, and Python3.7.14.

[0114] Table 8

[0115]

[0116] On the basis of the above embodiments, further, the cluster related information includes a cluster service version, the operation request includes a service version online request, and the preset grouping attributes include version merging, cluster, department, and service version switch; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes:

[0117] According to the operation request, a grouping result with preset grouping attributes is generated, wherein the version merge value is the service basic function version corresponding to the corresponding service type, the cluster value is the specified cluster value, the department value is the specified department value, and the service version switch is in the on state.

[0118] For example, if the user of department D in cluster B wants to launch Spark 3.4.2 of Spark 3.4, he only needs to insert a data shown in Table 9 into the storage table and set the service version switch to the on state. The added new version is only visible to the user of department D in cluster B, and the grayscale launch of the new version is realized. If the version is verified by department D later, both the cluster value and the department value can be changed to the default value so that all users have the right to use it.

[0119] Table 9

[0120]

[0121] Figure 3 A flow chart of a cluster service version query process provided in an embodiment of the present application is shown in FIG. Figure 3 , according to the operation request, determine whether the user specifies the service type of the cluster service version. If the service type is specified, determine that the service type in the query condition is the specified service type. If the service type is not specified, determine that the query condition includes the service type as the full service type. Continue to determine whether the user specifies the cluster value. If the cluster value is specified, determine that the query condition includes the cluster value as the specified cluster value or the default. If the cluster value is not specified, determine that the query condition includes the cluster value as the default and the department value as the default. Continue to determine whether the user specifies the department value. If the department value is specified, determine that the query condition includes the department value as the specified department value or the default. If the department value is not specified, determine that the query condition includes the department value as the default or all departments under the specified cluster. Perform group query on the cluster service version according to the query condition finally determined. After taking the union of the query results, eliminate the cluster service versions that do not meet the conditions according to the version coverage priority principle, and display the final query group results to the user.

[0122] Figure 4 A schematic diagram of the structure of a cluster information management device provided in an embodiment of the present application, wherein the device is arranged in an electronic device, such as Figure 4 As shown, the device comprises:

[0123] An operation request receiving module 410 is used to receive an operation request sent by a user for cluster related information. If the cluster related information includes cluster environment configuration, the operation request includes a request to modify a cluster environment configuration item. If the cluster related information includes a cluster service version, the operation request includes a cluster service version query request or a cluster service version online request.

[0124] The grouping result determination module 420 is used to respond to the operation request and determine the grouping result related to the preset grouping attribute;

[0125] The operation execution module 430 is used to execute corresponding operations on the grouping results.

[0126] The cluster information management device provided in this embodiment includes an operation request receiving module, which is used to receive operation requests sent by users for cluster related information. If the cluster related information includes cluster environment configuration, the operation request includes a modification request for cluster environment configuration items. If the cluster related information includes cluster service version, the operation request includes a cluster service version query request or a cluster service version online request; a grouping result determination module, which is used to respond to the operation request and determine the grouping result related to the preset grouping attribute; an operation execution module, which is used to perform corresponding operations on the grouping result. By adding corresponding preset grouping attributes to the cluster environment configuration, the cluster environment configurations are independent of each other and do not affect each other. Even if the configuration modification of any cluster is wrong, it will not affect the normal execution of tasks of other clusters of the same type. In addition, by adding corresponding preset grouping attributes to the cluster service version, the cluster service version can be authorized and distributed according to different users, and gray-scale upgrades can be performed, etc., to ultimately ensure that the big data platform can perform tasks normally.

[0127] On the basis of the above-mentioned technical solutions, further, the cluster-related information includes cluster environment configuration, the operation request includes a modification request of the cluster environment configuration item, and the preset grouping attribute includes an executor group; accordingly, the grouping result determination module 420 can be specifically used to: determine whether the executor group corresponding to the cluster environment configuration item exists, the executor group includes one or more executors, wherein the executor is the executor corresponding to the cluster environment configuration item; if it exists, the executor corresponding to the cluster environment configuration item is attributed to the executor group; accordingly, the operation execution module 430 can be specifically used to: based on the environment configuration storage path, perform a modification operation of the cluster environment configuration item on each executor in the executor group, wherein the environment configuration storage path is stored in a one-to-one correspondence with the executor group, and the environment configuration storage path is used to indicate the storage location of the cluster environment configuration item in the corresponding executor.

[0128] On the basis of the above-mentioned technical solutions, further, the operation execution module 430 can also be specifically used to modify the environment configuration storage path if the environment configuration storage path changes after the cluster environment configuration item modification operation is performed on each executor in the executor group.

[0129] On the basis of the above-mentioned technical solutions, further, the grouping result determination module 420 can also be specifically used for: after determining whether the executor group corresponding to the cluster environment configuration item exists, if it does not exist, a new executor group is created, and the executors with the same cluster environment configuration item are assigned to the executor group, and the environment configuration storage path corresponding to the executor group is determined.

[0130] On the basis of the above-mentioned technical solutions, further, the grouping result determination module 420 can also be specifically used for: before performing a modification operation on the cluster environment configuration items of each executor in the executor group, determining whether there are irrelevant executors in the executor group, and the irrelevant executors are executors that do not need to modify the cluster environment configuration items; if so, removing the irrelevant executors, creating a new irrelevant executor group, assigning the irrelevant executors to the irrelevant executor group, and using the executor group after removing the irrelevant executors as the new executor group.

[0131] On the basis of the above-mentioned technical solutions, the cluster information management device further includes a task execution and result judgment module, which is used to execute the corresponding task based on the modified cluster environment configuration after performing the corresponding operation on the grouping result; if the execution result meets the expectation, the modification operation is completed; if the execution result does not meet the expectation, the steps of determining the grouping result related to the preset grouping attribute and performing the corresponding operation on the grouping result are repeated until the execution result meets the expectation.

[0132] On the basis of the above-mentioned technical solutions, further, the cluster-related information includes the cluster service version, the operation request includes the service version query request, and the preset grouping attributes include version merge, cluster, department and service version switch; accordingly, the grouping result determination module 420 can be specifically used to: determine the query condition based on the operation request, the operation request includes at least one of the service type, cluster value and department value, wherein the service type includes a specified service type or the full service type, the cluster value includes a specified cluster or the default, and the department value includes a specified department or the default; based on the query condition, the preset version coverage priority and the service version switch value, determine the service version grouping result with the preset grouping attribute, the preset version coverage priority is that if the version merge values ​​corresponding to the version merge are the same, the department value coverage priority is higher than the cluster value coverage priority, and the cluster value coverage priority is higher than the default coverage priority, wherein cluster service versions belonging to the same service type and the same service basic functions have the same version merge value.

[0133] On the basis of the above technical solutions, further, the grouping result determination module 420 can also be specifically used for: if the service type, cluster value and department value are not specified in the operation request, the query condition is that the service type is the full service type and the cluster value is the default and the department value is the default;

[0134] If the service type and department value are not specified in the operation request, but the cluster value is specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, department value is the default or all departments under the specified cluster, and service type is all service types, cluster value is the default, and department value is the default;

[0135] If the service type is not specified in the operation request, but the cluster value and department value are specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, and department value is the specified department value; service type is all service types, cluster value is the specified cluster value, and department value is the default; and service type is all service types, cluster value is the default, and department value is the default;

[0136] If the service type is specified in the operation request, but the cluster value and department value are not specified, the query condition is that the service type is the specified service type and the cluster value is the default and the department value is the default;

[0137] If the service type and cluster value are specified in the operation request, but the department value is not specified, the query conditions are: service type is the specified service type, cluster value is the specified cluster value, and department value is the default or all departments under the specified cluster, and service type is the specified service type, cluster value is the default, and department value is the default;

[0138] If the service type, cluster value, and department value are specified in the operation request, the query conditions are: the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the specified department value; the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the default; and the service type is the specified service type, the cluster value is the default, and the department value is the default.

[0139] On the basis of the above technical solutions, further, the grouping result determination module 420 can also be specifically used to: after the initial service version grouping result is queried using the query condition, the grouping result whose service version value is closed in the initial service version grouping result is removed to obtain the pre-processed service version grouping result;

[0140] In the pre-processing service version grouping results, if there is a version merge grouping result with the same version merge value, determine whether there is a first sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a specified department value. If so, retain the first sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the first sub-grouping result. If not, determine whether there is a second sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a default. If so, retain the second sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the second sub-grouping result. If not, retain the version merge grouping result to finally obtain the service version grouping result.

[0141] On the basis of the above technical solutions, further, the cluster related information includes the cluster service version, the operation request includes the service version online request, and the preset grouping attributes include version merging, cluster, department, and service version switch; accordingly, the grouping result determination module 420 can also be specifically used for:

[0142] According to the operation request, a grouping result with preset grouping attributes is generated, wherein the version merge value is the service basic function version corresponding to the corresponding service type, the cluster value is the specified cluster value, the department value is the specified department value, and the service version switch is in the on state.

[0143] The cluster information management device provided in the embodiment of the present application can execute the steps in the cluster information management method provided in the method embodiment of the present application, and the execution steps and beneficial effects are not repeated here.

[0144] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 5 As shown, the electronic device 330 includes a processor 331 and a memory 332 , wherein the processor 331 may be one or more.

[0145] The processor 331 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 330 to perform desired functions.

[0146] The memory 332 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and / or a cache memory (cache), etc. The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer programs or instructions may be stored on the computer-readable storage medium, and the processor 331 may call the program or instruction to implement the power battery low power protection method of any embodiment of the present application described above and / or other desired functions. Various contents such as initial external parameters, thresholds, etc. may also be stored in the computer-readable storage medium.

[0147] In one example, the electronic device 330 may further include: an input device 333 and an output device 334, which are interconnected via a bus system and / or other forms of connection mechanisms (not shown). The input device 333 may include, for example, a keyboard, a mouse, etc. The output device 334 may output various information to the outside, including early warning prompt information, braking force, etc. The output device 334 may include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, etc.

[0148] Of course, to simplify, Figure 5 Only some of the components related to the present application in the electronic device 330 are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application conditions, the electronic device 330 may also include any other appropriate components.

[0149] In addition to the above methods and devices, the embodiments of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the cluster information management method provided by any embodiment of the present application.

[0150] The computer program product may be written in any combination of one or more programming languages ​​to write program codes for performing the operations of the embodiments of the present application, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0151] In addition, the embodiments of the present application may also be a computer-readable storage medium on which a program or instruction is stored, and the program or instruction enables a computer to execute the steps of the cluster information management method provided by any embodiment of the present application.

[0152] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0153] It should be noted that the terms used in this application are only for describing specific embodiments, rather than limiting the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates an exception, the words "one", "a", "a kind of" and / or "the" do not specifically refer to the singular, but may also include the plural. The terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method or device including the elements.

[0154] It should also be noted that the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. Unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", etc. should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0155] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and its core ideas of this application. The above is only the preferred implementation method of this application. It should be pointed out that due to the limitations of textual expression and the objective existence of infinite specific structures, ordinary technicians in this technical field can make several improvements, modifications or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner; these improvements, modifications, changes or combinations, or the direct application of the concept and technical solution of the invention to other occasions without improvement, should be regarded as the scope of protection of this application.

Claims

1. A cluster information management method, It is characterized in that include: Receive an operation request sent by a user for cluster related information, if the cluster related information includes cluster environment configuration, the operation request includes a modification request for a cluster environment configuration item, if the cluster related information includes a cluster service version, the operation request includes a cluster service version query request or a cluster service version online request; In response to the operation request, determine a grouping result related to a preset grouping attribute; Performing corresponding operations on the grouping results; The cluster related information includes cluster environment configuration, the operation request includes a request to modify a cluster environment configuration item, and the preset grouping attribute includes an actuator group; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes: Determine whether an executor group corresponding to the cluster environment configuration item exists, the executor group includes one or more executors, wherein the executor is the executor corresponding to the cluster environment configuration item; If so, the executor corresponding to the cluster environment configuration item is assigned to the executor group, and correspondingly, corresponding operations are performed on the grouping result, including: based on the environment configuration storage path, performing a modification operation of the cluster environment configuration item on each executor in the executor group, wherein the environment configuration storage path is stored in a one-to-one correspondence with the executor group, and the environment configuration storage path is used to indicate the storage location of the cluster environment configuration item in the corresponding executor; The cluster related information includes a cluster service version, the operation request includes a service version query request, and the preset grouping attributes include version merge, cluster, department, and service version switch; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes: Determine the query condition based on the operation request, wherein the operation request includes at least one of a service type, a cluster value, and a department value, wherein the service type includes a specified service type or a full service type, the cluster value includes a specified cluster or a default, and the department value includes a specified department or a default; Based on the query conditions, the preset version coverage priority and the service version switch value, the service version grouping result with the preset grouping attribute is determined. The preset version coverage priority is that if the version merge values ​​corresponding to the version merge are the same, the department value coverage priority is higher than the cluster value coverage priority, and the cluster value coverage priority is higher than the default coverage priority. Among them, cluster service versions belonging to the same service type and the same service basic functions have the same version merge value.

2. The method according to claim 1, It is characterized in that After performing a modification operation on the cluster environment configuration item on each executor in the executor group, if the environment configuration storage path is changed, performing a corresponding operation on the grouping result, further comprising: The environment configuration storage path is modified.

3. The method according to claim 1, It is characterized in that After determining whether the executor group corresponding to the cluster environment configuration item exists, the method further includes: If it does not exist, a new executor group is created, and executors with the same cluster environment configuration items are assigned to the executor group, and the environment configuration storage path corresponding to the executor group is determined.

4. The method according to any one of claims 1 to 3, It is characterized in that Before performing a modification operation on the cluster environment configuration item on each executor in the executor group, the method further includes: Determine whether there is an irrelevant executor in the executor group, wherein the irrelevant executor is an executor that does not require cluster environment configuration item modification; If it exists, the irrelevant executor is removed, a new irrelevant executor group is created, the irrelevant executor is assigned to the irrelevant executor group, and the executor group after removing the irrelevant executor is used as the new executor group.

5. The method according to any one of claims 1 to 3, It is characterized in that After performing corresponding operations on the grouping results, the method further includes: Execute corresponding tasks based on the modified cluster environment configuration; If the execution result is as expected, the modification operation is completed; If the execution result does not meet expectations, the steps of determining the grouping result related to the preset grouping attribute and performing corresponding operations on the grouping result are repeated until the execution result meets expectations.

6. The method according to claim 1, It is characterized in that Determining a service version grouping result having the preset grouping attribute based on the query condition, the preset version coverage priority, and the service version switch value includes: If the service type, cluster value, and department value are not specified in the operation request, the query conditions are that the service type is all service types and the cluster value is default and the department value is default; If the service type and department value are not specified in the operation request, but the cluster value is specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, department value is the default or all departments under the specified cluster, and service type is all service types, cluster value is the default, and department value is the default; If the service type is not specified in the operation request, but the cluster value and department value are specified, the query conditions are: service type is all service types, cluster value is the specified cluster value, and department value is the specified department value; service type is all service types, cluster value is the specified cluster value, and department value is the default; and service type is all service types, cluster value is the default, and department value is the default; If the service type is specified in the operation request, but the cluster value and department value are not specified, the query condition is that the service type is the specified service type and the cluster value is the default and the department value is the default; If the service type and cluster value are specified in the operation request, but the department value is not specified, the query conditions are: service type is the specified service type, cluster value is the specified cluster value, and department value is the default or all departments under the specified cluster, and service type is the specified service type, cluster value is the default, and department value is the default; If the service type, cluster value, and department value are specified in the operation request, the query conditions are: the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the specified department value; the service type is the specified service type, the cluster value is the specified cluster value, and the department value is the default; and the service type is the specified service type, the cluster value is the default, and the department value is the default.

7. The method according to claim 6, It is characterized in that Determining a service version grouping result having the preset grouping attribute based on the query condition, the preset version coverage priority, and the service version switch value includes: After the initial service version grouping result is queried using the query condition, the grouping result with the service version value of closed in the initial service version grouping result is removed to obtain the pre-processed service version grouping result; In the pre-processing service version grouping results, if there is a version merge grouping result with the same version merge value, determine whether there is a first sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a specified department value. If so, retain the first sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the first sub-grouping result. If not, determine whether there is a second sub-grouping result in the version merge grouping result whose cluster value is a specified cluster value and whose department value is a default. If so, retain the second sub-grouping result and delete the other sub-grouping results in the version merge grouping result except the second sub-grouping result. If not, retain the version merge grouping result to finally obtain the service version grouping result.

8. The method according to claim 1, It is characterized in that The cluster related information includes a cluster service version, the operation request includes a service version online request, and the preset grouping attributes include version merge, cluster, department, and service version switch; accordingly, in response to the operation request, determining a grouping result related to the preset grouping attribute includes: According to the operation request, a grouping result with preset grouping attributes is generated, wherein the version merge value is the service basic function version corresponding to the corresponding service type, the cluster value is the specified cluster value, the department value is the specified department value, and the service version switch is in the on state.