CN108958933B - Configuration parameter updating method, device and equipment of task executor - Google Patents
Configuration parameter updating method, device and equipment of task executor Download PDFInfo
- Publication number
- CN108958933B CN108958933B CN201810682534.5A CN201810682534A CN108958933B CN 108958933 B CN108958933 B CN 108958933B CN 201810682534 A CN201810682534 A CN 201810682534A CN 108958933 B CN108958933 B CN 108958933B
- Authority
- CN
- China
- Prior art keywords
- task
- executor
- task executor
- original
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5011—Pool
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Document Processing Apparatus (AREA)
- Stored Programmes (AREA)
Abstract
In this embodiment, when a need for updating the configuration parameters of the task executor is encountered, a new configuration parameter may be obtained, a new configuration file may be generated by using the new configuration parameter, a new task executor may be created based on the configuration file, which is referred to as a target task executor in this embodiment, and then the target task executor replaces an original task executor, and a newly received task may be allocated to the target task executor for processing, thereby achieving a purpose of updating the configuration parameters of the task executor. The embodiment can not interrupt the original task processing work, thereby supporting the dynamic configuration of the thread pool parameters, and when the traffic volume changes, the configuration parameters can be adjusted at any time, thereby being capable of meeting various service requirements.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for updating configuration parameters of a task executor.
Background
At present, a device may use a concurrent processing mode to handle a task request, taking multithread processing as an example, the processing procedure includes: creating a thread pool based on a configuration file, wherein configuration parameters of the thread pool, such as the number of core threads, the maximum number of concurrent threads or the idle time of threads, are written in the thread pool, and a task scheduler adds a task to be processed to a task queue; after finding that the task waiting for processing in the task queue arrives, the thread pool can create threads to execute the task, and one thread processes one task.
In practical application, with the development of services, the requirement for updating the configuration parameters of the thread pool may be met; for example, due to upgrading of hardware functions of the device or increase of service requests, the maximum number of concurrent threads of the thread pool needs to be enlarged, and the like. At this time, the work of the thread pool needs to be terminated, so that the task processing is interrupted, then the configuration file of the thread pool is modified, the thread pool is brought online again according to the new configuration file, and the maximum number of concurrent threads of the thread pool is increased.
Disclosure of Invention
In order to overcome the problems in the related art, the specification provides a method, a device and equipment for updating configuration parameters of a task executor.
According to a first aspect of the embodiments of the present specification, there is provided a method for updating configuration parameters of a task executor, where the method is used to update configuration parameters of an original task executor that currently hosts a task, and the method includes:
acquiring configuration parameters to be updated, and generating a configuration file by using the configuration parameters to be updated;
and after a target task executor is created based on the configuration file, distributing the received task to the target task executor.
Optionally, after the received task is assigned to the target task executor, the method further includes: and logging out the original task executor.
Optionally, the original task executor is logged out after all threads of the original task executor process the completed tasks, or is logged out after the target time arrives.
Optionally, the allocating the received task to the target task executor includes:
and sending the identification of the target task executor to a task scheduler, and distributing the received task to the task executor corresponding to the identification by the task scheduler.
Optionally, the task executor includes one or more of the following: a thread pool or an object pool.
According to a second aspect of embodiments herein, there is provided a task processing system including:
a dynamic configuration manager to: acquiring configuration parameters to be updated and task executor identifiers to be switched, and sending the task executor identifiers to a task scheduler;
an executor management unit to: generating a configuration file by using the configuration parameters, and creating a task executor based on the configuration file; and managing the created one or more task executors;
a task scheduler to: receiving a task to be processed; and after receiving the task executor identifier, sending the task to be processed to a task executor corresponding to the task executor identifier.
Optionally, the executor management unit is configured to: and logging out the original task executor.
Optionally, the original task executor is logged out after all threads of the original task executor process the completed tasks, or is logged out after the target time arrives.
According to a third aspect of the embodiments of the present specification, there is provided a configuration parameter updating apparatus for a task executor, configured to update configuration parameters of an original task executor currently hosting a task, the apparatus including:
an acquisition module to: acquiring configuration parameters to be updated, and generating a configuration file by using the configuration parameters to be updated;
an assignment module to: and after a target task executor is created based on the configuration file, distributing the received task to the target task executor.
Optionally, after the received task is assigned to the target task executor, the method further includes: and logging out the original task executor.
Optionally, the original task executor is logged out after all threads of the original task executor process the completed tasks, or is logged out after the target time arrives.
According to a fourth aspect of embodiments herein, there is provided a computer apparatus comprising: the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the configuration parameter updating method of the task executor.
The technical scheme provided by the embodiment of the specification can have the following beneficial effects:
in this embodiment, if a need for updating the configuration parameters of the task executor is encountered, a new configuration parameter may be obtained, the new configuration parameter is used to generate a new configuration file, a new task executor may be created based on the configuration file, which is referred to as a target task executor in this embodiment, then the target task executor replaces an original task executor, and a newly received task may be allocated to the target task executor for processing, so as to achieve the purpose of updating the configuration parameters of the task executor. The embodiment can not interrupt the original task processing work, thereby supporting the dynamic configuration of the thread pool parameters, and when the traffic volume changes, the configuration parameters can be adjusted at any time, thereby being capable of meeting various service requirements.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.
FIG. 1 is a multi-threaded processing diagram shown in accordance with an exemplary embodiment of the present description.
FIG. 2A is an application scenario diagram illustrating configuration parameter updating for a task executor according to an exemplary embodiment.
FIG. 2B is a flow diagram illustrating updating of configuration parameters of a task executor according to an exemplary embodiment.
FIG. 2C is a schematic diagram illustrating updating of configuration parameters of a task executor, according to an example embodiment.
FIG. 3 is an architectural diagram of a task processing system, shown in accordance with an exemplary embodiment of the present description.
Fig. 4 is a hardware configuration diagram of a computer device in which a configuration parameter updating apparatus of a task executor according to an embodiment of the present disclosure is located.
FIG. 5 is a block diagram illustrating a configuration parameter update mechanism for a task executor according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
With the continuous development of internet technology, the requirements for the processing capability of devices such as terminals or servers are higher and higher. For example, at some point, a device may receive multiple tasks, and how to handle these tasks becomes a concern to technicians.
Optionally, the apparatus may adopt a multi-thread processing form, as shown in fig. 1, which is a multi-thread processing schematic diagram according to an exemplary embodiment shown in this specification, and involves a thread pool and a task scheduler; the treatment process comprises the following steps: creating a thread pool based on a configuration file, wherein configuration parameters of the thread pool, such as the number of core threads, the maximum number of concurrent threads or the idle time of threads, are written in the file; the task scheduler adds the tasks to be processed to the task queue; after finding that the task waiting for processing in the task queue arrives, the thread pool can create threads to execute the task, and one thread processes one task.
And after the thread pool is established, the set configuration parameters are kept unchanged. For example, after the thread pool is created, the number of threads may be controlled by setting the maximum number of concurrent threads, for example, if the maximum number of concurrent threads of a thread pool is set to 5, then a maximum of 5 threads may be created in the thread pool to process tasks. However, since the number of the to-be-processed tasks in the task queue is variable and the maximum number of the concurrent threads is fixed, the number of the to-be-processed tasks in the task queue may be too large, and particularly in a high-concurrency scenario, a situation that the to-be-processed tasks cannot be executed in time often occurs.
In practical application, with the development of services, the requirement for updating the configuration parameters of the thread pool may be met; for example, due to upgrading of hardware functions of the device or increase of service requests, the maximum number of concurrent threads of the thread pool needs to be enlarged. At this time, the task processing is interrupted because the work of the thread pool needs to be terminated, and then the configuration file of the thread pool is modified, and the thread pool is re-created according to the new configuration file, so that the maximum concurrent thread number of the thread pool is increased.
Similar to thread pools, task executors such as object pools also have a need for configuration parameter updates. The thread pool can be used for processing various tasks, and the object pool can be used for managing task objects such as index files, webpage content resources and the like. Based on this, an embodiment of the present specification provides a configuration parameter updating scheme for a task executor, and an application scenario of the configuration parameter updating method for a task executor in the embodiment of the present specification is illustrated first, as shown in fig. 2A, fig. 2A relates to a plurality of terminal devices, a network, and a plurality of servers (which may also be a server cluster, a cloud server, and the like). The network serves as a medium for providing a communication link between the terminal device and the server. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use a terminal device to interact with a server over a network to receive or transmit data, etc. Various applications can be installed on the terminal device, such as a social application, a web browser application, a search engine application, a shopping application, an instant messaging application, a mobile phone assistant application, and the like.
The terminal device may be a variety of electronic devices including, but not limited to, smart phones, tablet computers, electronic book readers, multimedia players, laptop portable computers, desktop computers, and the like.
The server may be a server providing various services, such as a background server providing support for applications installed on the terminal device. The background server can receive the request of the terminal equipment, process data according to the request and feed back the processing result to the terminal equipment.
The method for updating the configuration parameters of the task executor in the embodiment of the present description may be executed by the server or the terminal device, and accordingly, the apparatus for updating the configuration parameters of the task executor may be disposed in the server 1 or the terminal device. It should be understood that the number of terminal devices, networks, and servers in fig. 2A are merely illustrative. There may be any number of terminal devices, networks, and servers, as desired.
In this embodiment, a task executor currently accepting a task is referred to as an original task executor, and if a configuration parameter of the original task executor needs to be updated, a device may apply a method for updating a configuration parameter of a task executor as shown in fig. 2B, where the method includes the following steps:
in step 202, the configuration parameters of the actuator to be updated are obtained, and a configuration file is generated by using the configuration parameters of the actuator.
In step 204, after creating the target task executor based on the configuration file, the received task is switched from being allocated to the original task executor to being allocated to the target task executor.
In this embodiment, if a need for updating the configuration parameters of the task executor is met, a new configuration parameter may be obtained, the new configuration parameter is used to generate a new configuration file, a new task executor may be created based on the new configuration file, which is called as a target task executor, and then the target task executor replaces an original task executor to support a task, and a newly received task may be allocated to the target task executor to be processed, so as to achieve the purpose of updating the configuration parameters of the task executor. The embodiment can not interrupt the original task processing work, so that the dynamic configuration parameters can be supported, and when the traffic volume changes, the configuration parameters can be adjusted at any time, thereby meeting various service requirements.
After the target task executor is created, two task executors are involved in the embodiment: optionally, the original task executor and the target task executor may have unique identifiers, and the identifiers may uniquely distinguish the original task executor from the target task executor by using a name, a pointer address, and the like. In some examples, a task scheduler is used to take over tasks and distribute the received tasks to task executors; the task scheduler needs to obtain an identification of the task executor so that the task scheduler can know to which task executor the task should be allocated. Thus, the switching the assignment of the received task from the assignment to the original task executor to the target thread pool may include:
and sending the identification of the target task executor to a task scheduler, and informing the task scheduler to switch and allocate the received task from the original task executor to the target task executor.
The target task executor replaces an original task executor, updating of configuration parameters of the task executor is achieved, the original task executor does not need to take over a new task, and in order to release resources occupied by the original task executor, the original task executor can be cancelled after a received task is distributed to the task executor.
The logout time can be flexibly configured according to needs, and in some examples, the logout can be directly performed after the target task executor accepts the tasks; in some examples, since the original task executor has accepted some tasks for processing, if direct logout would cause the tasks to fail to be processed, logout may be performed after processing has completed all accepted tasks. In other examples, the original task executor may take a long time to process the accepted tasks, and considering that the original task executor may occupy a large amount of resources, it may also set a target time, and after the target time is reached, the original task executor is logged off to release the resources regardless of whether all tasks in the original task executor are completed. The target time can be flexibly determined according to actual needs.
The above method for updating configuration parameters of a task executor may be applied to a task processing scenario, as shown in fig. 3, which is an architectural diagram of a task processing system according to an exemplary embodiment shown in this specification, and includes:
a dynamic configuration manager 31 for: the method comprises the steps of obtaining configuration parameters to be updated, obtaining task executor identifiers to be switched, and sending the task executor identifiers to a task scheduler.
An executor management unit 32 to: generating a configuration file by using the configuration parameters, and creating a task executor based on the configuration file; and managing the created one or more task executors.
A task scheduler 33 for: receiving a task to be processed; and after receiving the task executor identifier, sending the task to be processed to a task executor corresponding to the task executor identifier.
In the task management system of this embodiment, the executor management unit may manage at least one task executor, where the task executor is configured to process a task; the creation process of the task executor may be that a configuration file is generated by using the configuration parameters, and the task executor is created based on the configuration file. As business evolves, a need to update configuration parameters of task performers may be faced. In the embodiment, the configuration parameters are updated by newly building another task executor to replace the existing task executor.
The embodiment provides a dynamic configuration manager, which can be used for acquiring configuration parameters to be updated; the configuration parameters to be updated may be configured by a technician, or may be automatically obtained by a dynamic configuration manager according to a set policy. After acquiring the new configuration parameters, the executor management unit may generate a new configuration file by using the configuration parameters to be updated, and create a new task executor based on the configuration file. Under the condition that one or more task executors exist, a task scheduler needs to send the task to be processed to the task executor corresponding to the task executor identifier according to the task executor identifier. Based on the above framework, after a new task executor is created, the task scheduler can be notified of the identifier of the new task executor, the task to be processed is sent to the newly created task executor through the task scheduler, and the old task executor does not carry the task any more, thereby realizing the update of the configuration parameters.
In this embodiment, the task executor that accepts the task before the dynamic configuration manager receives the task executor identifier is an original task executor, and the executor management unit is configured to: and after the dynamic configuration manager receives the task executor identifier, canceling the original task executor so as to release the resources occupied by the original thread pool.
Optionally, the executor management unit is configured to: and logging out the original task executor after the original task executor processes the completed task, or logging out the original task executor after the target time is reached. In some examples, since the original task executor has accepted some tasks for processing, if direct logout would cause the tasks to fail to be processed, logout may be performed after processing has completed all accepted tasks. In other examples, the original task executor may take a long time to process the accepted tasks, and considering that the original task executor may occupy a large amount of resources, it may also set a target time, and after the target time is reached, the original task executor is logged off to release the resources regardless of whether all tasks in the original task executor are completed.
Corresponding to the foregoing embodiments of the method for updating configuration parameters of a task executor, the present specification further provides embodiments of a device for updating configuration parameters of a task executor and a computer device to which the device is applied.
The embodiment of the configuration parameter updating device of the task executor in the specification can be applied to computer equipment, such as a server or terminal equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor in which the file processing is located. From a hardware aspect, as shown in fig. 4, it is a hardware structure diagram of a computer device where a configuration parameter updating apparatus of a task executor in this description is located, except for the processor 410, the memory 430, the network interface 420, and the nonvolatile memory 440 shown in fig. 4, a server or an electronic device where the apparatus 431 is located in this embodiment may also include other hardware according to an actual function of the computer device, which is not described again.
As shown in fig. 5, fig. 5 is a block diagram of a configuration parameter updating apparatus for a task executor according to an exemplary embodiment, for updating a configuration parameter of an original task executor of a currently hosted task, the apparatus including:
an obtaining module 51, configured to: acquiring configuration parameters to be updated, and generating a configuration file by using the configuration parameters to be updated;
an assignment module 52 to: and after a target task executor is created based on the configuration file, distributing the received task to the target task executor.
Optionally, after the received task is assigned to the target task executor, the method further includes: and logging out the original task executor.
Optionally, the original task executor is logged out after all threads of the original task executor process the completed tasks, or is logged out after the target time arrives.
Optionally, the allocating module is further configured to:
and sending the identification of the target task executor to a task scheduler, and distributing the received task to the task executor corresponding to the identification by the task scheduler.
Optionally, the task executor includes one or more of the following: a thread pool, an object pool, or a resource pool.
The implementation process of the function and the action of each module in the configuration parameter updating apparatus of the task executor is specifically described in the implementation process of the corresponding step in the configuration parameter updating method of the task executor, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (9)
1. A method for updating configuration parameters of a task executor, which is used for updating configuration parameters of an original task executor of a current accepting task, comprises the following steps:
acquiring configuration parameters to be updated, and generating a configuration file by using the configuration parameters to be updated;
and after a target task executor is created based on the configuration file, switching and distributing the received task from the task executor distributed to the original task executor to the target task executor, and logging off the original task executor.
2. The method of claim 1, wherein the original task executor is logged out after processing all accepted tasks, or is logged out after the target time arrives.
3. The method of claim 1, the switching the assignment of the received task from the assignment to the original task executor to the target task executor, comprising:
and sending the identification of the target task executor to a task scheduler, and switching and distributing the received task from the task scheduler to the original task executor to the task executor corresponding to the identification.
4. The method of claim 1, the task executor comprising one or more of: a thread pool or an object pool.
5. A task processing system comprising:
a dynamic configuration manager to: acquiring configuration parameters to be updated and task executor identifiers to be switched, and sending the task executor identifiers to a task scheduler;
an executor management unit to: generating a configuration file by using the configuration parameters, and creating a task executor based on the configuration file; and managing the created one or more task executors; after the dynamic configuration manager receives the task executor identifier, an original task executor is cancelled, wherein the original task executor is a task executor for bearing a task before the dynamic configuration manager receives the task executor identifier;
a task scheduler to: receiving a task to be processed; and after receiving the task executor identifier, sending the task to be processed to a task executor corresponding to the task executor identifier.
6. The system of claim 5, the executor management unit to: and logging out the original task executor after the original task executor processes the completed task, or logging out the original task executor after the target time is reached.
7. A configuration parameter updating device of a task executor, configured to update a configuration parameter of an original task executor currently hosting a task, the device comprising:
an acquisition module to: acquiring configuration parameters to be updated, and generating a configuration file by using the configuration parameters to be updated;
an assignment module to: and after a target task executor is created based on the configuration file, distributing the received task to the target task executor and logging off the original task executor.
8. The apparatus of claim 7, wherein the original task executor is logged out after all threads of the original task executor process the completed task, or is logged out after the target time arrives.
9. A computer device, comprising: memory, processor and computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the method according to any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810682534.5A CN108958933B (en) | 2018-06-27 | 2018-06-27 | Configuration parameter updating method, device and equipment of task executor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810682534.5A CN108958933B (en) | 2018-06-27 | 2018-06-27 | Configuration parameter updating method, device and equipment of task executor |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108958933A CN108958933A (en) | 2018-12-07 |
| CN108958933B true CN108958933B (en) | 2021-12-21 |
Family
ID=64487579
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810682534.5A Active CN108958933B (en) | 2018-06-27 | 2018-06-27 | Configuration parameter updating method, device and equipment of task executor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108958933B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112925578B (en) * | 2021-01-28 | 2024-01-30 | 北京达佳互联信息技术有限公司 | Task processing method, device and storage medium |
| CN112948085A (en) * | 2021-03-03 | 2021-06-11 | 杉数科技(北京)有限公司 | Task scheduling processing method and device |
| CN114090112B (en) * | 2021-10-27 | 2023-06-16 | 青岛海尔科技有限公司 | Method and device for loading configuration file, storage medium and electronic device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346767A (en) * | 2011-09-19 | 2012-02-08 | 北京金和软件股份有限公司 | Database connection method based on double connection pools |
| CN103218264A (en) * | 2013-03-26 | 2013-07-24 | 广东威创视讯科技股份有限公司 | Multi-thread finite state machine switching method and multi-thread finite state machine switching device based on thread pool |
| CN106020927A (en) * | 2016-05-05 | 2016-10-12 | 中国人民解放军国防科学技术大学 | Universal method for task scheduling and resource configuration in cloud computing system |
| CN106802826A (en) * | 2016-12-23 | 2017-06-06 | 中国银联股份有限公司 | A kind of method for processing business and device based on thread pool |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2608032A1 (en) * | 2011-12-22 | 2013-06-26 | Software AG | Resource adapter for establishing a connection between an executive information system (EIS) and at least one client |
-
2018
- 2018-06-27 CN CN201810682534.5A patent/CN108958933B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346767A (en) * | 2011-09-19 | 2012-02-08 | 北京金和软件股份有限公司 | Database connection method based on double connection pools |
| CN103218264A (en) * | 2013-03-26 | 2013-07-24 | 广东威创视讯科技股份有限公司 | Multi-thread finite state machine switching method and multi-thread finite state machine switching device based on thread pool |
| CN106020927A (en) * | 2016-05-05 | 2016-10-12 | 中国人民解放军国防科学技术大学 | Universal method for task scheduling and resource configuration in cloud computing system |
| CN106802826A (en) * | 2016-12-23 | 2017-06-06 | 中国银联股份有限公司 | A kind of method for processing business and device based on thread pool |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108958933A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111831450B (en) | Method, device, electronic equipment and storage medium for distributing server resources | |
| CN108737270B (en) | Resource management method and device for server cluster | |
| CN113489772B (en) | Network request processing method and device and electronic equipment | |
| US20200328984A1 (en) | Method and apparatus for allocating resource | |
| EP3357006B1 (en) | Workflow service using state transfer | |
| CN109075986B (en) | Network function instance management method and related equipment | |
| CN109451088A (en) | A kind of data access method and device | |
| CN110765024A (en) | Simulation test method, simulation test device, electronic equipment and computer-readable storage medium | |
| CN109388626B (en) | Method and apparatus for assigning numbers to services | |
| CN108958933B (en) | Configuration parameter updating method, device and equipment of task executor | |
| CN111491015B (en) | Preheating task processing method and system, proxy server and service center | |
| CN105516086A (en) | Service processing method and apparatus | |
| CN111478781B (en) | Message broadcasting method and device | |
| CN111770176B (en) | Traffic scheduling method and device | |
| CN109828830B (en) | Method and apparatus for managing containers | |
| CN105847319A (en) | Mobile terminal network request method and system | |
| RU2696299C2 (en) | Control when initiating elementary tasks on server platform | |
| CN110113176B (en) | Information synchronization method and device for configuration server | |
| CN112398669A (en) | Hadoop deployment method and device | |
| CN112104679A (en) | Method, apparatus, device and medium for processing hypertext transfer protocol request | |
| CN108696557B (en) | Information processing system, method and device | |
| CN110764911A (en) | Resource scheduling method, device and control system based on order | |
| JP2017021667A (en) | System and control method | |
| US20210256600A1 (en) | Connector leasing for long-running software operations | |
| CN111045778B (en) | Virtual machine creation method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200922 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200922 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |