CN111949287A - Software upgrading method and device - Google Patents
Software upgrading method and device Download PDFInfo
- Publication number
- CN111949287A CN111949287A CN201910410061.8A CN201910410061A CN111949287A CN 111949287 A CN111949287 A CN 111949287A CN 201910410061 A CN201910410061 A CN 201910410061A CN 111949287 A CN111949287 A CN 111949287A
- Authority
- CN
- China
- Prior art keywords
- management component
- metadata management
- version
- file metadata
- file
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure provides a software upgrading method and device, and relates to the field of computers. According to the method and the device, the characteristic description and the characteristic version configuration related to the metadata are changed, and the analysis logic of the management file maintained by the file metadata management component is modified, so that the new version software can analyze the management file in a corresponding version format according to the version of the management file, and the new version and the old version of the management file can be compatibly analyzed.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a method and an apparatus for upgrading software.
Background
Hadoop (an open source software) is widely used for storage and computation of large data. Compared with the old version of Hadoop software (such as Hadoop2.x), the new version of Hadoop software (such as Hadoop3.x) is added with an Erasure Code (EC) function, and the memory reduction function can be realized.
After some enterprises upgrade old-version Hadoop software to new-version Hadoop software, the enterprises find that the new-version Hadoop software cannot analyze management files (called metadata management files for short) maintained by a file metadata management component of the old-version Hadoop software, such as log files (Editlog) and directory mirror files (FsImage).
Disclosure of Invention
In view of this, the present disclosure may compatibly analyze the management files of the new version and the old version by changing the property description and the property version configuration related to the metadata and modifying the analysis logic of the management file maintained by the file metadata management component, so that the new version software performs analysis of the corresponding version format on the management file according to the version of the management file.
Some embodiments of the present disclosure provide a software upgrading method, including:
upgrading a file metadata management component of software to enable the file metadata management component to support a preset characteristic, wherein the preset characteristic is a characteristic that a second version is increased relative to a first version in characteristic versions supported by the file metadata management component;
deleting the description of the preset property from the property descriptions supported by the file metadata management component;
configuring the property version supported by the file metadata management component into a first version according to the property description supported by the file metadata management component;
and under the condition that the characteristic version supported by the file metadata management component is the first version, analyzing the corresponding version format of the management file according to the version number of the management file maintained by the read file metadata management component.
In some embodiments, when the version number of the management file maintained by the file metadata management component is a first version, no read operation is performed on the field related to the preset characteristic; and when the version number of the management file maintained by the file metadata management component is a second version, performing read operation on the field related to the preset characteristic.
In some embodiments, further comprising: and determining whether to execute write operation on the fields related to the preset characteristics according to the version number of the preset configuration item configuration.
In some embodiments, when the configuration item is configured as the first version, no write operation is performed on the preset property-related field; when the configuration item is configured to be the second version, writing operation is performed on the field related to the preset characteristic.
In some embodiments, the file metadata management components upgraded to support the preset characteristic include at least a first file metadata management component and a second file metadata management component in a master-slave mode,
upgrading a first file metadata management assembly in a slave service state at present, upgrading the first file metadata management assembly in the slave service state at present to enable the first file metadata management assembly to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the first file metadata management assembly, configuring the characteristic version supported by the first file metadata management assembly into a first version, analyzing the management file according to the read version number of the management file maintained by the first file metadata management assembly and switching the first file metadata management assembly into a master service state;
if the first file metadata management component is normally served within the preset time, upgrading a second file metadata management component which is currently in a slave service state to enable the second file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the second file metadata management component, configuring the characteristic version supported by the second file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the second file metadata management component, configuring the configuration item of the second file metadata management component into a second version, and switching the second file metadata management component into a main service state;
and if the second file metadata management component is normally served within the preset time, configuring the configuration item of the first file metadata management component into a second version.
In some embodiments, if the first file metadata management component is out of service within a preset time, switching the first file metadata management component to a version before upgrading; or if the second file metadata management component is abnormal in service within the preset time, configuring the configuration item of the second file metadata management component into the first version.
In some embodiments, the predetermined characteristic includes an erasure code characteristic, and the fields associated with the predetermined characteristic include an erasure code policy identification field in the log file and an erasure code policy field in the directory image file.
Some embodiments of the present disclosure provide a software upgrading apparatus, including:
an upgrade unit configured to upgrade a file metadata management component of software to support a preset characteristic that a second version is increased relative to a first version among characteristic versions supported by the file metadata management component;
a property description updating unit configured to delete the description of the preset property from the property descriptions supported by the file metadata management component;
a property version configuration unit configured to configure a property version supported by the file metadata management component into a first version according to a property description supported by the file metadata management component;
and the analysis unit is configured to analyze the management file in a corresponding version format according to the version number of the management file maintained by the read file metadata management component under the condition that the characteristic version supported by the file metadata management component is the first version.
In some embodiments, further comprising: and the write control unit is configured to determine whether to execute write operation on the field related to the preset characteristic according to the version number of the preset configuration item configuration.
In some embodiments, the file metadata management component upgraded to support the preset characteristic includes at least a first file metadata management component and a second file metadata management component in a master-slave mode, and further includes: an upgrade control unit configured to:
upgrading a first file metadata management component in a slave service state at present to enable the first file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the first file metadata management component, configuring the characteristic version supported by the first file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the first file metadata management component, configuring the configuration item of the first file metadata management component into the first version, and switching the first file metadata management component into a master service state;
if the first file metadata management component is normally served within the preset time, upgrading a second file metadata management component which is currently in a slave service state to enable the second file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the second file metadata management component, configuring the characteristic version supported by the second file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the second file metadata management component, configuring the configuration item of the second file metadata management component into a second version, and switching the second file metadata management component into a main service state;
and if the second file metadata management component is normally served within the preset time, configuring the configuration item of the first file metadata management component into a second version.
Some embodiments of the present disclosure provide a software upgrading apparatus, including:
a memory; and
a processor coupled to the memory, the processor configured to perform the software upgrade method of any of the preceding embodiments based on instructions stored in the memory.
Some embodiments of the present disclosure propose a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the software upgrade method of any of the preceding embodiments.
Drawings
The drawings that will be used in the description of the embodiments or the related art will be briefly described below. The present disclosure will be more clearly understood from the following detailed description, which proceeds with reference to the accompanying drawings,
it is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without undue inventive faculty.
Fig. 1 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure.
Fig. 2 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure.
Fig. 3 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure.
Fig. 4 is a schematic structural diagram of some embodiments of the software upgrading apparatus of the present disclosure.
Fig. 5 is a schematic structural diagram of some embodiments of the software upgrading apparatus of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure.
Fig. 1 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure. The method may be controlled by a software upgrade, for example.
As shown in fig. 1, the method of this embodiment includes: 11-14.
In step 11, the file metadata management component of the software is upgraded to support a preset property, which is a property in which the second version is increased relative to the first version among property versions supported by the file metadata management component.
In some embodiments, the software is, for example, Hadoop, the file metadata management component of which is a name node (NameNode, NN), the predetermined property is, for example, an erasure code property, and the first and second versions of the property versions supported by the file metadata management component are-63 and-64, respectively. The name node of the Hadoop is responsible for management of file metadata, such as information of a file name space, file blocks and the like, and is also responsible for coordination of management among nodes, such as validity check of the nodes, redundant copy of the file blocks, creation and deletion of files and the like.
In some embodiments, the manner of upgrading software includes: the new version of software is used directly, or new functions are added to the old version of software. Taking Hadoop software as an example, the Hadoop3.x version is directly used, or erasure code characteristics are transplanted into the Hadoop2.x version.
In step 12, the description of the preset property is deleted from the property descriptions supported by the file metadata management component.
Taking Hadoop software as an example, the description of ERASURE code property "ERASURE _ CODING" is deleted from the property description "LayoutFeature" supported by the file metadata management component.
public enum Feature implements LayoutFeature{
……
// ERASURE _ CODING (-64, -61, "Support operation CODING"); erasure correction code feature
}
In step 13, the property version supported by the file metadata management component is configured as a first version according to the property description supported by the file metadata management component.
Taking Hadoop software as an example, if the ERASURE code property "ERASURE _ CODING" is deleted from the feature description, configure/data 0/nn/current/Version as-63.
In step 14, in the case that the property version supported by the file metadata management component is the first version, the management file is parsed according to the version number of the management file maintained by the read file metadata management component.
In some embodiments, when the version number of the management file maintained by the file metadata management component is a first version, no read operation is performed on the field related to the preset property; when the version number of the management file maintained by the file metadata management component is the second version, a read operation is performed on the field related to the preset property.
Taking Hadoop software as an example, the management file maintained by the file metadata management component includes a log file (Editlog) and a directory mirror file (FsImage), and the fields related to erasure code characteristics include an erasure code policy identification field (erasure coding policy id) in the log file and erasure code policy fields (erasure coding policies) in the directory mirror file. According to the prior art, if the property version supported by the file metadata management component is not consistent with the version number of the management file, the software cannot be started normally. According to the scheme disclosed by the invention, the property version supported by the file metadata management component is not required to be consistent with the version number of the management file, when the Editlog and the FsImage are of a new version, the field related to the erasure code property is read, and when the Editlog and the FsImage are of an old version, the field related to the erasure code property is not read.
In the embodiment, by changing the characteristic description and the characteristic version configuration related to the metadata and modifying the analysis logic of the management file maintained by the file metadata management component, the new version software analyzes the management file in a corresponding version format according to the version of the management file, and can compatibly analyze the management files of the new version and the old version.
Fig. 2 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure. The method may be controlled by a software upgrade, for example.
As shown in fig. 2, the method of this embodiment includes: and 21-25.
The steps 21 to 24 are the same as the steps 11 to 14, and are not described herein again.
In step 25, it is determined whether to perform a write operation on the field associated with the preset feature according to the version number of the preset configuration item.
In some embodiments, when the configuration item is configured as the first version, no write operation is performed on the field associated with the preset property; when the configuration item is configured as the second version, a write operation is performed on the field associated with the preset property. In addition, when the configuration item is configured into the first version and the second version, a write operation can be performed on the fields related to the preset property.
Taking Hadoop software as an example, when the configuration item (write _ layout) is configured as the first version (-63), the erasure code policy identification field (erasure coding policy id) in the addition option (addOp) of the log file (Editlog) and the erasure code policy field (erasure coding policies) in the directory image file (FsImage) cannot be written, but can be read; when the configuration item (write _ layout) is configured as the second version (-64), the erasure code policy identification field (erasure code policy id) and the erasure code policy field (erasure code policies) can be either written or read.
In addition, the meaning of a field of 12 bytes at the head of the directory image file (FsImage) is changed, and if the directory image file (FsImage) is the first version (-63), the 12 bytes represent the number of copies (replication); if the directory image file (FsImage) is of the second version (-64), the lower 11 bits of the 12 bytes indicate the number of copies in the case where the highest bit of the 12 bytes is 0, and the lower 11 bits of the 12 bytes indicate the erasure code policy identification (erasure coding policy id) in the case where the highest bit of the 12 bytes is 1. The inode of the directory image file (FsImage) does not need to be specially processed, and can be read and written in a mode of a second version (-64).
According to the embodiment, the writing logic of the fields related to the preset characteristics of the management files of different versions is controlled according to the content of the configuration item, so that the writing operation can be compatibly performed on the management files of the new version and the old version.
Based on the embodiments described in fig. 1 and fig. 2, in a high availability environment (i.e., the file metadata management components at least include the first file metadata management component and the second file metadata management component in a master-slave mode), the present disclosure provides a smooth software upgrade scheme, the software upgrade process does not need to interrupt external services, and if the software upgrade is abnormal, a gradual rollback function is supported. Described below in conjunction with fig. 3.
Fig. 3 is a schematic flow chart diagram of some embodiments of the software upgrade method of the present disclosure. The method may be controlled by a software upgrade, for example. It is assumed that the file metadata management components include at least a first file metadata management component and a second file metadata management component in a master-slave mode. The first file metadata management component and the second file metadata management component are currently in the first version, and can be smoothly upgraded to the second version through the embodiment. The second version of the file metadata management component supports a newly added predetermined characteristic, such as an erasure code characteristic, relative to the first version of the file metadata management component.
As shown in fig. 3, the method of this embodiment includes: 31 to 33.
In step 31, a first software upgrade is performed for a first file metadata management component currently in a slave service state:
according to the method of the embodiment shown in fig. 1, the first file metadata management component currently in the slave service state (standby) is upgraded to support the preset characteristics (that is, the first file metadata management component currently in the slave service state is upgraded to support the preset characteristics, the description of the preset characteristics is deleted from the description of the characteristics supported by the first file metadata management component, the version of the characteristics supported by the first file metadata management component is configured as the first version, the management file is parsed according to the read version number of the management file maintained by the first file metadata management component, the configuration item of the first file metadata management component is configured as the first version, and the first file metadata management component is switched to the master service state (active). At this time, the first file metadata management component operates and provides a service according to the second version, but performs only a read operation and does not perform a write operation on the erasure code related field during operation.
If the first file metadata management component is abnormal in service within preset time, such as performance degradation and the like, switching the first file metadata management component to a first version before upgrading; if the first file metadata management component is functioning properly within the preset time, a second software upgrade is performed at step 32.
At step 32, a second software upgrade is performed for the second file metadata management component currently in the slave service state:
according to the method of the embodiment shown in fig. 1, the second file metadata management component currently in the slave service state is upgraded to support the preset characteristics (that is, the second file metadata management component currently in the slave service state is upgraded to support the preset characteristics, the description of the preset characteristics is deleted from the description of the characteristics supported by the second file metadata management component, the version of the characteristics supported by the second file metadata management component is configured as the first version, the management file is analyzed according to the read version number of the management file maintained by the second file metadata management component in the corresponding version format), the configuration item of the second file metadata management component is configured as the second version, and the second file metadata management component is switched to the master service state. At this time, the second file metadata management component operates and provides a service according to the second version, and a read operation and a write operation may be performed on the erasure code related field during the operation.
If the second file metadata management component is abnormal in service within preset time, such as performance degradation and the like, configuring the configuration item of the second file metadata management component into a first version, namely, returning to the version and the working mode which are already tried to run before; if the second file metadata management component is normally serviced within the preset time, a third software upgrade of step 33 is performed.
At step 33, a third software upgrade is performed for the first file metadata management component: the configuration item of the first file metadata management component is configured to the second version such that the components of the slave service state are consistent with the version and associated configuration of the components of the master service state.
In the embodiment, the file metadata management components are smoothly upgraded in an alternate and progressive upgrading mode of the two file metadata management components, external services are not interrupted in the software upgrading process, and if the software upgrading is abnormal, a gradual rollback function is supported.
Fig. 4 is a schematic structural diagram of some embodiments of the software upgrading apparatus of the present disclosure.
As shown in fig. 4, the apparatus 40 of this embodiment includes:
an upgrade unit 41 configured to upgrade a file metadata management component of software so that it supports a preset property that a second version is increased with respect to a first version among property versions supported by the file metadata management component;
a property description updating unit 42 configured to delete a description of a preset property from among property descriptions supported by the file metadata management component;
a property version configuration unit 43 configured to configure a property version supported by the file metadata management component into a first version according to the property description supported by the file metadata management component;
and the parsing unit 44 is configured to, when the property version supported by the file metadata management component is the first version, parse the management file according to the version number of the management file maintained by the read file metadata management component in the corresponding version format.
For example, when the version number of the management file maintained by the file metadata management component is a first version, no read operation is performed on the field related to the preset characteristic; and when the version number of the management file maintained by the file metadata management component is a second version, performing read operation on the field related to the preset characteristic.
In some embodiments, the apparatus 40 further comprises: and a write control unit 45 configured to determine whether to perform a write operation on the field related to the preset characteristic according to the version number of the preset configuration item configuration.
For example, when the configuration item is configured as the first version, no write operation is performed on the field related to the preset characteristic; when the configuration item is configured to be the second version, writing operation is performed on the field related to the preset characteristic.
In some embodiments, the file metadata management components upgraded to support the preset feature include at least a first file metadata management component and a second file metadata management component in a master-slave mode, and the apparatus 40 further includes: an upgrade control unit 46 configured to:
upgrading the first file metadata management component currently in the slave service state according to the units 41 to 44 (that is, upgrading the first file metadata management component currently in the slave service state to make the first file metadata management component support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the first file metadata management component, configuring the characteristic version supported by the first file metadata management component as a first version, performing corresponding version format analysis on the management file according to the read version number of the management file maintained by the first file metadata management component), configuring the configuration item of the first file metadata management component as the first version, and switching the first file metadata management component to the master service state;
if the first file metadata management component is normally served within the preset time, upgrading the second file metadata management component currently in the slave service state according to the units 41-44 (namely, upgrading the second file metadata management component currently in the slave service state to enable the second file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the second file metadata management component, configuring the characteristic version supported by the second file metadata management component into a first version, analyzing the management file according to the read version number of the management file maintained by the second file metadata management component and the corresponding version format), configuring the configuration item of the second file metadata management component into a second version, and switching the second file metadata management component into the main service state;
and if the second file metadata management component is normally served within the preset time, configuring the configuration item of the first file metadata management component into a second version.
Fig. 5 is a schematic structural diagram of some embodiments of the software upgrading apparatus of the present disclosure.
As shown in fig. 5, the apparatus 50 of this embodiment includes:
a memory 51; and
a processor 52 coupled to the memory, the processor 52 configured to perform the software upgrade method of any of the preceding embodiments based on instructions stored in the memory.
The memory 51 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (12)
1. A software upgrade method, comprising:
upgrading a file metadata management component of software to enable the file metadata management component to support a preset characteristic, wherein the preset characteristic is a characteristic that a second version is increased relative to a first version in characteristic versions supported by the file metadata management component;
deleting the description of the preset property from the property descriptions supported by the file metadata management component;
configuring the property version supported by the file metadata management component into a first version according to the property description supported by the file metadata management component;
and under the condition that the characteristic version supported by the file metadata management component is the first version, analyzing the corresponding version format of the management file according to the version number of the management file maintained by the read file metadata management component.
2. The method of claim 1, wherein,
when the version number of the management file maintained by the file metadata management component is a first version, reading operation is not executed on the field related to the preset characteristic;
and when the version number of the management file maintained by the file metadata management component is a second version, performing read operation on the field related to the preset characteristic.
3. The method of claim 1, further comprising:
and determining whether to execute write operation on the fields related to the preset characteristics according to the version number of the preset configuration item configuration.
4. The method of claim 3, wherein,
when the configuration item is configured to be the first version, no writing operation is carried out on the field related to the preset characteristic;
when the configuration item is configured to be the second version, writing operation is performed on the field related to the preset characteristic.
5. The method of claim 4, wherein the file metadata management components upgraded to support the preset feature include at least a first file metadata management component and a second file metadata management component in a master-slave mode,
upgrading a first file metadata management component in a slave service state at present to enable the first file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the first file metadata management component, configuring the characteristic version supported by the first file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the first file metadata management component, configuring the configuration item of the first file metadata management component into the first version, and switching the first file metadata management component into a master service state;
if the first file metadata management component is normally served within the preset time, upgrading a second file metadata management component which is currently in a slave service state to enable the second file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the second file metadata management component, configuring the characteristic version supported by the second file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the second file metadata management component, configuring the configuration item of the second file metadata management component into a second version, and switching the second file metadata management component into a main service state;
and if the second file metadata management component is normally served within the preset time, configuring the configuration item of the first file metadata management component into a second version.
6. The method of claim 5, wherein,
if the first file metadata management component is abnormal in service within the preset time, switching the first file metadata management component to a version before upgrading;
or if the second file metadata management component is abnormal in service within the preset time, configuring the configuration item of the second file metadata management component into the first version.
7. The method of any of claims 2-6, wherein the predetermined characteristic comprises an erasure coding characteristic, the predetermined characteristic related fields comprising an erasure coding policy identification field in a log file and an erasure coding policy field in a directory image file.
8. A software upgrade apparatus comprising:
an upgrade unit configured to upgrade a file metadata management component of software to support a preset characteristic that a second version is increased relative to a first version among characteristic versions supported by the file metadata management component;
a property description updating unit configured to delete the description of the preset property from the property descriptions supported by the file metadata management component;
a property version configuration unit configured to configure a property version supported by the file metadata management component into a first version according to a property description supported by the file metadata management component;
and the analysis unit is configured to analyze the management file in a corresponding version format according to the version number of the management file maintained by the read file metadata management component under the condition that the characteristic version supported by the file metadata management component is the first version.
9. The apparatus of claim 8, further comprising:
and the write control unit is configured to determine whether to execute write operation on the field related to the preset characteristic according to the version number of the preset configuration item configuration.
10. The apparatus of claim 9, wherein the file metadata management components upgraded to support the preset feature comprise at least a first file metadata management component and a second file metadata management component in a master-slave mode, further comprising:
an upgrade control unit configured to:
upgrading a first file metadata management component in a slave service state at present to enable the first file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the first file metadata management component, configuring the characteristic version supported by the first file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the first file metadata management component, configuring the configuration item of the first file metadata management component into the first version, and switching the first file metadata management component into a master service state;
if the first file metadata management component is normally served within the preset time, upgrading a second file metadata management component which is currently in a slave service state to enable the second file metadata management component to support the preset characteristics, deleting the description of the preset characteristics from the characteristic description supported by the second file metadata management component, configuring the characteristic version supported by the second file metadata management component into a first version, analyzing the corresponding version format of the management file according to the read version number of the management file maintained by the second file metadata management component, configuring the configuration item of the second file metadata management component into a second version, and switching the second file metadata management component into a main service state;
and if the second file metadata management component is normally served within the preset time, configuring the configuration item of the first file metadata management component into a second version.
11. A software upgrade apparatus comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the software upgrade method of any one of claims 1-7 based on instructions stored in the memory.
12. A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, implements the software upgrade method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910410061.8A CN111949287A (en) | 2019-05-16 | 2019-05-16 | Software upgrading method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910410061.8A CN111949287A (en) | 2019-05-16 | 2019-05-16 | Software upgrading method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111949287A true CN111949287A (en) | 2020-11-17 |
Family
ID=73336674
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910410061.8A Pending CN111949287A (en) | 2019-05-16 | 2019-05-16 | Software upgrading method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111949287A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1648857A (en) * | 2004-01-28 | 2005-08-03 | 三星电子株式会社 | Auto version managing system and method for use in software |
| US20070294684A1 (en) * | 2006-06-15 | 2007-12-20 | Fujitsu Limited | Computer program and apparatus for updating installed software programs |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
| CN105099780A (en) * | 2015-08-12 | 2015-11-25 | 北京思特奇信息技术股份有限公司 | Automatic file publishing or upgrading method and system thereof |
| CN106886422A (en) * | 2017-04-07 | 2017-06-23 | 广州华多网络科技有限公司 | Method for upgrading software and device, electronic equipment |
| US9747291B1 (en) * | 2015-12-29 | 2017-08-29 | EMC IP Holding Company LLC | Non-disruptive upgrade configuration translator |
-
2019
- 2019-05-16 CN CN201910410061.8A patent/CN111949287A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1648857A (en) * | 2004-01-28 | 2005-08-03 | 三星电子株式会社 | Auto version managing system and method for use in software |
| US20070294684A1 (en) * | 2006-06-15 | 2007-12-20 | Fujitsu Limited | Computer program and apparatus for updating installed software programs |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
| CN105099780A (en) * | 2015-08-12 | 2015-11-25 | 北京思特奇信息技术股份有限公司 | Automatic file publishing or upgrading method and system thereof |
| US9747291B1 (en) * | 2015-12-29 | 2017-08-29 | EMC IP Holding Company LLC | Non-disruptive upgrade configuration translator |
| CN106886422A (en) * | 2017-04-07 | 2017-06-23 | 广州华多网络科技有限公司 | Method for upgrading software and device, electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10114630B2 (en) | Management of software and operating system updates required for the process of creating a virtual machine facsimile of an existing physical or virtual machine | |
| JP5342302B2 (en) | Firmware update system, firmware distribution server, and program | |
| CN107870968B (en) | Performing real-time updates to a file system volume | |
| US20190245919A1 (en) | Method and apparatus for information processing, server and computer readable medium | |
| US10296423B2 (en) | System and method for live virtual incremental restoring of data from cloud storage | |
| US8725969B2 (en) | Distributed content storage system supporting different redundancy degrees | |
| US20050091247A1 (en) | System and method for backing up and restoring data | |
| JP4825433B2 (en) | Computing device with relatively limited storage space and operating system / file system thereof | |
| US10592354B2 (en) | Configurable recovery states | |
| GB2508599A (en) | Software version management when downgrading software | |
| KR20080097196A (en) | File-based compression on a fat volume | |
| CN113568566B (en) | Method for seamless migration of simple storage service by index object, main device and storage server | |
| US8561050B2 (en) | Method and system for updating an application | |
| WO2024066995A1 (en) | Text code editing method and system | |
| WO2018177193A1 (en) | Software upgrade method and device | |
| US20120151005A1 (en) | Image file download method | |
| CN104331311A (en) | Upgrade package generating method and device | |
| US20230222093A1 (en) | Systems and method for indexing and data compaction | |
| US10564894B2 (en) | Free space pass-through | |
| CN111949287A (en) | Software upgrading method and device | |
| US11726668B2 (en) | Device with flash memory and method for writing/erasing/updating data in flash memory thereof | |
| CN110795113A (en) | Redis cluster service installation method, server and medium | |
| CN111522783B (en) | Data synchronization method, device, electronic equipment and computer readable storage medium | |
| US11954081B1 (en) | Management of two application versions in one database table | |
| CN110109624B (en) | Method and device for adjusting NTFS partition |
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 |