CN111752695B - Offline method, device, equipment and storage medium - Google Patents

Abstract

The embodiments of the present application disclose a method, device, equipment and storage medium for going offline, which relate to the fields of computers, cloud computing and audio and video processing technology. The specific implementation scheme is: determine that multiple instances in a machine to be taken offline are multiple instances to be deleted; record the multiple instances to be deleted in a preset list, wherein the instances to be deleted recorded in the preset list stop acquiring tasks; if the instance to be deleted is not executing a task, delete the instance to be deleted from the system; after all the multiple instances to be deleted in the machine to be taken offline are deleted, take the machine to be taken offline offline from the system. The embodiments of the present application can reduce the impact of the machine going offline on the system service.

Description

Offline method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer technology, and in particular to the field of cloud computing and audio and video processing technology.

Background Art

In the audio and video transcoding system, if a machine needs to be used for other purposes, needs to be repaired due to a fault, or needs to be removed from the shelf due to aging, the current way to operate the machine offline (also known as machine retirement) is to violently delete multiple instances on the machine and then remove the machine from the audio and video transcoding system. If the instance is processing a real-time transcoding task at this time, the violent deletion method will cause the transcoding task to fail.

Summary of the invention

The present application provides an offline method, apparatus, device and storage medium.

According to one aspect of the present application, a method for going offline is provided, comprising:

Determine that multiple instances in the machine to be taken offline are multiple instances to be deleted;

Recording multiple instances to be deleted in a preset list, wherein the instances to be deleted recorded in the preset list stop acquiring tasks;

If the instance to be deleted recorded in the preset list is not executing a task, the instance to be deleted will be deleted from the system;

After all the instances to be deleted in the machine to be taken offline are deleted, the machine to be taken offline is taken offline from the system.

According to another aspect of the present application, there is provided a offline device, comprising:

An instance determination module, used for determining that multiple instances in the machine to be taken offline are multiple instances to be deleted;

A recording module, used for recording multiple instances to be deleted in a preset list, and stopping the acquisition task for the instances to be deleted recorded in the preset list;

A deletion module, used for deleting the instance to be deleted from the system if the instance to be deleted recorded in the preset list is not executing a task;

The offline module is used to offline the machine to be offline from the system after all the multiple instances to be deleted in the machine to be offline are deleted.

According to another aspect of the present application, a computer program product is provided, comprising a computer program, wherein the computer program implements the method described above when executed by a processor.

The technology of the present application can reduce the impact of machine offline on system services.

It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present application.

FIG1 is a flowchart of a method for going offline provided according to an embodiment of the present application;

FIG2 is a second flowchart of the offline method provided according to an embodiment of the present application;

FIG3 is a flowchart of a method for going offline provided according to an embodiment of the present application;

FIG4 is an exemplary diagram of a method for going offline provided according to an embodiment of the present application;

FIG5 is a second example diagram of a method for going offline provided according to an embodiment of the present application;

FIG6 is a structural diagram of a offline device according to an embodiment of the present application;

FIG7 is a second structural diagram of a offline device according to an embodiment of the present application;

FIG8 is a block diagram of an electronic device for implementing the offline method according to an embodiment of the present application.

DETAILED DESCRIPTION

The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

Referring to FIG. 1 , an embodiment of the present application provides an offline method, which relates to the field of computer technology, and in particular to the field of cloud computing and audio and video processing technology. The method includes:

S101, determining that multiple instances in the machine to be taken offline are multiple instances to be deleted;

S102, recording multiple instances to be deleted in a preset list, wherein the instances to be deleted recorded in the preset list stop acquiring tasks;

S103. If the instance to be deleted is not executing a task, the instance to be deleted is deleted from the system;

S104: After all the instances to be deleted in the machine to be taken offline are deleted, the machine to be taken offline is taken offline from the system.

