WO2010122710A1 - 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 - Google Patents
若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 Download PDFInfo
- Publication number
- WO2010122710A1 WO2010122710A1 PCT/JP2010/001832 JP2010001832W WO2010122710A1 WO 2010122710 A1 WO2010122710 A1 WO 2010122710A1 JP 2010001832 W JP2010001832 W JP 2010001832W WO 2010122710 A1 WO2010122710 A1 WO 2010122710A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rejuvenation
- host
- virtual
- machine
- machines
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/203—Failover techniques using migration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/815—Virtual
Definitions
- the present invention is a rejuvenation processing apparatus for integrated control of a plurality of host machines, and in particular, a rejuvenation process for integrated control of a plurality of host machines each including hardware in which at least one virtual machine is operating by software.
- the present invention relates to an apparatus, a rejuvenation processing system having the rejuvenation processing apparatus, a computer program of the rejuvenation processing apparatus, and a data processing method.
- the virtualization software is software for generating and operating a plurality of virtual machines on a host machine, and high reliability is required for stable operation of the virtual machine.
- An aging bug is a bug that causes performance degradation or failure due to continuous operation for a long time.
- Software rejuvenation is known as an effective solution to aging bugs. This is a technique to avoid failures by resetting the internal state and operating environment of aged software. Since software rejuvenation causes downtime in the rejuvenation process itself, it is necessary to schedule rejuvenation at an appropriate timing and interval.
- Patent Document 1 there is a technique for avoiding a failure by executing a rejuvenation process periodically based on the operating time of software (see, for example, Patent Document 1). There is also a technique for monitoring the operation of an application and restarting the process to normalize the operation (see, for example, Patent Document 2).
- JP 2001-188684 A Japanese Patent Laid-Open No. 08-095814
- virtual machine rejuvenation can unnecessarily increase virtual machine downtime.
- the reason is that the virtual machine and the application running on the virtual machine each have an appropriate rejuvenation timing and do not always coincide with the rejuvenation timing of the virtualization software.
- the present invention has been made in view of the above-described problems.
- the rejuvenation processing apparatus of the present invention is a rejuvenation processing apparatus that controls a plurality of host machines in which virtual machines are operating, and selects at least one host machine as a rejuvenation target from each host machine.
- the virtual migration means to migrate the virtual machine running on the host machine selected for rejuvenation to the host machine where the virtual machine was running, and the host selected for rejuvenation Rejuvenation execution means for rejuvenating the machine.
- the rejuvenation processing system of the present invention includes a plurality of host machines on which virtual machines are operating, host rejuvenation scheduling means for selecting at least one host machine as a rejuvenation target from each host machine, rejuvenation Virtual rejuvenation scheduling means to select at least one virtual machine from the virtual machines running on the host machine that was not selected as the target of the operation, and the selected virtual machine is stopped and the virtual machine is running
- host rejuvenation scheduling means for selecting at least one host machine as a rejuvenation target from each host machine
- rejuvenation Virtual rejuvenation scheduling means to select at least one virtual machine from the virtual machines running on the host machine that was not selected as the target of the operation, and the selected virtual machine is stopped and the virtual machine is running
- a virtual migration means for migrating a virtual machine running on a host machine selected for rejuvenation to a host machine that has been rejuvenated
- a rejuvenation execution means for rejuvenating a host machine selected for rejuvenation And having.
- the computer program of the present invention is a computer program of a rejuvenation processing apparatus that controls a plurality of host machines on which virtual machines are operating, and selects at least one host machine as a rejuvenation target from each host machine Host rejuvenation scheduling processing, virtual rejuvenation scheduling processing for selecting at least one virtual machine from among virtual machines running on host machines that were not selected for rejuvenation, and for the selected virtual machines
- Host rejuvenation scheduling processing virtual rejuvenation scheduling processing for selecting at least one virtual machine from among virtual machines running on host machines that were not selected for rejuvenation, and for the selected virtual machines
- a virtual migration process that migrates a virtual machine running on a host machine selected for rejuvenation to a host machine where the virtual machine was running and selected for rejuvenation. Rejuvenation execution processing to rejuvenate the host machine and That.
- the data processing method of the present invention is a data processing method of a rejuvenation processing apparatus that controls a plurality of host machines on which virtual machines are operating, and includes at least one host machine as an object of rejuvenation from each host machine
- a host rejuvenation scheduling operation that selects a virtual machine
- a virtual rejuvenation scheduling operation that selects at least one virtual machine from virtual machines running on a host machine that has not been selected as a rejuvenation target, and a selected virtual machine. Stop the machine and select the virtual migration operation that migrates the virtual machine running on the host machine selected for rejuvenation to the host machine that the virtual machine was running on, and the rejuvenation target Rejuvenation execution operation for rejuvenating a host machine that has been reconfigured.
- the various components of the present invention need only be formed so as to realize their functions.
- dedicated hardware that exhibits a predetermined function, rejuvenation provided with a predetermined function by a computer program It can be realized as a processing device, a predetermined function realized in the rejuvenation processing device by a computer program, an arbitrary combination thereof, or the like.
- a plurality of components are formed as a single member, and a single component is formed of a plurality of members. It may be that a certain component is a part of another component, a part of a certain component overlaps with a part of another component, or the like.
- the order of the plurality of processes and the plurality of operations can be changed within a range that does not hinder the contents.
- the computer program and the data processing method of the present invention are not limited to being executed at a timing when a plurality of processes and a plurality of operations are individually different. For this reason, other processes and operations occur during execution of certain processes and operations, and the execution timing of certain processes and operations overlaps with the execution timing of other processes and operations. Etc.
- At least one host machine is selected as a rejuvenation target from among the host machines. Select at least one virtual machine from the virtual machines running on the host machine that was not selected for rejuvenation. The operation of the selected virtual machine is stopped, and the virtual machine running on the host machine selected as the rejuvenation target is migrated to the host machine on which the virtual machine was running. Rejuvenate the host machine selected for rejuvenation. For this reason, it is not necessary to stop together the virtual machines that are running when the host machine is rejuvenated and need not be rejuvenated. Therefore, it is possible to rejuvenate a host machine that needs to be rejuvenated while continuously operating a host machine and a virtual machine that do not need to be rejuvenated.
- a rejuvenation processing system includes a management server 1 that is a rejuvenation processing device that operates under program control, a communication network 2, a plurality of host machines 3, and a network storage device. 5.
- the management server 1 is connected to a plurality of host machines 3 via a communication network 2.
- the plurality of host machines 3 share the network storage device 5.
- the plurality of host machines 3 are composed of hardware in which at least one virtual machine 302 is operated by virtualization software 301 that is software.
- the management server 1 integrally controls the plurality of host machines 3 as described above.
- the management server 1 includes a host machine rejuvenation schedule 104 that is a host rejuvenation scheduling means for selecting at least one host machine 3 as a rejuvenation target from among the host machines 3, and a rejuvenation schedule.
- a virtual machine rejuvenation schedule 105 which is a virtual rejuvenation scheduling means for selecting at least one virtual machine 302 from among virtual machines 302 running on a host machine 3 that has not been selected as a target for rejuvenation, and a selected virtual machine Migration that is a virtual migration means for stopping the operation of the machine 302 and migrating the virtual machine 302 running on the host machine 3 selected as the rejuvenation target to the host machine 3 on which the virtual machine 302 was running
- It has a rejuvenation execution management function 107 is a rejuvenation execution means for rejuvenation, the host machine 3 which.
- the host machine rejuvenation schedule 104 selects each host machine 3 to be rejuvenated by determining each aging state individually.
- the virtual machine rejuvenation schedule 105 selects the virtual machine 302 to be rejuvenated and the virtual machine 302 not to rejuvenate by individually determining each aging state.
- the management server 1 also has an aging characteristic 102 in which aging characteristics are registered in advance for each of the plurality of host machines 3, and the host machine rejuvenation schedule 104 corresponds to the registered aging characteristics.
- the host machine 3 to be rejuvenated is selected, and the virtual machine rejuvenation schedule 105 selects the virtual machine 302 to be rejuvenated corresponding to the registered aging characteristics.
- the management server 1 includes the virtual machine arrangement configuration 101, the rejuvenation schedule generation function 103, the host machine start / stop control function 108, and the virtual machine start / stop control function 109 in addition to the above-described units. And a virtual machine migration control function 110.
- the plurality of host machines 3 are connected in parallel to the communication network 2, for example, and each include at least one virtualization software 301 and at least one or more virtual machines 302 thereby. These components generally operate as follows.
- the rejuvenation schedule generation function 103 reads the virtual machine arrangement configuration 101 and the aging characteristic 102, generates a host machine rejuvenation schedule 104, a virtual machine rejuvenation schedule 105, and a migration schedule 106.
- the host machine rejuvenation schedule 104, virtual machine The rejuvenation schedule 105 and the migration schedule 106 are stored.
- the rejuvenation execution management function 107 calls the host machine start / stop control function 108, the virtual machine start / stop control function 109, and the virtual machine migration control function 110 based on the generated schedule information, and performs the virtualization software 301 and the virtual The machine 302 is operated.
- the host machine start / stop control function 108 starts / stops the virtualization software 301 of the host machine 3 via the communication network 2.
- Activation / deactivation of the virtualization software 301 corresponds to activation / deactivation of the host machine 3.
- the virtual machine start / stop control function 109 operates to start / stop the virtual machine 302 via the communication network 2. All images of the virtual machine 302 are stored in the network storage device 5 and can be referred to from all the host machines 3.
- the virtual machine migration control function 110 operates the virtualization software 301 via the communication network 2 and migrates the virtual machine 302 to another host machine 3.
- the virtual machine 302 is temporarily stopped by the migration of the virtual machine 302, but the time required for the migration is very short compared to the restart time.
- the computer program of the management server 1 as described above is, for example, a host rejuvenation scheduling process for selecting at least one host machine 3 as a rejuvenation target from among the host machines 3 and a rejuvenation target.
- the virtual rejuvenation scheduling process for selecting at least one virtual machine 302 from the virtual machines 302 operating on the host machine 3 that has not been performed, and the operation of the selected virtual machine 302 are stopped.
- a virtual migration process for migrating the virtual machine 302 running on the host machine 3 selected as the rejuvenation target to the host machine 3 that was running, and the rejuvenation of the host machine 3 selected as the rejuvenation target Rejuvenation execution processing to be executed is described to be executed by the management server 1
- the rejuvenation schedule generation function 103 refers to the virtual machine arrangement configuration 101 and the aging characteristic 102 (steps 3000 and 3001 in FIG. 2).
- An example of the virtual machine arrangement configuration 101 is shown in FIG. In the configuration of FIG. 3, there are three host machines 3, and a total of six virtual machines 302 are hosted.
- the rejuvenation schedule generation function 103 creates a rejuvenation schedule for the host machine 3 based on the given virtual machine arrangement configuration 101 and the aging characteristics 102 (step 3002).
- step 3003 Schedule each host machine 3 not to stop at the same time.
- An example of the rejuvenation schedule of the host machine 3 is shown in FIG. Next, or simultaneously with step 3002, a rejuvenation schedule for the virtual machine 302 is created (step 3003).
- the rejuvenation schedule of the virtual machine 302 created at this stage is a provisional schedule based only on the aging characteristics 102 of the virtual machine 302, and is corrected in the subsequent steps.
- the correction is performed by sequentially adjusting the save destination of the virtual machine 302 at the timing of rejuvenation of each host machine 3 based on the rejuvenation schedule of the host machine 3. First, the latest rejuvenation timing of the host machine 3 is selected (step 3004).
- the virtual machine 302 operating on the host machine 3 is saved to another host, it is checked whether or not there is a free area on the other host machine 3 at this time. The investigation of the free area needs to be based on the virtual machine arrangement configuration 101 at that time.
- step 3005-Y If sufficient free space is found to save all the virtual machines 302 operating on the rejuvenation target host machine 3 (step 3005-Y), the virtual machine 302 is moved by migration before the host machine 3 is stopped. A schedule to be evacuated is added (step 3009).
- step 3005-N if there is not enough free space (step 3005-N), the virtual machine 302 having the highest risk due to aging (for example, the longest operation time) is selected and stopped. At this time, the selection is performed in consideration of capacity so that the selected virtual machine 302 can operate on one host machine 3 (step 3006).
- a schedule is created so that these virtual machines 302 are started on the host machine 3 (step 3007).
- the virtual machine 302 for which the schedule has been set is operating on a host machine 3 different from the host machine 3 to be rejuvenated, the virtual machine that operates on the host machine 3 in the free area of the stopped virtual machine 302 A migration schedule 106 for saving 302 is added.
- Migration is scheduled after the virtual machine 302 stops and before the host machine 3 stops (steps 3008 and 3009).
- the above procedure is executed in order for the rejuvenation timing of each host machine 3, and the rejuvenation schedule modification of the virtual machine 302 and the migration schedule 106 are repeated (step 3010).
- FIG. 5 shows an example of a rejuvenation schedule in which the host machine 3 and the virtual machine 302 are combined, assuming that there is no free space in the arrangement configuration given in FIG.
- vm04 and vm06 are selected and stopped at the timing of rejuvenating host01
- vm01 and vm03 are selected and stopped at the timing of rejuvenating host02
- vm02 and vm05 are stopped at the timing of stopping host03. Select and stop.
- FIG. 6 shows an example of a state in which a migration schedule for the virtual machine 302 is added to the rejuvenation schedule in FIG.
- vm01 is migrated to host02
- vm02 is migrated to host03.
- the management server 1 of the rejuvenation processing system of the present embodiment selects at least one rejuvenating from a plurality of host machines 3 as described above. At least one virtual machine 302 that is not rejuvenated is selected from the virtual machines 302 that are running on the selected and rejuvenated host machine 3, and is rejuvenated from the virtual machine 302 that is running on the host machine 3 that is not selected and is not rejuvenated. Select at least one to do.
- the virtual machine 302 that is not rejuvenated in the host machine 3 to be rejuvenated and the virtual machine 302 that is rejuvenated in the host machine 3 that is not rejuvenated are migrated to each other.
- the migrated rejuvenated virtual machine 302 is rejuvenated together with the rejuvenated host machine 3.
- the virtual machine 302 that needs to be rejuvenated can be rejuvenated together with the host machine 3 that needs to be rejuvenated, and the virtual machine that is running and does not need to be rejuvenated when the host machine 3 is rejuvenated. There is no need to stop the machines 302 together.
- the host machine 3 and the virtual machine 302 that need to be rejuvenated can be rejuvenated at the same time while continuously operating the host machine 3 and the virtual machine 302 that do not need to be rejuvenated.
- the present invention is not limited to the present embodiment, and various modifications are allowed without departing from the scope of the present invention.
- the aging characteristic 102 is registered for each of the plurality of host machines 3 in advance, and the host machine rejuvenation schedule 104 corresponds to the aging characteristic as shown in FIG. An example of selecting a host machine 3 to be realized is shown.
- the host machine rejuvenation schedule 104 has an aging characteristic 102 for detecting and recording an aging state in real time for each of a plurality of host machines 3, and the host machine rejuvenation schedule 104 selects a host machine 3 to be rejuvenated corresponding to the recorded aging state. You may choose.
- the management server 1 further includes an aging state 112 and a resource usage / configuration monitoring function 111 as components.
- the configuration and aging state of the virtual machine 302 and the host machine 3 are continuously monitored, and the rejuvenation schedule is dynamically changed based on the monitoring result.
- the rejuvenation schedule generation function 103 generates a host machine rejuvenation schedule 104, a virtual machine rejuvenation schedule 105, and a migration schedule 106 in accordance with the rejuvenation schedule generation method described in the first embodiment.
- the operation is started based on the generated schedule, and at the same time, the resource usage / configuration monitoring function is used to monitor the resource usage / configuration information (steps 4000 and 4001 in FIG. 8).
- step 4003 data that may be aged with data such as resource usage is recorded in the aging state 112 (step 4002). If it becomes clear from the monitoring that the arrangement of the virtual machine 302 has changed, the virtual machine arrangement configuration 101 is updated (step 4003).
- the rejuvenation schedule is regenerated so that the component in which aging is in progress is rejuvenated soon (step 4004-Y, 4006).
- aging may accelerate and proceed due to concentration of requests even for a short time.
- ⁇ ⁇ Detect such a condition and use it as a trigger to regenerate the rejuvenation schedule. Also, when an unscheduled configuration change other than the migration scheduled in advance is detected, the rejuvenation schedule is similarly regenerated (steps 4005-Y and 4006).
- the rejuvenation schedule is regenerated when a new virtual machine 302 or host machine 3 is additionally activated, or when the arrangement configuration of the virtual machine 302 is changed by migration for the purpose of load balancing or the like.
- the rejuvenation schedule obtained by the regeneration is stored in the host machine rejuvenation schedule 104, the virtual machine rejuvenation schedule 105, and the migration schedule 106, respectively (step 4007), and the schedule operation is continued by the rejuvenation execution management function 107. . If there is no need to reschedule, continue monitoring.
- the rejuvenation processing system as described above is configured to monitor resource usage, detect an unexpected aging progress state, and regenerate the rejuvenation schedule. Therefore, aging is caused by factors other than elapsed time. It can respond dynamically to the situation as it progresses.
- the configuration information is further monitored to detect an unexpected change in the virtual machine arrangement configuration 101, and the rejuvenation schedule is regenerated.
- the rejuvenation schedule can be changed dynamically in an environment where functions such as automatic relocation of the virtual machine 302 for the purpose of adding a host machine 3 or virtual machine 302 or load balancing by the system administrator operate. Yes.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
- Hardware Redundancy (AREA)
Abstract
Description
Claims (10)
- 仮想マシンが稼働している複数のホストマシンを制御する若化処理装置であって、
前記各ホストマシンの中から若化の対象として少なくとも一個の前記ホストマシンを選定するホスト若化スケジューリング手段と、
前記若化の対象として選定されなかった前記ホストマシンで稼働している前記仮想マシンの中から少なくとも一つの前記仮想マシンを選定する仮想若化スケジューリング手段と、
選定された前記仮想マシンの稼動を停止し、当該仮想マシンが稼動していた前記ホストマシンに、若化の対象として選定された前記ホストマシンで稼動している前記仮想マシンをマイグレーションする仮想マイグレーション手段と、
前記若化の対象として選定された前記ホストマシンを若化する若化実行手段と、
を有する若化処理装置。 - 前記ホスト若化スケジューリング手段は、各々のエージング状態を個別に判定して若化する前記ホストマシンを選定する請求項1に記載の若化処理装置。
- 複数の前記ホストマシンごとにエージング特性が事前に登録されているエージング管理手段を、さらに有し、
前記ホスト若化スケジューリング手段は、前記エージング特性に対応して若化する前記ホストマシンを選定する請求項2に記載の若化処理装置。 - 複数の前記ホストマシンごとに前記エージング状態をリアルタイムに検出して記録するエージング管理手段を、さらに有し、
前記ホスト若化スケジューリング手段は、記録された前記エージング状態に対応して若化する前記ホストマシンを選定する請求項2に記載の若化処理装置。 - 前記仮想若化スケジューリング手段は、各々のエージング状態を個別に判定して若化する前記仮想マシンと若化しない前記仮想マシンとを選定する請求項1ないし4の何れか一項に記載の若化処理装置。
- 複数の前記仮想マシンごとにエージング特性が事前に登録されているエージング管理手段を、さらに有し、
前記仮想若化スケジューリング手段は、前記エージング特性に対応して若化する前記仮想マシンを選定する請求項5に記載の若化処理装置。 - 複数の前記仮想マシンごとに前記エージング状態をリアルタイムに検出して記録するエージング管理手段を、さらに有し、
前記仮想若化スケジューリング手段は、記録された前記エージング状態に対応して若化する前記仮想マシンと若化しない前記仮想マシンとを選定する請求項5に記載の若化処理装置。 - 仮想マシンが稼働している複数のホストマシンと、
前記各ホストマシンの中から若化の対象として少なくとも一個の前記ホストマシンを選定するホスト若化スケジューリング手段と、
前記若化の対象として選定されなかった前記ホストマシンで稼働している前記仮想マシンの中から少なくとも一つの前記仮想マシンを選定する仮想若化スケジューリング手段と、
選定された前記仮想マシンの稼動を停止し、当該仮想マシンが稼動していた前記ホストマシンに、若化の対象として選定された前記ホストマシンで稼動している前記仮想マシンをマイグレーションする仮想マイグレーション手段と、
前記若化の対象として選定された前記ホストマシンを若化する若化実行手段と、
を有する若化処理システム。 - 仮想マシンが稼働している複数のホストマシンを制御する若化処理装置のコンピュータプログラムであって、
前記各ホストマシンの中から若化の対象として少なくとも一個の前記ホストマシンを選定するホスト若化スケジューリング処理と、
前記若化の対象として選定されなかった前記ホストマシンで稼働している前記仮想マシンの中から少なくとも一つの前記仮想マシンを選定する仮想若化スケジューリング処理と、
選定された前記仮想マシンの稼動を停止し、当該仮想マシンが稼動していた前記ホストマシンに、若化の対象として選定された前記ホストマシンで稼動している前記仮想マシンをマイグレーションする仮想マイグレーション処理と、
前記若化の対象として選定された前記ホストマシンを若化する若化実行処理と、
を若化処理装置に実行させるコンピュータプログラム。 - 仮想マシンが稼働している複数のホストマシンを制御する若化処理装置のデータ処理方法であって、
前記各ホストマシンの中から若化の対象として少なくとも一個の前記ホストマシンを選定するホスト若化スケジューリング動作と、
前記若化の対象として選定されなかった前記ホストマシンで稼働している前記仮想マシンの中から少なくとも一つの前記仮想マシンを選定する仮想若化スケジューリング動作と、
選定された前記仮想マシンの稼動を停止し、当該仮想マシンが稼動していた前記ホストマシンに、若化の対象として選定された前記ホストマシンで稼動している前記仮想マシンをマイグレーションする仮想マイグレーション動作と、
前記若化の対象として選定された前記ホストマシンを若化する若化実行動作と、
を有するデータ処理方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/260,659 US8789045B2 (en) | 2009-04-23 | 2010-03-15 | Rejuvenation processing device, rejuvenation processing system, computer program, and data processing method |
JP2011510160A JP5403051B2 (ja) | 2009-04-23 | 2010-03-15 | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009104695 | 2009-04-23 | ||
JP2009-104695 | 2009-04-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010122710A1 true WO2010122710A1 (ja) | 2010-10-28 |
Family
ID=43010840
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/001832 WO2010122710A1 (ja) | 2009-04-23 | 2010-03-15 | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US8789045B2 (ja) |
JP (1) | JP5403051B2 (ja) |
WO (1) | WO2010122710A1 (ja) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010122709A1 (ja) | 2009-04-23 | 2010-10-28 | 日本電気株式会社 | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 |
US10542049B2 (en) | 2014-05-09 | 2020-01-21 | Nutanix, Inc. | Mechanism for providing external access to a secured networked virtualization environment |
CN104035542B (zh) * | 2014-05-28 | 2017-06-06 | 中国科学院计算技术研究所 | 一种计算与制冷能耗权衡的虚拟机迁移方法及系统 |
US10095506B2 (en) | 2016-02-12 | 2018-10-09 | Nutanix, Inc. | Virtualized file server data sharing |
US11218418B2 (en) | 2016-05-20 | 2022-01-04 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
US11562034B2 (en) | 2016-12-02 | 2023-01-24 | Nutanix, Inc. | Transparent referrals for distributed file servers |
US10824455B2 (en) | 2016-12-02 | 2020-11-03 | Nutanix, Inc. | Virtualized server systems and methods including load balancing for virtualized file servers |
US10728090B2 (en) | 2016-12-02 | 2020-07-28 | Nutanix, Inc. | Configuring network segmentation for a virtualization environment |
US11568073B2 (en) | 2016-12-02 | 2023-01-31 | Nutanix, Inc. | Handling permissions for virtualized file servers |
US11294777B2 (en) | 2016-12-05 | 2022-04-05 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
US11281484B2 (en) | 2016-12-06 | 2022-03-22 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
US11288239B2 (en) | 2016-12-06 | 2022-03-29 | Nutanix, Inc. | Cloning virtualized file servers |
US11086826B2 (en) | 2018-04-30 | 2021-08-10 | Nutanix, Inc. | Virtualized server systems and methods including domain joining techniques |
US11194680B2 (en) | 2018-07-20 | 2021-12-07 | Nutanix, Inc. | Two node clusters recovery on a failure |
US11770447B2 (en) | 2018-10-31 | 2023-09-26 | Nutanix, Inc. | Managing high-availability file servers |
US11768809B2 (en) | 2020-05-08 | 2023-09-26 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004030363A (ja) * | 2002-06-27 | 2004-01-29 | Hitachi Ltd | 論理計算機システム、論理計算機システムの構成制御方法および論理計算機システムの構成制御プログラム |
JP2007536657A (ja) * | 2004-05-08 | 2007-12-13 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 仮想マシン・コンピュータ・プログラムの動的マイグレーション |
JP2008217302A (ja) * | 2007-03-02 | 2008-09-18 | Nec Corp | 仮想マシンシステム、管理サーバ、仮想マシン移行方法及びプログラム |
JP2009080704A (ja) * | 2007-09-26 | 2009-04-16 | Toshiba Corp | 仮想計算機システム及び同システムにおけるサービス引き継ぎ制御方法 |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2580061B2 (ja) | 1990-05-15 | 1997-02-12 | 富士通株式会社 | サーバ型プログラムの活性保守処理方法 |
JPH0778037A (ja) | 1993-09-08 | 1995-03-20 | Hitachi Ltd | 分散処理システム |
CA2152329C (en) | 1994-09-08 | 1999-02-09 | N Dudley Fulton Iii | Apparatus and methods for software rejuvenation |
JPH09305218A (ja) | 1996-05-17 | 1997-11-28 | Hitachi Ltd | 予防保全最適化方法およびその装置 |
JP2000222376A (ja) | 1999-01-29 | 2000-08-11 | Toshiba Corp | 計算機システムとその運用方法 |
US6594784B1 (en) * | 1999-11-17 | 2003-07-15 | International Business Machines Corporation | Method and system for transparent time-based selective software rejuvenation |
US6820215B2 (en) | 2000-12-28 | 2004-11-16 | International Business Machines Corporation | System and method for performing automatic rejuvenation at the optimal time based on work load history in a distributed data processing environment |
KR100420266B1 (ko) * | 2001-10-23 | 2004-03-02 | 한국전자통신연구원 | 클러스터 컴퓨터 시스템의 소프트웨어 가용도 개선 방법및 그 장치 |
US7100079B2 (en) | 2002-10-22 | 2006-08-29 | Sun Microsystems, Inc. | Method and apparatus for using pattern-recognition to trigger software rejuvenation |
US20060130044A1 (en) * | 2004-12-01 | 2006-06-15 | Alberto Avritzer | System and method for triggering software rejuvenation using a customer affecting performance metric |
US20060155912A1 (en) | 2005-01-12 | 2006-07-13 | Dell Products L.P. | Server cluster having a virtual server |
US7454661B2 (en) | 2005-10-06 | 2008-11-18 | International Business Machines Corporation | Minimizing software downtime associated with software rejuvenation in a single computer system |
US8042108B2 (en) * | 2006-03-18 | 2011-10-18 | International Business Machines Corporation | Virtual machine migration between servers |
WO2007136021A1 (ja) | 2006-05-24 | 2007-11-29 | Nec Corporation | 仮想マシン管理装置、仮想マシン管理方法およびプログラム |
US8572735B2 (en) | 2007-03-29 | 2013-10-29 | George Mason Research Foundation, Inc. | Attack resistant continuous network service trustworthiness controller |
US8327354B1 (en) | 2007-05-31 | 2012-12-04 | Hewlett-Packard Development Company, L.P. | Virtualization with binary translation |
JP2008299791A (ja) * | 2007-06-04 | 2008-12-11 | Hitachi Ltd | 仮想計算機システム |
US8307177B2 (en) | 2008-09-05 | 2012-11-06 | Commvault Systems, Inc. | Systems and methods for management of virtualization data |
US8200771B2 (en) | 2008-10-10 | 2012-06-12 | International Business Machines Corporation | Workload migration using on demand remote paging |
WO2010122709A1 (ja) | 2009-04-23 | 2010-10-28 | 日本電気株式会社 | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 |
US8171349B2 (en) | 2010-06-18 | 2012-05-01 | Hewlett-Packard Development Company, L.P. | Associating a monitoring manager with an executable service in a virtual machine migrated between physical machines |
-
2010
- 2010-03-15 WO PCT/JP2010/001832 patent/WO2010122710A1/ja active Application Filing
- 2010-03-15 JP JP2011510160A patent/JP5403051B2/ja active Active
- 2010-03-15 US US13/260,659 patent/US8789045B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004030363A (ja) * | 2002-06-27 | 2004-01-29 | Hitachi Ltd | 論理計算機システム、論理計算機システムの構成制御方法および論理計算機システムの構成制御プログラム |
JP2007536657A (ja) * | 2004-05-08 | 2007-12-13 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 仮想マシン・コンピュータ・プログラムの動的マイグレーション |
JP2008217302A (ja) * | 2007-03-02 | 2008-09-18 | Nec Corp | 仮想マシンシステム、管理サーバ、仮想マシン移行方法及びプログラム |
JP2009080704A (ja) * | 2007-09-26 | 2009-04-16 | Toshiba Corp | 仮想計算機システム及び同システムにおけるサービス引き継ぎ制御方法 |
Also Published As
Publication number | Publication date |
---|---|
JP5403051B2 (ja) | 2014-01-29 |
US20120023495A1 (en) | 2012-01-26 |
US8789045B2 (en) | 2014-07-22 |
JPWO2010122710A1 (ja) | 2012-10-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5403051B2 (ja) | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 | |
JP5861733B2 (ja) | 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法 | |
EP2614436B1 (en) | Controlled automatic healing of data-center services | |
US8464092B1 (en) | System and method for monitoring an application or service group within a cluster as a resource of another cluster | |
US7653833B1 (en) | Terminating a non-clustered workload in response to a failure of a system with a clustered workload | |
JP5851503B2 (ja) | 高可用性仮想機械環境におけるアプリケーションの高可用性の提供 | |
US9558082B2 (en) | VM availability during migration and VM network failures in host computing systems | |
JP5093259B2 (ja) | Biosとbmcとの間の通信パス強化方法、その装置及びそのプログラム | |
WO2015169199A1 (zh) | 分布式环境下虚拟机异常恢复方法 | |
JP2007536657A (ja) | 仮想マシン・コンピュータ・プログラムの動的マイグレーション | |
US20080307254A1 (en) | Information-processing equipment and system therefor | |
JP2008052407A (ja) | クラスタシステム | |
WO2016045439A1 (zh) | 一种vnfm容灾保护的方法、装置和nfvo、存储介质 | |
JP5998577B2 (ja) | クラスタ監視装置、クラスタ監視方法、及びプログラム | |
CN111935244B (zh) | 一种业务请求处理系统及超融合一体机 | |
JP5855724B1 (ja) | 仮想機器管理装置、仮想機器管理方法及び仮想機器管理プログラム | |
CN115167757A (zh) | 加速卡分布式存储访问方法、装置、设备及存储介质 | |
KR20150111608A (ko) | 가상화 서버의 이중화를 위한 제어 방법 및 이를 위한 가상화 제어 장치 | |
CN113596152A (zh) | 负载均衡实现方法、系统及装置 | |
JP2000222376A (ja) | 計算機システムとその運用方法 | |
EP3921729A1 (en) | Hosting virtual machines on a secondary storage system | |
JP7057178B2 (ja) | 管理ノード、ノード、クラスタシステムおよびノード制御方法 | |
CN117421158A (zh) | 数据库故障处理方法、系统及存储介质 | |
KR20240074678A (ko) | 고장 동작 제어 시스템, 고장 동작 제어 방법, 비일시적 컴퓨터 판독 가능 매체 | |
JP2013054605A5 (ja) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10766773 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011510160 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13260659 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10766773 Country of ref document: EP Kind code of ref document: A1 |