CN108009186A - Service release switching method, service release switching device and server - Google Patents
Service release switching method, service release switching device and server Download PDFInfo
- Publication number
- CN108009186A CN108009186A CN201710081517.1A CN201710081517A CN108009186A CN 108009186 A CN108009186 A CN 108009186A CN 201710081517 A CN201710081517 A CN 201710081517A CN 108009186 A CN108009186 A CN 108009186A
- Authority
- CN
- China
- Prior art keywords
- version
- service
- pointer
- file
- target
- 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
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000001960 triggered effect Effects 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 14
- 230000005012 migration Effects 0.000 description 5
- 238000013508 migration Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/134—Distributed indices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention proposes a kind of service release switching method, service release switching device and server, wherein, the service release switching method includes：For each corresponding file distribution index node of version in multiple versions of same service；In the case of the index node for the current version respective file that the pointer of the service is directed toward the service, the instruction that the service is switched to target version from the current version is received；According to described instruction, the pointer is controlled to be directed toward the index node of the target version respective file.By technical scheme, efficiently and accurately the version of service can be switched over.
Description
Technical field
The present invention relates to server technology field, in particular to service release switching method, service release switching dress
Put and server.
Background technology
In the prior art, version switching can be carried out by client, specifically, user selects to be cut on the client
The version changed, server whether there is to inquire about this version, and if there is upgrading message is confirmed, then server is corresponding version
Notebook data is transmitted to client by network and is upgraded.It can also realize that the version of service switches by following steps,
1. backup existing version, 2. migration existing versions, 3. refund the version for needing rollback.But the version in two above scheme
The speed of switching is slow, and operation error easily occurs.
Therefore, how efficiently and accurately the version of service is switched over as technical problem urgently to be resolved hurrily.
The content of the invention
The present invention is based on the above problem, it is proposed that a kind of new technical solution, can solve the version of switching service
Speed is slow and the technical problem of operation error easily occurs.
In view of this, the first aspect of the present invention proposes a kind of service release switching method, including：For same service
Multiple versions in each corresponding file distribution index node of version；The current of the service is directed toward in the pointer of the service
In the case of the index node of version respective file, the finger that the service is switched to target version from the current version is received
Order；According to described instruction, the pointer is controlled to be directed toward the index node of the target version respective file.
In the technical scheme, by the corresponding file distribution index node of each version for same service, needing
When service is switched to target version, by controlling pointer to be directed toward the index node of the target version respective file, elder generation is avoided
Select to be switched version on the client, and avoid server by be switched edition data by network transmission to visitor
Family end, target version is switched to so as to efficiently realize by service from current version, and this programme avoids performing migration version
, there is the risk of mistake so as to reduce in this step of during switching service release.
In the above-mentioned technical solutions, it is preferable that further include：The corresponding file of the multiple version is stored in together
Under one catalogue.
In the technical scheme, by the way that the corresponding file of multiple versions of service is stored same catalogue
Under, the file that target version is searched when switching version is avoided, further ensure that the speed of version switching.
In any of the above-described technical solution, it is preferable that be directed toward the target version in the control pointer and correspond to text
After the index node of part, further include：If receiving the reading instruction for the corresponding file of the target version, institute is obtained
State pointer；The corresponding file of the target version is read according to the pointer.
In the technical scheme, the if desired corresponding file of the target version of reading service, then can be by obtaining the clothes
The pointer of business carries out the reading of file, so as to ensure that service can be with normal operation.
In any of the above-described technical solution, it is preferable that it is described to obtain the pointer, specifically include：According to the target version
The title of this respective file, determines the index number of the target version respective file；According to being read the index number
The index node table of target version respective file；The pointer is got in the index node table.
In the technical scheme, index number is determined by file name, index node table is read according to index number, with
Pointer is obtained in index node table, so that the file according to the normal reading service of the pointer.
In any of the above-described technical solution, it is preferable that further include：According to the title of the service and version number, to described
Each version is named.
In the technical scheme, each version is named according to the title of service and version number so that user according to
Version name just can quickly recognize the concrete condition of version, consequently facilitating user carries out version switching.
In any of the above-described technical solution, it is preferable that described instruction includes：The version switching command, described of user's triggering
Service runs the version switching command triggered when something goes wrong under the current version or is serviced described from described current
The version switching command that version updating triggers when failing to version updating during the target version.
In the technical scheme, user can carry out version switching according to the demand of oneself, for example, in service renewal to most
During new version, the uncomfortable service using latest edition of user, then by service be switched to renewal before version, so as to meet
The use demand of user.Either when service under current version operation go wrong or version updating fail when, will can take
Business, which is switched under target version, to be run, so as to ensure that the normal operation of service.
In any of the above-described technical solution, it is preferable that if described instruction includes：The service is transported under the current version
The version switching command that row triggers when something goes wrong, then the target version is a upper version for the current version.
In the technical scheme, go wrong if service is run under current version, service is switched to current version
A upper version under run, avoid service version switching before and version switching after performance having big difference, so as to ensure
The reliability of service operation.
In any of the above-described technical solution, it is preferable that be stored with the situation of the corresponding file of the multiple version
Under, further include：If the quantity of the multiple version is more than default quantity, by least one version oldest in the multiple version
This corresponding file is deleted.
In the technical scheme, since the file of storing excess version can take more memory space, and service general
It is to switch under newest several versions and runs, therefore, the oldest corresponding file of at least one version is deleted, so that
The discarded record of storing excess is avoided, and then improves the utilization rate of memory space.
In any of the above-described technical solution, it is preferable that the default quantity is 2 or 3.
The second aspect of the present invention proposes a kind of service release switching device, including：Allocation unit, for be same
The corresponding file distribution index node of each version in multiple versions of service；Receiving unit, for the pointer in the service
In the case of the index node of current version respective file for being directed toward the service, receive and serviced described from the current version
It is switched to the instruction of target version；Control unit, for according to described instruction, controlling the pointer to be directed toward the target version pair
Answer the index node of file.
In the technical scheme, by the corresponding file distribution index node of each version for same service, needing
When service is switched to target version, by controlling pointer to be directed toward the index node of the target version respective file, elder generation is avoided
Select to be switched version on the client, and avoid server by be switched edition data by network transmission to visitor
Family end, target version is switched to so as to efficiently realize by service from current version, and this programme avoids performing migration version
, there is the risk of mistake so as to reduce in this step of during switching service release.
In any of the above-described technical solution, it is preferable that further include：Storage unit, for the multiple version is right respectively
The file answered is stored under same catalogue.
In the technical scheme, by the way that the corresponding file of multiple versions of service is stored same catalogue
Under, the file that target version is searched when switching version is avoided, further ensure that the speed of version switching.
In any of the above-described technical solution, it is preferable that further include：Acquiring unit, if for receiving for the target
The reading instruction of the corresponding file of version, then obtain the pointer；Reading unit, for reading the target according to the pointer
The corresponding file of version.
In the technical scheme, the if desired corresponding file of the target version of reading service, then can be by obtaining the clothes
The pointer of business carries out the reading of file, so as to ensure that service can be with normal operation.
In any of the above-described technical solution, it is preferable that the acquiring unit includes：Determination subelement, for according to
The title of target version respective file, determines the index number of the target version respective file；Subelement is read, for basis
The index number reads the index node table of the target version respective file；Subelement is obtained, in the index section
The pointer is got in point table.
In the technical scheme, index number is determined by file name, index node table is read according to index number, with
Pointer is obtained in index node table, so that the file according to the normal reading service of the pointer.
In any of the above-described technical solution, it is preferable that further include：Name unit, for the title according to the service and
Version number, is named each version.
In the technical scheme, each version is named according to the title of service and version number so that user according to
Version name just can quickly recognize the concrete condition of version, consequently facilitating user carries out version switching.
In any of the above-described technical solution, it is preferable that described instruction includes：The version switching command, described of user's triggering
Service runs the version switching command triggered when something goes wrong under the current version or is serviced described from described current
The version switching command that version updating triggers when failing to version updating during the target version.
In the technical scheme, user can carry out version switching according to the demand of oneself, for example, in service renewal to most
During new version, the uncomfortable service using latest edition of user, then by service be switched to renewal before version, so as to meet
The use demand of user.Either when service under current version operation go wrong or version updating fail when, will can take
Business, which is switched under target version, to be run, so as to ensure that the normal operation of service.
In any of the above-described technical solution, it is preferable that if described instruction includes：The service is transported under the current version
The version switching command that row triggers when something goes wrong, then the target version is a upper version for the current version.
In the technical scheme, go wrong if service is run under current version, service is switched to current version
A upper version under run, avoid service version switching before and version switching after performance having big difference, so as to ensure
The reliability of service operation.
In any of the above-described technical solution, it is preferable that be stored with the situation of the corresponding file of the multiple version
Under, further include：Delete unit, if the quantity for the multiple version is more than default quantity, by the multiple version most
The corresponding file of old at least one version is deleted.
In the technical scheme, since the file of storing excess version can take more memory space, and service general
It is to switch under newest several versions and runs, therefore, the oldest corresponding file of at least one version is deleted, so that
The discarded record of storing excess is avoided, and then improves the utilization rate of memory space.
In any of the above-described technical solution, it is preferable that the default quantity is 2 or 3.The third aspect of the present invention proposes
A kind of server, including the service release switching device any one of above-mentioned technical proposal, therefore, the server have and
The identical technique effect of service release switching device any one of above-mentioned technical proposal, details are not described herein.
In the above-mentioned technical solutions, it is preferable that the server includes：Cloud Server and/or physical server.
By technical scheme, efficiently and accurately the version of service can be switched over.
Brief description of the drawings
Fig. 1 shows the flow diagram of service release switching method according to an embodiment of the invention；
Fig. 2A and Fig. 2 B show the principle schematic of service release switching according to an embodiment of the invention；
Fig. 3 shows the flow diagram of service release switching method according to another embodiment of the invention；
Fig. 4 shows the principle schematic of accessing file according to an embodiment of the invention；
Fig. 5 shows the flow diagram of service release switching method according to still another embodiment of the invention；
Fig. 6 shows the structure diagram of service release switching device according to an embodiment of the invention；
Fig. 7 shows the structure diagram of service release switching device according to another embodiment of the invention；
Fig. 8 shows the structure diagram of service release switching device according to still another embodiment of the invention；
Fig. 9 shows the structure diagram of server according to an embodiment of the invention.
Embodiment
It is below in conjunction with the accompanying drawings and specific real in order to be more clearly understood that the above objects, features and advantages of the present invention
Mode is applied the present invention is further described in detail.It should be noted that in the case where there is no conflict, the implementation of the application
Feature in example and embodiment can be mutually combined.
Many details are elaborated in the following description to facilitate a thorough understanding of the present invention, still, the present invention may be used also
To be implemented using other different from other modes described here, therefore, protection scope of the present invention and from described below
Specific embodiment limitation.
Fig. 1 shows the flow diagram of service release switching method according to an embodiment of the invention.
As shown in Figure 1, service release switching method according to an embodiment of the invention, including：
Step 102, it is the corresponding file distribution index node of each version in multiple versions of same service.
Wherein, the service in above-mentioned can be software, for example, WORD, EXCEL, wechat, for what is be controlled to vehicle
Software, service can also be the program for supporting various functions, for example, the journey of the door of the program of the door of opening vehicle, closing vehicle
Sequence, the program for checking vehicle-state, the program for opening vehicle window, the program for closing vehicle window.
Step 104, in the case of the index node for the current version respective file that the pointer of service is directed toward service, receive
The instruction that target version is switched to from current version will be serviced.
Step 106, the index node of target version respective file is directed toward according to instruction, control pointer.
As shown in Figure 2 A, service has three versions, is respectively version 1, version 2 and version 3, and the pointer of the service is directed toward version
The index node of this 1 respective file.As shown in Figure 2 B, receive will service be switched to the instruction of version 2 from version 1 when, refer to
Pin disconnects the index node for being directed toward 1 respective file of version, and controls the index node of pointer direction version 2 respective file, will
Service is switched to version 2 from version 1, then can start the service of version 2.
In the technical scheme, by the corresponding file distribution index node of each version for same service, needing
When service is switched to target version, by controlling pointer to be directed toward the index node of the target version respective file, elder generation is avoided
Select to be switched version on the client, and avoid server by be switched edition data by network transmission to visitor
Family end, target version is switched to so as to efficiently realize by service from current version, and this programme avoids performing migration version
, there is the risk of mistake so as to reduce in this step of during switching service release.
It is understood that service is switched to the instruction of target version from current version to be included：The version of user's triggering
Switching command, service run the version switching command triggered when something goes wrong under current version or are servicing from current version
Update the version switching command triggered when version updating fails during target version.
User can carry out version switching according to the demand of oneself, for example, when latest edition is arrived in service renewal, user is not
The service of latest edition accustomed to using, then be switched to version before updating, so as to meet the use demand of user by service.
Either when service under current version operation go wrong or version updating fail when, service can be switched to target version
Lower operation, so as to ensure that the normal operation of service.
It is understood that if the instruction in above-mentioned includes：Service runs what is triggered when something goes wrong under current version
Version switching command, then target version is a upper version for current version.
Go wrong if service is run under current version, service is switched under a upper version for current version and transported
OK, avoid performance of the service before version switching and after version switching to have big difference, so as to ensure that the reliable of service operation
Property.
For example, service has A versions, B versions and C versions, and C versions are newer than B version, and B versions are newer than A version, service in C
Run under version when something goes wrong, directly service is switched under B versions and is run.
Fig. 3 shows the flow diagram of service release switching method according to another embodiment of the invention.
Step 102, step 104 and step 106 and the step 102 in Fig. 1, step 104 and step 106 in Fig. 3 is basic
It is identical.In addition, service release switching method further includes step 103, step 108 and step 110 in Fig. 3.
Wherein, step 103：The corresponding file of multiple versions is stored under same catalogue, according to service
Title and version number, are named each version.
For example, service is wechat, according to the version distribution order of wechat, multiple version names of wechat have：wechat_
Version1.1, wechat_version1.2 and wechat_version1.3.
Step 108：If receiving the reading instruction for the corresponding file of target version, pointer is obtained.
Step 110：The corresponding file of target version is read according to pointer.
In the technical scheme, except that service efficiently can be switched to target version, and reduction from current version
, can also be by the way that the corresponding file of multiple versions of service be deposited outside the risk for occurring mistake when switching service release
Store up under same catalogue, avoid the file that target version is searched when switching version, further ensure that version switches
Speed.And each version of service is named according to the title and version number of service, so as to facilitate user rapidly
Understand the situation of each version of service, and then version switching is carried out easy to user.In addition, the if desired target version of reading service
This corresponding file, then can carry out the reading of file, so as to ensure that service can be just by obtaining the pointer of the service
Often operation.
It is understood that step 103 can perform after step 102 and before step 104, step 103 may be used also
To be performed before step 102.Or the corresponding file of multiple versions is stored in same catalogue in step 103
Under be after step 102 and performed before step 104, title according to service and version number in step 103, to each
Version, which is named, to be performed before step 102.Or the title according to service in step 103 and version number, to each
Version, which is named, to be after step 102 and is performed before step 104, corresponding to multiple versions respectively in step 103
File to be stored under same catalogue performed before step 102.
It is understood that the acquisition pointer in step 108, specifically includes：According to target version respective file
Title, determines the index number of target version respective file；The index section of target version respective file is read according to index number
Point table；Pointer is got in index node table.
As shown in figure 4, looked for first according to filename (i.e. File name) by the correspondence of Directory (catalogue)
To the index number (Inode number) of this file.Then corresponding bar is found in index node table according to index number
Mesh.There are index number, file type (File type), the authority (permission) of file, hard link number in index node table
(Link count), User ID (User ID, UID), group ID (Group ID, GID), the size (size) of file, time stab
(Time stamp) and pointer (pointer).Authority information is finally checked, to determine whether the user for accessing file has access should
The authority of file, however, it is determined that user has the authority for accessing this document, then is directed to file into line access according to finger.
It is understood that before control pointer is directed toward the index node of target version respective file, and according to upper
The scheme stated carrys out the corresponding file of current version of reading service, and it is no longer repeated herein.
Fig. 5 shows the flow diagram of service release switching method according to still another embodiment of the invention.
Step 102, step 104 and step 106 and the step 102 in Fig. 1, step 104 and step 106 in Fig. 5 is basic
It is identical.In addition, service release switching method further includes step 112 in Fig. 5.
Wherein, step 112：In the case where storing the corresponding file of multiple versions, if the quantity of multiple versions is big
In default quantity, then the corresponding file of at least one version oldest in multiple versions is deleted.
For example, the A versions of service, B versions and C versions are stored, and C versions are newer than B version, B versions are newer than A version,
If default quantity is 2, the oldest corresponding file of A versions is deleted.
, can also be before step 102 or step it is understood that step 112 can perform after step 106
Performed after 102.
In the technical scheme, since the file of storing excess version can take more memory space, and service general
It is to switch under newest several versions and runs, therefore, service except can be efficiently switched to by this programme from current version
Target version, and while reducing switching service release, occur outside the risk of mistake, also by by oldest at least one version
Corresponding file is deleted, and so as to avoid the discarded record of storing excess, and then improves the utilization rate of memory space.
It is understood that the default quantity is 2 or 3.Certainly, default quantity can also be other numbers such as 4,5 or 6
Amount.Default quantity can be that default settings are good, or user changes the default quantity according to the demand of oneself.
Fig. 6 shows the structure diagram of service release switching device according to an embodiment of the invention.
As shown in fig. 6, service release switching device 600 according to an embodiment of the invention, including：Allocation unit
602nd, receiving unit 604 and control unit 606.
Allocation unit 602, for the corresponding file distribution index section of each version in multiple versions for same service
Point；Receiving unit 604, the index node of the current version respective file for being directed toward the service in the pointer of the service
In the case of, receive the instruction that the service is switched to target version from the current version；Control unit 606, for basis
Described instruction, controls the pointer to be directed toward the index node of the target version respective file.
In the technical scheme, by the corresponding file distribution index node of each version for same service, needing
When service is switched to target version, by controlling pointer to be directed toward the index node of the target version respective file, elder generation is avoided
Select to be switched version on the client, and avoid server by be switched edition data by network transmission to visitor
Family end, target version is switched to so as to efficiently realize by service from current version, and this programme avoids performing migration version
, there is the risk of mistake so as to reduce in this step of during switching service release.
Fig. 7 shows the structure diagram of service release switching device according to another embodiment of the invention.
Allocation unit 602, receiving unit 604 and control unit 606 and the allocation unit 602 in Fig. 6, reception in Fig. 7
Unit 604 and control unit 606 are essentially identical.In addition, the service release switching device 600 shown in Fig. 7 further includes storage unit
608th, acquiring unit 610, reading unit 612 and name unit 614.
Wherein, storage unit 608 is used to the corresponding file of the multiple version being stored under same catalogue.
If acquiring unit 610 is used to receive the reading instruction for the corresponding file of the target version, the pointer is obtained；Read
Unit 612 is taken to be used to read the corresponding file of the target version according to the pointer.Unit 614 is named to be used for according to the clothes
The title of business and version number, are named each version.
In the technical scheme, except that service efficiently can be switched to target version, and reduction from current version
, can also be by the way that the corresponding file of multiple versions of service be deposited outside the risk for occurring mistake when switching service release
Store up under same catalogue, avoid the file that target version is searched when switching version, further ensure that version switches
Speed.And each version of service is named according to the title and version number of service, so as to facilitate user rapidly
Understand the situation of each version of service, and then version switching is carried out easy to user.In addition, the if desired target version of reading service
This corresponding file, then can carry out the reading of file, so as to ensure that service can be just by obtaining the pointer of the service
Often operation.
It is understood that acquiring unit 610 includes：Determination subelement 6102, read subelement 6104 and obtain son list
Member 6106.Determination subelement 6102 is used for the title according to target version respective file, determines the rope of target version respective file
Draw numbering；Read the index node table that subelement 6104 is used to read target version respective file according to index number；Obtain son
Unit 6106 is used to get pointer in index node table.
Fig. 8 shows the structure diagram of service release switching device according to still another embodiment of the invention.
Allocation unit 602, receiving unit 604 and control unit 606 and the allocation unit 602 in Fig. 6, reception in Fig. 8
Unit 604 and control unit 606 are essentially identical.In addition, the service release switching device 600 shown in Fig. 8 further includes deletion unit
616。
Wherein, in the case where being stored with the corresponding file of multiple versions, delete unit 616 and be used for, if multiple versions
This quantity is more than default quantity, then deletes the corresponding file of at least one version oldest in multiple versions.
For example, the A versions of service, B versions and C versions are stored, and C versions are newer than B version, B versions are newer than A version,
If default quantity is 2, the oldest corresponding file of A versions is deleted.
In the technical scheme, since the file of storing excess version can take more memory space, and service general
It is to switch under newest several versions and runs, therefore, service except can be efficiently switched to by this programme from current version
Target version, and while reducing switching service release, occur outside the risk of mistake, also by by oldest at least one version
Corresponding file is deleted, and so as to avoid the discarded record of storing excess, and then improves the utilization rate of memory space.
It is understood that the default quantity is 2 or 3.Certainly, default quantity can also be other numbers such as 4,5 or 6
Amount.Default quantity can be that default settings are good, or user changes the default quantity according to the demand of oneself.
Fig. 9 shows the structure diagram of server according to an embodiment of the invention.
As shown in figure 9, server 900 according to an embodiment of the invention, including any one of above-mentioned technical proposal
Service release switching device 902 (equivalent to the service release switching device 600 in Fig. 6 either Fig. 7 or Fig. 8), therefore, should
Server 900 has the technique effect identical with the service release switching device 902 of any one of above-mentioned technical proposal, herein not
Repeat again.
It is understood that server 900 includes：Cloud Server and/or physical server.
Technical scheme is described in detail above in association with attached drawing, by technical scheme, can efficiently,
The version of service is switched over exactly.
In the present invention, term " first ", " second " are only used for the purpose described, and it is not intended that instruction or hint phase
To importance；Term " multiple " represents two or more.For the ordinary skill in the art, can be according to tool
Body situation understands the concrete meaning of above-mentioned term in the present invention.
The foregoing is only a preferred embodiment of the present invention, is not intended to limit the invention, for the skill of this area
For art personnel, the invention may be variously modified and varied.Within the spirit and principles of the invention, that is made any repaiies
Change, equivalent substitution, improvement etc., should all be included in the protection scope of the present invention.
Claims (17)
- A kind of 1. service release switching method, it is characterised in that including：For each corresponding file distribution index node of version in multiple versions of same service；In the case of the index node for the current version respective file that the pointer of the service is directed toward the service, receive institute The service stated is switched to the instruction of target version from the current version；According to described instruction, the pointer is controlled to be directed toward the index node of the target version respective file.
- 2. service release switching method according to claim 1, it is characterised in that further include：The corresponding file of the multiple version is stored under same catalogue.
- 3. service release switching method according to claim 1, it is characterised in that be directed toward institute in the control pointer After the index node for stating target version respective file, further include：If receiving the reading instruction for the corresponding file of the target version, the pointer is obtained；The corresponding file of the target version is read according to the pointer.
- 4. service release switching method according to claim 3, it is characterised in that described to obtain the pointer, specific bag Include：According to the title of the target version respective file, the index number of the target version respective file is determined；The index node table of the target version respective file is read according to the index number；The pointer is got in the index node table.
- 5. service release switching method according to any one of claim 1 to 4, it is characterised in that further include：According to the title of the service and version number, each version is named.
- 6. service release switching method according to any one of claim 1 to 4, it is characterised in thatDescribed instruction includes：The version switching command of user's triggering, the service run under the current version and go wrong When the version switching command that the triggers or version during the service is updated to the target version from the current version The version switching command triggered during this renewal failure.
- 7. service release switching method according to claim 6, it is characterised in thatIf described instruction includes：The service runs the version switching command triggered when something goes wrong under the current version, Then the target version is a upper version for the current version.
- 8. service release switching method according to any one of claim 1 to 4, it is characterised in that described more storing In the case of the corresponding file of a version, further include：If the quantity of the multiple version is more than default quantity, at least one version oldest in the multiple version is distinguished Corresponding file is deleted.
- 9. service release switching method according to claim 8, it is characterised in thatThe default quantity is 2 or 3.
- A kind of 10. service release switching device, it is characterised in that including：Allocation unit, for the corresponding file distribution index node of each version in multiple versions for same service；Receiving unit, the feelings of the index node of the current version respective file for being directed toward the service in the pointer of the service Under condition, the instruction that the service is switched to target version from the current version is received；Control unit, for according to described instruction, controlling the pointer to be directed toward the index node of the target version respective file.
- 11. service release switching device according to claim 10, it is characterised in that further include：Storage unit, for the corresponding file of the multiple version to be stored under same catalogue.
- 12. service release switching device according to claim 10, it is characterised in that further include：Acquiring unit, if for receiving the reading instruction for the corresponding file of the target version, obtains the pointer；Reading unit, for reading the corresponding file of the target version according to the pointer.
- 13. service release switching device according to claim 12, it is characterised in that the acquiring unit includes：Determination subelement, for the title according to the target version respective file, determines the target version respective file Index number；Subelement is read, for reading the index node table of the target version respective file according to the index number；Subelement is obtained, for getting the pointer in the index node table.
- 14. the service release switching device according to any one of claim 10 to 13, it is characterised in that further include：Unit is named, for the title according to the service and version number, each version is named.
- 15. the service release switching device according to any one of claim 10 to 13, it is characterised in that in storage In the case of stating the corresponding file of multiple versions, further include：Delete unit, if the quantity for the multiple version is more than default quantity, by the multiple version it is oldest extremely The corresponding file of a version is deleted less.
- A kind of 16. server, it is characterised in that including：Service release switching as any one of claim 10 to 15 Device.
- 17. server according to claim 16, it is characterised in thatThe server includes：Cloud Server and/or physical server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710081517.1A CN108009186A (en) | 2017-02-15 | 2017-02-15 | Service release switching method, service release switching device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710081517.1A CN108009186A (en) | 2017-02-15 | 2017-02-15 | Service release switching method, service release switching device and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108009186A true CN108009186A (en) | 2018-05-08 |
Family
ID=62048727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710081517.1A Pending CN108009186A (en) | 2017-02-15 | 2017-02-15 | Service release switching method, service release switching device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108009186A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558382A (en) * | 2018-12-06 | 2019-04-02 | Oppo广东移动通信有限公司 | File management method, electronic device and computer readable storage medium |
| CN112737942A (en) * | 2020-12-24 | 2021-04-30 | 深圳市彬讯科技有限公司 | Service route switching method, device, equipment and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831204A (en) * | 2012-08-09 | 2012-12-19 | 珠海金山网络游戏科技有限公司 | File packaging format with version control ability |
| CN102955861A (en) * | 2012-11-30 | 2013-03-06 | 华为技术有限公司 | Method and device for generating index files based on backup files |
| US8938425B1 (en) * | 2011-06-30 | 2015-01-20 | Emc Corporation | Managing logical views of storage |
-
2017
- 2017-02-15 CN CN201710081517.1A patent/CN108009186A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8938425B1 (en) * | 2011-06-30 | 2015-01-20 | Emc Corporation | Managing logical views of storage |
| CN102831204A (en) * | 2012-08-09 | 2012-12-19 | 珠海金山网络游戏科技有限公司 | File packaging format with version control ability |
| CN102955861A (en) * | 2012-11-30 | 2013-03-06 | 华为技术有限公司 | Method and device for generating index files based on backup files |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558382A (en) * | 2018-12-06 | 2019-04-02 | Oppo广东移动通信有限公司 | File management method, electronic device and computer readable storage medium |
| CN112737942A (en) * | 2020-12-24 | 2021-04-30 | 深圳市彬讯科技有限公司 | Service route switching method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11809726B2 (en) | Distributed storage method and device | |
| CN111095219B (en) | File system point-in-time restoration using recycle bin and version history | |
| US7765189B2 (en) | Data migration apparatus, method, and program for data stored in a distributed manner | |
| CN102667772B (en) | File level hierarchical storage management system, method, and apparatus | |
| JP5727020B2 (en) | Cloud computing system and data synchronization method thereof | |
| CN100354824C (en) | Method and system for deployment of operating system | |
| KR20200093596A (en) | Resynchronization of metadata in content management system | |
| US10496618B2 (en) | Managing data replication in a data grid | |
| CN104715001A (en) | Method and system performing wirite operation on shared resource in cluster of data processing system | |
| CN106161523B (en) | A kind of data processing method and equipment | |
| US20140081911A1 (en) | Optimizing automatic deletion of backup files | |
| US9747291B1 (en) | Non-disruptive upgrade configuration translator | |
| US9690796B2 (en) | Non-transitory computer-readable media storing file management program, file management apparatus, and file management method | |
| KR101916240B1 (en) | Storage constrained synchronization of shared content items | |
| CN105278882A (en) | Disk management method of distributed file system | |
| US20180013827A1 (en) | File server apparatus | |
| US20190073153A1 (en) | Efficient repository migration and storage | |
| CN114629921A (en) | Cloud platform and bucket management method of object storage service provided by cloud platform | |
| CN108009186A (en) | Service release switching method, service release switching device and server | |
| JP2020017282A (en) | Storage constrained synchronization engine | |
| JP4719732B2 (en) | Backup server, mobile device, communication system using these, and backup method | |
| US20100250634A1 (en) | File server system and file management method | |
| JP5911378B2 (en) | Document management server, computer program, and document management method | |
| JP4249605B2 (en) | Client server system, cache control method, and computer program | |
| US9418097B1 (en) | Listener event consistency points |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 103, building 1, yard 4, Hengxing Road, Gaoliying Town, Shunyi District, Beijing Applicant after: BEIJING CHJ AUTOMOTIVE TECHNOLOGY Co.,Ltd. Address before: Unit 819, Block D, Building 8, Wangjing Dongyuan District 4, Chaoyang District, Beijing 100102 Applicant before: Beijing Chehejia Information Technology Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180508 |