Taking the audio transcoding system as an example, there are multiple clusters in the audio transcoding system, multiple machines in each cluster, multiple instances running on each machine, and each instance is used to perform a corresponding audio transcoding task, thereby realizing the audio transcoding function of the audio transcoding system. In addition, the present application can be used in various target object processing systems, such as video transcoding systems, image recognition systems, and speech recognition systems, etc.

An instance can also be called a container instance. A container instance can be understood as effectively dividing the resources managed by the operating system on a single machine into isolated groups to better balance conflicting resource usage requirements between isolated groups. A container instance runs one or more applications and the environment required for the application to run.

The machine in this application can be a physical machine, a virtual machine, or a cloud host, etc. The offline of a machine can also be referred to as the machine exiting the field.

The preset list in this application is called a blacklist, and the operation of recording an instance in the preset list is called blacklist processing.

The present application can be applied to servers, computing clusters or physical machines, etc. When the present application takes the machine offline from the system, the impact of the machine being offline on the system service can be greatly reduced. Taking the audio transcoding system as an example, if the instance in the machine is currently processing a real-time transcoding task, directly deleting the instance will cause the transcoding task to fail, and the task can only wait for the upstream to actively initiate a retry, re-initiate the transcoding task and wait for other instances to execute, resulting in high delays in online transcoding tasks. The present application records the instance of the machine to be taken offline in a preset list so that the instance no longer pulls the online transcoding task into its own task queue. Then, the instance is deleted only after the instance has completed executing the online transcoding task in the task queue, thereby reducing the impact of the machine being offline on the system's online services.

In one implementation, multiple instances in the machine to be taken offline are used to execute at least one of an audio transcoding task and a video transcoding task.

In one embodiment, before step S101, the method further includes:

A machine offline request is received, and a machine to be offline is determined according to the machine offline request. The machine offline request includes identifier information of the machine to be offline and identity information of the requester.

Optionally, a general machine exit operation interface or application programming interface (API) is provided. The user initiates a machine offline request by calling the API or operating through the interface. The main parameters of the API are: the operation object (the machine to be offline) and the operation initiator identity.

In one embodiment, referring to FIG. 2 , before recording information of multiple instances to be deleted in a preset list in step S102 , the method further includes:

S201. Under the assumption that the instance to be deleted is deleted, determine whether the system satisfies a preset fallback strategy;

S202: If the preset fallback strategy is met, execute step S102 to record the instance to be deleted in a preset list.

Optionally, when performing a fallback strategy judgment on each instance, it is necessary to perform a fallback strategy judgment on each instance to be deleted in turn to ensure the accuracy of the fallback strategy judgment. For example, first assume that instance A is deleted for a fallback strategy judgment. If it is satisfied, instance A is recorded in the preset list. Then, assume that instance B is deleted for a fallback strategy judgment. The fallback strategy judgment will take into account the situation where instance A in the system is recorded in the preset list. At this time, the fallback strategy judgment conclusion will obviously be more accurate than the conclusion of parallel judgment of multiple instances. The serial judgment method is adopted to ensure the accuracy of the fallback strategy judgment.

Optionally, if the result of the judgment in step S201 is that the system fallback strategy is not satisfied, step S102 is not executed, that is, the instance to be deleted is not recorded in the preset list.

Before taking offline machines, the system will be judged for a backup strategy before each instance is put into the preset list to ensure that the normal service of the system will not be affected after the instance is deleted. The instance is recorded in the preset list for deletion, which can avoid the problem of insufficient cluster resources of the system due to too many machines going offline. Taking the audio transcoding system as an example, if too many machines are taken offline on a certain day, there may be fewer instances used to process transcoding tasks, congestion in the transcoding queue, and a decrease in the system's transcoding capacity, which will eventually manifest as an increase in the overall transcoding delay of the system. By judging the backup strategy, the risk of insufficient cluster resources due to too many machines leaving the market can be avoided.

In one embodiment, the preset fallback strategy includes at least one of the following:

(1) The system configuration of the system meets the normal operation requirements; the system configuration includes one or more of the total central processing unit (CPU) capacity, total memory and total load;

(2) The proportion of instances recorded in the preset list in the system is less than the preset ratio;

(3) The number of machine offline times within the preset time does not exceed the preset number.

Before deleting an instance, after deleting it, you can effectively avoid the risk of insufficient cluster resources due to machine decommissioning by evaluating the system configuration, the proportion of instances to be deleted in the preset list, and the number of times the system operating machine has been offline.

In one implementation, step S102 records the multiple instances to be deleted in a preset list, including: calling an instance recording application programming interface (Application Programming Interface, API) of the transcoding system to record the multiple instances to be deleted in the preset list.

In one embodiment, for recording the instance to be deleted in a preset list in step S102, the instance in the system will periodically poll the preset list and update its own instance status. If it detects that it is in the preset list, it will no longer pull tasks, thereby achieving the goal of stopping the instance to be deleted recorded in the preset list from obtaining tasks.

In one embodiment, after step S102, the method further includes: after the instance recorded in the preset list completes the task, setting the instance status to a disabled state. If it is detected that the instance status is a disabled state, returning a deletion permission indication, and deleting the instance from the system according to the deletion permission indication.

Correspondingly, in step S103, if the instance state is disabled by querying, it is determined that the instance to be deleted is not executing a task, and the instance to be deleted is deleted from the system.

In one implementation, after deleting the instance to be deleted from the system in step S103, the method further includes: setting the state of the instance to a delete state.

Correspondingly, in step S104, by querying that the instances in the machine to be taken offline are all in the delete state, it is determined that all the multiple instances to be deleted are deleted, and then the machine to be taken offline is taken offline from the system.

Optionally, the instance status is queried by calling an instance status query interface of the transcoding system.

In one embodiment, referring to FIG3 , the method further includes:

S301, regularly polling whether each instance to be deleted has been deleted;

S302: For the to-be-deleted instances that have not been deleted, re-execute the process of recording the to-be-deleted instances in a preset list.

The advantage of this processing is that each instance to be deleted is polled regularly to see whether it has been deleted, so that the fallback strategy judgment of step S201 can be called back for the instance that has not been deleted to restart the deletion process for the instance.

In one embodiment, the method further comprises:

When receiving the clearing preset list instruction, clear the instances that are not in the system in the preset list. Optionally, it is possible to set a daily scheduled clearing preset list instruction to perform scheduled clearing of the preset list.

In the scenario where a machine goes offline, the deleted instances will always be recorded in the preset list, releasing the offline instances to prevent the accumulation of too many blacklisted instances in the system, which would affect the normal offline of subsequent instances.

In addition, considering that some instances to be deleted may be recorded in the preset list, some of the instances recorded are instances to be deleted. Therefore, setting a cleanup strategy for deleting records of instances in the preset list that are not in the system can avoid accidental deletion of records of instances to be deleted.

Taking the implementation of an audio transcoding system as an example, an example of an embodiment of the present application is given.

Step 1: Receive a machine exit operation request, i.e., a machine offline request. A machine exit task can be generated based on the machine exit operation request. Provide a general machine exit operation interface or application programming interface (API), and call the API interface/operate through the interface before the operation. The main parameters of the application programming interface are: operation object (machine to be exited) and operation initiator identity.

Step 2: Decompose the machine exit task: obtain each instance on the operation object according to the operation object, and generate offline subtasks corresponding to each instance.

Refer to Figure 4, which is an example diagram of the machine exit process. After the machine exit task is initiated, the instance exit task 1 on the machine, the instance exit task 2 on the machine, and the machine instance exit task n corresponding to each instance are triggered. In addition, the instance offline callback task in the figure refers to the callback of the corresponding instance exit task on the machine, and the callback refers to the re-execution of the machine instance exit task. For example, instance offline callback task 1 corresponds to the callback of instance exit task 1 on the machine, instance offline callback task 2 corresponds to the callback of instance exit task 2 on the machine, and ..., instance offline callback task n corresponds to the callback of instance exit task n on the machine.

In conjunction with FIG. 5 , the following steps 2-0 to 2-4 are described by taking an instance executing a round of instance offline callback tasks as an example.

Callback starts;

Step 2-0: Periodically poll whether it is allowed (ALLOWED) to delete the instance from the audio transcoding system; if deletion is not allowed, execute the fallback policy judgment of step 2-1; if deletion is allowed, after deleting the instance, execute step 2-4 to check whether the deletion is successful;

Step 2-1: Perform a bottom-line strategy judgment on the current audio transcoding system. The bottom-line strategy judgment includes whether the current total central processing unit (CPU) and total memory of the current audio transcoding system after the instance goes offline meet the operation requirements of the current audio transcoding system, whether the ratio of blacklisted instances to total instances in the current audio transcoding system meets the preset requirements, whether the number of offline operations of the current audio transcoding system meets the preset threshold, etc.;

Step 2-2: If the bottom-line strategy is met, call the instance blacklisting interface of the audio transcoding system to blacklist the instance, that is, record the instance in the blacklist. At this time, in the transcoding system, each instance in each transcoding cluster (such as transcoding cluster 1, ..., transcoding cluster n) will periodically poll the blacklist and update its own instance status. If the instance detects that it is on the blacklist, it will no longer pull the transcoding task into the task queue, and after completing the currently executed task, the instance status will be set to a disabled state.

If the fallback strategy is not met, a REJECT message is returned to indicate the end of the current round of instance offline callback task.

Step 2-3: If the instance fails to be blacklisted, a REJECT indication is returned to end the current round of instance offline callback task; if the instance is blacklisted successfully, the instance status query API of the audio transcoding system is called to detect the instance status. If the instance status is detected to be disabled, an ALLOWED indication is returned. When the ALLOWED indication is received in the regular polling of step 2-0, the instance can be deleted; otherwise, a REJECT indication is returned to end the current round of instance offline callback task.

Step 2-4: Check whether the instance is deleted successfully. If it is deleted successfully, update the instance status in the machine to the DELETE status, and end the current round of instance offline callback task. If it is not deleted successfully, update the instance status in the machine to the UNKNOW status.

Step 3: Return to Figure 4, and periodically poll whether all callback tasks are successfully completed, that is, periodically poll the status of each instance of the subtask. If the status of all instances changes to the deleted state, the machine is operated offline, that is, the machine exits; otherwise, for each instance whose status is not the deleted state, the instance exit task is re-called (that is, the above steps 2-0 to 2-4) until the instance status changes to the deleted state.

In addition, this example also provides an instance blacklist cleanup strategy: obtain all current instances in the audio transcoding system, and unblacklist instances that are in the blacklist but not in the audio transcoding system. In the scenario where the machine is offline, blacklist instances, and deleted instances will remain in the blacklist. Consider blacklisting at a fixed time every day to release offline instances to prevent the number of blacklisted instances in the system from accumulating too many instances, which will affect the subsequent instances from being able to go offline normally.

The machine offline method provided in the embodiment of the present application can not only ensure that the service efficiency of the online system is not affected, such as the transcoding efficiency of the transcoding system, but also avoid the risk of insufficient cluster resources due to too many machine withdrawals.

According to an embodiment of the present application, the present application further provides a offline device, as shown in FIG6 , comprising:

An instance determination module 61 is used to determine that multiple instances in the machine to be taken offline are multiple instances to be deleted;

A recording module 62, used for recording multiple instances to be deleted in a preset list, and stopping the acquisition task for the instances to be deleted recorded in the preset list;

A deleting module 63, configured to delete the instance to be deleted from the system if the instance to be deleted recorded in the preset list is not executing a task;

The offline module 64 is used to offline the machine to be offline from the system after all the multiple instances to be deleted in the machine to be offline are deleted.

As shown in FIG7 , in one embodiment, the offline device further includes:

The fallback strategy judgment module 75 is used to judge whether the system satisfies the preset fallback strategy when assuming that the instance to be deleted is deleted; if the preset fallback strategy is satisfied, the recording module is executed.

In one embodiment, wherein

The default fallback strategy includes at least one of the following:

The system configuration of the system meets the normal operation requirements;

The proportion of instances recorded in the preset list in the system is less than the preset ratio;

The number of machine offline times within the preset time does not exceed the preset number.

In one embodiment, the offline device further comprises:

The timing polling module 76 is used for timing polling whether each to-be-deleted instance has been deleted; for the to-be-deleted instance that has not been deleted, the recording module 62 is re-executed.

In one embodiment, the offline device further comprises:

The cleaning module 77 is used to clean up the instances in the preset list that are not in the system when receiving an instruction to clean up the preset list.

In one implementation, multiple instances in the machine to be taken offline are used to execute at least one of an audio transcoding task and a video transcoding task.

According to an embodiment of the present application, the present application also provides an electronic device, a readable storage medium and a computer program product.

As shown in Figure 8, it is a block diagram of an electronic device according to the method of going offline of an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples, and are not intended to limit the implementation of the present application described herein and/or required.

As shown in Figure 8, the electronic device includes: one or more processors 801, memory 802, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input/output device (such as a display device coupled to the interface). In other embodiments, if necessary, multiple processors and/or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor cluster). In Figure 8, a processor 801 is taken as an example.

The memory 802 is a non-transient computer-readable storage medium provided in the present application. The memory stores instructions executable by at least one processor to enable the at least one processor to perform the offline method provided in the present application. The non-transient computer-readable storage medium of the present application stores computer instructions, which are used to enable a computer to perform the offline method provided in the present application.

The memory 802, as a non-transient computer-readable storage medium, can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions/modules corresponding to the offline method in the embodiment of the present application (for example, the instance determination module 61, the recording module 62, the deletion module 63 and the offline module 64 shown in FIG. 6). The processor 801 executes various functional applications and data processing of the server by running the non-transient software programs, instructions and modules stored in the memory 802, that is, implements the offline method in the above method embodiment.

The memory 802 may include a program storage area and a data storage area, wherein the program storage area may store the application programs required for the operation cluster and at least one function; the data storage area may store data created according to the use of the offline electronic device, etc. In addition, the memory 802 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 802 may optionally include a memory remotely arranged relative to the processor 801, and these remote memories may be connected to the offline electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The electronic device of the offline method may further include: an input device 803 and an output device 804. The processor 801, the memory 802, the input device 803 and the output device 804 may be connected via a bus or other means, and FIG8 takes the bus connection as an example.

The input device 803 can receive input digital or character information, and generate key signal input related to user settings and function control of offline electronic devices, such as touch screen, keypad, mouse, track pad, touch pad, indicator bar, one or more mouse buttons, trackball, joystick and other input devices. The output device 804 may include a display device, an auxiliary lighting device (e.g., LED) and a tactile feedback device (e.g., a vibration motor), etc. The display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display and a plasma display. In some embodiments, the display device may be a touch screen.

Various implementations of the clusters and techniques described herein can be implemented in digital electronic circuit clusters, integrated circuit clusters, dedicated ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and/or interpreted on a programmable cluster including at least one programmable processor, which can be a dedicated or general purpose programmable processor that can receive data and instructions from a storage cluster, at least one input device, and at least one output device, and transmit data and instructions to the storage cluster, the at least one input device, and the at least one output device.

These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for programmable processors and can be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and/or means (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and/or data to a programmable processor.

To provide interaction with a user, the cluster and techniques described herein may be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

The clusters and techniques described herein may be implemented in a computing cluster that includes backend components (e.g., as data servers), or a computing cluster that includes middleware components (e.g., application servers), or a computing cluster that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the clusters and techniques described herein), or a computing cluster that includes any combination of such backend components, middleware components, or frontend components. The components of the cluster may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

A computer cluster may include clients and servers. The clients and servers are generally remote from each other and usually interact through a communication network. The client-server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and virtual private servers (VPS) services.

It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution disclosed in this application can be achieved, and this document is not limited here.

The machine offline method provided in the embodiment of the present application can not only ensure that the online service efficiency of the system is not affected, but also avoid the risk of insufficient cluster resources caused by too many machines being offline.

The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims (11)

1. A method of offline comprising:

determining a plurality of instances in a machine to be offline as a plurality of instances to be deleted, wherein the machine to be offline is determined by receiving a machine offline request and according to the machine offline request;

Recording the plurality of to-be-deleted examples in a preset list, so that the examples in the system poll the preset list at regular time, and if the to-be-deleted examples recorded in the preset list are detected to be in the preset list, the to-be-deleted examples are not pulled to acquire tasks any more, wherein the to-be-deleted examples recorded in the preset list stop acquiring tasks;

if the to-be-deleted instance recorded in the preset list is not executing the task, deleting the to-be-deleted instance from the system;

After all the plurality of instances to be deleted in the machine to be offline are deleted, the machine to be offline is offline from the system;

Before the to-be-deleted instance is recorded in the preset list, the method further comprises:

under the condition that the to-be-deleted instance is supposed to be deleted, judging whether the system meets a preset spam strategy or not;

If the preset spam strategy is met, executing the record to-be-deleted instance in the preset list;

Further comprises:

and when a preset list clearing instruction is received, clearing the examples which are not in the system in the preset list.

2. The method of claim 1, wherein,

The preset bottom-covering strategy comprises at least one of the following steps:

the system configuration of the system meets the normal operation requirement;

the ratio of the examples recorded in the preset list in the system is smaller than a preset proportion;

The machine offline times of the system in the preset time do not exceed the preset times.

3. The method of claim 1, further comprising:

polling whether each instance to be deleted is deleted or not at regular time;

and for the instance to be deleted which is not deleted, re-executing the record of the instance to be deleted in a preset list.

4. A method according to any of claims 1-3, wherein multiple instances in the machine to be offline are used to perform at least one of an audio transcoding task and a video transcoding task.

5. An offline device, comprising:

the system comprises an instance determining module, a processing module and a processing module, wherein the instance determining module is used for determining a plurality of instances in a machine to be offline as a plurality of instances to be deleted, and the machine to be offline is used for receiving a machine offline request and determining according to the machine offline request;

The recording module is used for recording the plurality of to-be-deleted examples in a preset list so as to enable the examples in the system to poll the preset list at regular time, and if the to-be-deleted examples recorded in the preset list stop acquiring tasks if the to-be-deleted examples are detected to be in the preset list;

the deleting module is used for deleting the to-be-deleted instance recorded in the preset list from the system if the to-be-deleted instance is not executing the task;

the offline module is used for offline the offline machine from the system after all the plurality of instances to be deleted in the offline machine are deleted;

Further comprises:

The spam policy judging module is used for judging whether the system meets a preset spam policy under the condition that the to-be-deleted instance is supposed to be deleted; if the preset spam strategy is met, executing the recording module;

and the cleaning module is used for cleaning the examples which are not in the system in the preset list when receiving the instruction for cleaning the preset list.

6. The apparatus of claim 5, wherein,

The preset bottom-covering strategy comprises at least one of the following steps:

the system configuration of the system meets the normal operation requirement;

the ratio of the examples recorded in the preset list in the system is smaller than a preset proportion;

The machine offline times of the system in the preset time do not exceed the preset times.

7. The apparatus of claim 5, further comprising:

the timing polling module is used for periodically polling whether each instance to be deleted is deleted or not; and re-executing the recording module for the instance to be deleted which is not deleted.

8. The apparatus of any of claims 5-7, wherein multiple instances in the machine to be offline are to perform at least one of an audio transcoding task and a video transcoding task.

9. An electronic device, comprising:

At least one processor; and

A memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4.

10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-4.

11. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-4.