CN105760519A - Cluster file system and file lock allocation method thereof - Google Patents
Cluster file system and file lock allocation method thereof Download PDFInfo
- Publication number
- CN105760519A CN105760519A CN201610108914.9A CN201610108914A CN105760519A CN 105760519 A CN105760519 A CN 105760519A CN 201610108914 A CN201610108914 A CN 201610108914A CN 105760519 A CN105760519 A CN 105760519A
- Authority
- CN
- China
- Prior art keywords
- file
- file lock
- locking request
- lock
- module
- 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.)
- Granted
Links
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/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
-
- 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/17—Details of further file system functions
- G06F16/176—Support for shared access to files; File sharing support
- G06F16/1767—Concurrency control, e.g. optimistic or pessimistic approaches
- G06F16/1774—Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
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)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a cluster file system and a file lock allocation method thereof.The method includes the steps that an agent module acquires file locks for a file from a file lock module and receives multiple first locking requests for the file from multiple service clients; a waiting queue is established for the multiple first locking requests according to the timing sequence, the multiple first locking requests are responded to in sequence according to the waiting queue, and the file locks are allocated to be possessed by the corresponding service clients; when all the service clients do not possess the file lock any more, the waiting queue is empty and no new first locking request is received within a subsequent preset duration, the file locks are released; in the state that the agent module does not possess file locks, the file lock module receives second locking requests from restored clients, and the file locks are allocated to be possessed by the restored clients.By means of the cluster file system and the file lock allocation method thereof, front-end services are not influenced in data restoration, the performance of the front-end services is guaranteed, hardware resources are fully utilized, and user cost is lowered.
Description
Technical field
The present invention relates to technical field of data processing, particularly relate to a kind of cluster file system and file lock distribution method thereof.
Background technology
Cluster file system refers to and operates on multiple stage computer, between intercom thus by memory space resource consolidations all in cluster, virtualization the file system externally providing file access services mutually by certain mode.They are different from the purpose of the local file systems such as NTFS, EXT, and the former is for autgmentability, and the latter operates in stand-alone environment, mapping between pure management block and file and file attribute.Cluster file system has the feature of High Availabitity; namely refer to when cluster file system suffers human operational error or natural fault etc.; normal file access still it is provided that in certain limit; it is generally adopted copy or data are protected by erasure techniques, need to carry out data syn-chronization after redundant data degradation after calamity；In the process that above-mentioned file access and data syn-chronization are repaired, apply file lock mechanism, even file is only capable of the user being held file lock and accesses.
Existing cluster file system is when the data carrying out file are repaired, recover data to be physically separated with front-end business generally by dividing the network segment, although eliminating the bandwidth conflict of front-end business data, but the process pressure interference between front-end business and data cannot be avoided to repair, cause the read-write requests that can affect front-end business when data are repaired, and user needs the data occurred for low probability to recover to increase physical link, adds hardware cost and management operating cost undoubtedly.
Summary of the invention
In view of this, it is an object of the invention to propose a kind of cluster file system and file lock distribution method thereof, when making data repair, do not affect front-end business, ensure front-end business performance, embodying cluster file system High Availabitity feature, abundant multiplexing utilizes hardware resource, and then reduces user cost.
Based on the file lock distribution method of above-mentioned purpose a kind of cluster file system provided by the invention, described cluster file system includes: file lock module, proxy module；Described method includes:
Described proxy module obtains the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module；
The plurality of first locking request is set up waiting list according to sequential by described proxy module, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds；
Described proxy module monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
When described proxy module does not hold file lock, described file lock module receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
Preferably, described file lock module further comprises the steps of: after file lock distributing to reparation client holding
Reparation client described in file lock module monitors is held file lock and is carried out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client discharge its file lock held.
Preferably, described default word length is 128k.
Preferably, the plurality of first locking request is set up waiting list according to sequential by described proxy module, respond the plurality of first locking request successively by described waiting list order, described file lock is distributed to after corresponding service customer end holds, further comprise the steps of:
Described proxy module judges currently to hold locking next locking interval required by the first locking request in interval and described waiting list and whether existing and conflict of the service customer end of file lock, if so, then next first locking request described is held in described waiting list；If it is not, then respond next first locking request described.
Preferably, described preset duration is: 0-10s.
On the other hand, present invention also offers a kind of cluster file system applying as above method described in any one, it includes the file lock module for distributing file lock, also includes:
Proxy module, for obtaining the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module；The plurality of first locking request is set up waiting list according to sequential, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds；Monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
Described file lock module is further used for when described proxy module does not hold file lock, receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
Preferably, described file lock module is further used for: monitors described reparation client and holds file lock and carry out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client discharge its file lock held.
Preferably, described default word length is 128k.
Preferably, described proxy module is further used for: judge currently to hold the locking next locking interval required by the first locking request in interval and described waiting list and whether exist and conflict of service customer end of file lock, if so, then next first locking request described is held in described waiting list；If it is not, then respond next first locking request described.
Preferably, described preset duration is: 0-10s.
From the above it can be seen that cluster file system provided by the invention and file lock distribution method thereof, front-end business process and data are repaired process and carry out logic isolation, do not affect front-end business when making data repair, specifically include following advantage:
(1) when front end service customer end has access request, Back end data synchronizes reparation and can wait.
(2) reduce factor data while ensureing business datum safety and synchronize the impact on front-end business, reduce hardware cost and operation management cost.
(3) rear end can automatically utilize the free time of front-end access or access pressure less period and carry out data syn-chronization reparation, while not affecting front-end business, shortens the time window that data syn-chronization is repaired as far as possible, improves data safety.
(4) get involved without expert engineer, reduce operation maintenance cost.
(5) data syn-chronization reparation can with front-end business logic isolation, it is to avoid IO conflict affects front-end business performance.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the file lock distribution method flow chart of the cluster file system of the embodiment of the present invention；
Fig. 2 is the cluster file system structural representation of the embodiment of the present invention.
Detailed description of the invention
For making the object, technical solutions and advantages of the present invention clearly understand, below in conjunction with specific embodiment, and with reference to accompanying drawing, the present invention is described in more detail.
It should be noted that, in the embodiment of the present invention, the statement of all uses " first " and " second " is for the parameter of entity or the non-equal distinguishing two same names non-equal, visible " first " " second " is only for the convenience of statement, should not be construed as the restriction to the embodiment of the present invention, this is no longer illustrated by subsequent embodiment one by one.
Embodiments provide a kind of cluster file system and file lock distribution method thereof.Existing cluster file system generally all includes file lock module, is used for distributing file lock, its concrete meeting locking request for certain file according to client, file lock is distributed to corresponding client and holds；After client completes its set work, file lock being discharged, now namely file lock can be assigned to other client.In the embodiment of the present invention, the file lock of use can be Read-Write Locks or mutual exclusion lock, uses different types of file lock not affect technique effect of the invention process, and the concrete function of above-mentioned all types of file lock is prior art, no longer describes in detail in description.For above-mentioned client, generally comprise service customer end and repair client.Service customer end is normally at system front end, is used by user, carries out front-end business process by service customer end；Repair client and be normally at System Back-end, be same as the data repair process carrying out file.
In the present embodiment, described cluster file system includes: file lock module and proxy module.Wherein, file lock module is the same with prior art, and user distributes file lock；Proxy module is the proprietary module of the present invention, for the locking request (being the first locking request in the present embodiment) from service customer end is allocated management.Concrete, the file lock distribution method of the cluster file system of the present embodiment, comprise the following steps:
Described proxy module obtains the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module；
The plurality of first locking request is set up waiting list according to sequential by described proxy module, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds；
Described proxy module monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
When described proxy module does not hold file lock, described file lock module receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
Visible by above-described embodiment, the file lock distribution method of the cluster file system of the present invention, by the first locking request from service customer end is carried out isolation in logic with the second locking request carrying out selfreparing client, make the priority of the first locking request higher than the second locking request；In effect, when front-end business has access request, data syn-chronization is repaired process and can be dodged；If Back end data synchronization reparation process can almost can carry out to full capacity when front end is without Operational Visit.Further, lock priority by the setting of preset duration, flexible service customer end and reparation client, control to repair the synchronizing speed of client so that it is reusable physical link, save user cost.Additionally, the method for the present invention is also applicable to and multiple data protection algorithms, such as redundant copy, correcting and eleting codes technology etc.；It is readily adaptable for use in other backend synchronization demands, such as Bedding storage, data reequilibrate etc..
With reference to Fig. 1, for the file lock distribution method flow chart of the cluster file system of the embodiment of the present invention.
As specific embodiment, a file lock distribution method for described cluster file system more, comprise the following steps:
Step 101, described proxy module obtain the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module.
For certain file in cluster file system, service customer end generally refers to, for this document locking request, the locking request interval for file different pieces of information that same service customer end sends, and the locking request for file that different business client sends, above-mentioned locking request is called the first locking request in the present embodiment.
In this step, first proxy module obtains file lock from file lock module.When proxy module holds file lock, the first locking request from service customer end all can be sent to proxy module and process.
The plurality of first locking request is set up waiting list according to sequential by step 102, described proxy module, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds.
For multiple first locking request received, first setting up waiting list according to its time sequencing, in waiting list, multiple first locking request were arranged in order to the order in evening by morning according to the time.It follows that respond successively according to the first locking request orders multiple in waiting list, and further file lock is distributed to corresponding service customer end and hold.That is, the service customer end currently holding file lock completes work by after file lock release, file lock will not provide equal acquisition chance to other all of locking request issuing sides, but according to waiting list, file lock is distributed to the next service customer end sending the first locking request in waiting list.
Step 103, described proxy module judge currently to hold locking next locking interval required by the first locking request in interval and described waiting list and whether existing and conflict of the service customer end of file lock, if so, then perform step 104；If it is not, then perform step 105.
In this step, when a service customer end currently holds file lock, further judge in waiting list to lock interval whether conflict with the locking interval existence of the service customer end currently holding file lock required by next first locking request.Described locking interval refers to, the required paper interval locked of the first locking request that different service customer ends sends, and locks interval existence conflict and refers to that both intervals that locks exist the part of overlap；Lock interval and be absent from the interval part being absent from overlap of the locking referring to both of conflicting, when locking the part that interval is absent from overlap again, file lock then can be simultaneously allocated to corresponding two service customer ends hold simultaneously, when these two service customer ends complete respective file data access work, conflict will not be produced.
Step 104, next first locking request described is held in described waiting list.
Currently hold file lock service customer end lock in interval and described waiting list the locking district required by next first locking request exist conflict time, next first locking request is held in waiting list, after file lock is discharged by the service customer end currently holding file lock, file lock is being distributed to the service customer end sending next the first locking request in waiting list.
Step 105, response next first locking request described.
Currently hold file lock service customer end lock in interval and described waiting list the locking district required by next first locking request be absent from conflicting time, next first locking request in response waiting list, is simultaneously allocated to send the service customer end of next the first locking request by file lock.
Step 106, described proxy module monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock.
In this step, the state of file lock can be continued to monitor, all discharge and waiting list is for time empty when monitoring the file lock that all service customer ends hold, when further continuing do not monitor the first new locking request of reception and add waiting list in follow-up preset duration, described file lock is discharged.Concrete, the optional of described preset duration ranges for: 0-10s；Preferred preset duration is set to 1s.
Step 107, when described proxy module does not hold file lock, described file lock module receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
After the proxied module release of file lock, file lock module is able to receive that and responds the second locking request of selfreparing client, according to the second described locking request, file lock is distributed to reparation client hold, repair after client holds file lock and namely start described file is carried out data syn-chronization reparation.
Reparation client described in step 108, file lock module monitors is held file lock and is carried out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client discharge its file lock held.
Hold file lock being distributed to reparation client, repair client and hold in the process that described file is carried out data syn-chronization reparation by file lock, monitor described reparation client to hold file lock and carry out the progress of file reparation, when repair data reaches to preset word length, send instruction at once, make reparation client discharge its file lock held.As preferably, described default word length is 128k.
By this step, hold file lock and carry out the duration of data syn-chronization reparation by repairing client and limit, repair client and want to continue to data syn-chronization when repairing, it is necessary to resend the second locking request, file lock so can be made as much as possible to have service customer end to hold, it is preferable that business data processing.
With reference to Fig. 2, for the cluster file system structural representation of the embodiment of the present invention.
On the other hand, the embodiment of the present invention additionally provides a kind of cluster file system, and this cluster file system applies the file lock distribution method as described in above-described embodiment.Described cluster file system, except including the file lock module 201 for distributing file lock, also includes: proxy module 202.
In the present embodiment, described proxy module 202 is for obtaining the file lock for a file reception from multiple service customer ends 203 multiple first locking request to this document from described file lock module 201；The plurality of first locking request is set up waiting list according to sequential, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end 203 and holds；Monitoring file lock state, when all service customer ends 203 all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
Additionally, in the present embodiment, described file lock module 201 is further used for when described proxy module 202 does not hold file lock, receive come selfreparing client 204 the second locking request, and file lock is distributed to reparation client 204 hold.
In a preferred embodiment, described file lock module 201 is further used for: monitors described reparation client 204 and holds file lock and carry out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client 204 discharge its file lock held.Wherein, described default word length is 128k.
In a preferred embodiment, described proxy module 202 is further used for: judge currently to hold the locking next locking interval required by the first locking request in interval and described waiting list and whether exist and conflict of service customer end 203 of file lock, if so, then next first locking request described is held in described waiting list；If it is not, then respond next first locking request described.Wherein, described preset duration is: 0-10s；Preferably, described preset duration is 1s.
Those of ordinary skill in the field are it is understood that the discussion of any of the above embodiment is exemplary only, it is not intended that hint the scope of the present disclosure (including claim) is limited to these examples；Under the thinking of the present invention, can also be combined between technical characteristic in above example or different embodiment, step can realize with random order, and there are other changes many of the different aspect of the present invention as above, for they not offers in details simple and clear.Therefore, all within the spirit and principles in the present invention, any omission of making, amendment, equivalent replacement, improvement etc., should be included within protection scope of the present invention.
Claims (10)
1. the file lock distribution method of a cluster file system, it is characterised in that described cluster file system includes: file lock module, proxy module；Described method includes:
Described proxy module obtains the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module；
The plurality of first locking request is set up waiting list according to sequential by described proxy module, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds；
Described proxy module monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
When described proxy module does not hold file lock, described file lock module receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
2. method according to claim 1, it is characterised in that described file lock module further comprises the steps of: after file lock distributing to reparation client holding
Reparation client described in file lock module monitors is held file lock and is carried out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client discharge its file lock held.
3. method according to claim 2, it is characterised in that described default word length is 128k.
4. method according to claim 1, it is characterized in that, the plurality of first locking request is set up waiting list according to sequential by described proxy module, the plurality of first locking request is responded successively by described waiting list order, described file lock is distributed to after corresponding service customer end holds, further comprise the steps of:
Described proxy module judges currently to hold locking next locking interval required by the first locking request in interval and described waiting list and whether existing and conflict of the service customer end of file lock, if so, then next first locking request described is held in described waiting list；If it is not, then respond next first locking request described.
5. method according to claim 1, it is characterised in that described preset duration is: 0-10s.
6. a cluster file system for application method as described in claim 1 to 5 any one, including the file lock module for distributing file lock, it is characterised in that also include:
Proxy module, for obtaining the file lock for a file reception from multiple service customer ends multiple first locking request to this document from described file lock module；The plurality of first locking request is set up waiting list according to sequential, responds the plurality of first locking request successively by described waiting list order, described file lock is distributed to corresponding service customer end and holds；Monitoring file lock state, when all service customer ends all no longer hold described file lock and described waiting list is empty and is not received by the first new locking request in follow-up preset duration, discharges described file lock；
Described file lock module is further used for when described proxy module does not hold file lock, receive come selfreparing client the second locking request, and file lock is distributed to reparation client hold.
7. cluster file system according to claim 6, it is characterized in that, described file lock module is further used for: monitors described reparation client and holds file lock and carry out the progress of file reparation, when repair data reaches to preset word length, makes described reparation client discharge its file lock held.
8. cluster file system according to claim 7, it is characterised in that described default word length is 128k.
9. cluster file system according to claim 1, it is characterized in that, described proxy module is further used for: judge currently to hold the locking next locking interval required by the first locking request in interval and described waiting list and whether exist and conflict of service customer end of file lock, if so, then next first locking request described is held in described waiting list；If it is not, then respond next first locking request described.
10. cluster file system according to claim 1, it is characterised in that described preset duration is: 0-10s.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610108914.9A CN105760519B (en) | 2016-02-26 | 2016-02-26 | Cluster file system and file lock distribution method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610108914.9A CN105760519B (en) | 2016-02-26 | 2016-02-26 | Cluster file system and file lock distribution method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105760519A true CN105760519A (en) | 2016-07-13 |
| CN105760519B CN105760519B (en) | 2020-08-28 |
Family
ID=56331374
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610108914.9A Active CN105760519B (en) | 2016-02-26 | 2016-02-26 | Cluster file system and file lock distribution method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105760519B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107016094A (en) * | 2017-04-06 | 2017-08-04 | 深圳创维－Rgb电子有限公司 | A kind of project shared file multi-person synergy development approach, apparatus and system |
| CN107181789A (en) * | 2017-03-31 | 2017-09-19 | 北京奇艺世纪科技有限公司 | A kind of distributed lock implementation method and device |
| CN107423454A (en) * | 2017-09-22 | 2017-12-01 | 郑州云海信息技术有限公司 | The processing method of file lock, device and equipment in a kind of distributed file system |
| CN109412891A (en) * | 2018-10-19 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of method and apparatus detecting client state |
| CN109408477A (en) * | 2018-10-09 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of method, system and associated component that setting group document is locked |
| CN109743366A (en) * | 2018-12-21 | 2019-05-10 | 苏宁易购集团股份有限公司 | A kind of resource locking method, apparatus and system for scene of more living |
| CN110008031A (en) * | 2018-01-05 | 2019-07-12 | 北京金山云网络技术有限公司 | Apparatus operation method, group system, electronic equipment and read/write memory medium |
| WO2020063373A1 (en) * | 2018-09-29 | 2020-04-02 | 华为技术有限公司 | Data storage method, metadata server, and client |
| CN113760369A (en) * | 2020-09-29 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Concurrent thread processing method, concurrent thread processing device, electronic equipment and storage medium |
| CN114116639A (en) * | 2022-01-27 | 2022-03-01 | 苏州浪潮智能科技有限公司 | Method, device, equipment and medium for setting cluster file lock |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5828876A (en) * | 1996-07-31 | 1998-10-27 | Ncr Corporation | File system for a clustered processing system |
| CN1945539A (en) * | 2006-10-19 | 2007-04-11 | 华为技术有限公司 | Method for distributing shared resource lock in computer cluster system and cluster system |
| CN103488526A (en) * | 2013-09-02 | 2014-01-01 | 用友软件股份有限公司 | System and method for locking business resource in distributed system |
| CN103514298A (en) * | 2013-10-16 | 2014-01-15 | 浪潮(北京)电子信息产业有限公司 | Method for achieving file lock and metadata server |
| CN103795801A (en) * | 2014-02-12 | 2014-05-14 | 浪潮电子信息产业股份有限公司 | Metadata group design method based on real-time application group |
| CN104484236A (en) * | 2014-11-28 | 2015-04-01 | 曙光云计算技术有限公司 | HA (high availability) access adaptation method |
-
2016
- 2016-02-26 CN CN201610108914.9A patent/CN105760519B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5828876A (en) * | 1996-07-31 | 1998-10-27 | Ncr Corporation | File system for a clustered processing system |
| CN1945539A (en) * | 2006-10-19 | 2007-04-11 | 华为技术有限公司 | Method for distributing shared resource lock in computer cluster system and cluster system |
| CN103488526A (en) * | 2013-09-02 | 2014-01-01 | 用友软件股份有限公司 | System and method for locking business resource in distributed system |
| CN103514298A (en) * | 2013-10-16 | 2014-01-15 | 浪潮(北京)电子信息产业有限公司 | Method for achieving file lock and metadata server |
| CN103795801A (en) * | 2014-02-12 | 2014-05-14 | 浪潮电子信息产业股份有限公司 | Metadata group design method based on real-time application group |
| CN104484236A (en) * | 2014-11-28 | 2015-04-01 | 曙光云计算技术有限公司 | HA (high availability) access adaptation method |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107181789A (en) * | 2017-03-31 | 2017-09-19 | 北京奇艺世纪科技有限公司 | A kind of distributed lock implementation method and device |
| CN107016094A (en) * | 2017-04-06 | 2017-08-04 | 深圳创维－Rgb电子有限公司 | A kind of project shared file multi-person synergy development approach, apparatus and system |
| CN107016094B (en) * | 2017-04-06 | 2020-11-17 | 深圳创维－Rgb电子有限公司 | Project shared file multi-person collaborative development method, device and system |
| CN107423454A (en) * | 2017-09-22 | 2017-12-01 | 郑州云海信息技术有限公司 | The processing method of file lock, device and equipment in a kind of distributed file system |
| US11416313B2 (en) | 2018-01-05 | 2022-08-16 | Beijing Kingsoft Cloud Network Technology Co., Ltd. | Equipment control method, cluster system , electronic device and readable storage medium |
| CN110008031B (en) * | 2018-01-05 | 2022-04-15 | 北京金山云网络技术有限公司 | Device operation method, cluster system, electronic device and readable storage medium |
| CN110008031A (en) * | 2018-01-05 | 2019-07-12 | 北京金山云网络技术有限公司 | Apparatus operation method, group system, electronic equipment and read/write memory medium |
| CN110968563A (en) * | 2018-09-29 | 2020-04-07 | 华为技术有限公司 | Data storage method, metadata server and client |
| WO2020063373A1 (en) * | 2018-09-29 | 2020-04-02 | 华为技术有限公司 | Data storage method, metadata server, and client |
| CN110968563B (en) * | 2018-09-29 | 2023-11-17 | 华为技术有限公司 | Data storage method, metadata server and client |
| CN109408477A (en) * | 2018-10-09 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of method, system and associated component that setting group document is locked |
| CN109412891B (en) * | 2018-10-19 | 2022-04-22 | 郑州云海信息技术有限公司 | Method and device for detecting client state |
| CN109412891A (en) * | 2018-10-19 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of method and apparatus detecting client state |
| CN109743366A (en) * | 2018-12-21 | 2019-05-10 | 苏宁易购集团股份有限公司 | A kind of resource locking method, apparatus and system for scene of more living |
| CN113760369A (en) * | 2020-09-29 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Concurrent thread processing method, concurrent thread processing device, electronic equipment and storage medium |
| CN114116639A (en) * | 2022-01-27 | 2022-03-01 | 苏州浪潮智能科技有限公司 | Method, device, equipment and medium for setting cluster file lock |
| CN114116639B (en) * | 2022-01-27 | 2022-04-29 | 苏州浪潮智能科技有限公司 | Method, device, equipment and medium for setting cluster file lock |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105760519B (en) | 2020-08-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105760519A (en) | Cluster file system and file lock allocation method thereof | |
| CN106662983B (en) | The methods, devices and systems of data reconstruction in distributed memory system | |
| US20210011817A1 (en) | Virtual Machine Recovery Method and Virtual Machine Management Device | |
| US7809887B2 (en) | Computer system and control method for the computer system | |
| CN101808137B (en) | Data transmission method, device and system | |
| CN101136728A (en) | Cluster system and method for backing up a replica in a cluster system | |
| JP2007317186A (en) | Method and device for managing backup data and journal | |
| CN109032837A (en) | The method and apparatus of data backup | |
| CN111651275A (en) | MySQL cluster automatic deployment system and method | |
| CN106325768B (en) | A kind of two-shipper storage system and method | |
| CN105357042A (en) | High-availability cluster system, master node and slave node | |
| US9298765B2 (en) | Apparatus and method for handling partially inconsistent states among members of a cluster in an erratic storage network | |
| CN108932180A (en) | A kind of disaster tolerance management method, device, storage medium and computer equipment matter | |
| US9092396B2 (en) | Standby system device, a control method, and a program thereof | |
| CN113407637A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN103516734A (en) | Data processing method, device and system | |
| CN103428288A (en) | Method for synchronizing copies on basis of partition state tables and coordinator nodes | |
| US8359601B2 (en) | Data processing method, cluster system, and data processing program | |
| CN113190620B (en) | Method, device, equipment and storage medium for synchronizing data between Redis clusters | |
| CN104052799B (en) | A kind of method that High Availabitity storage is realized using resource ring | |
| JP5154843B2 (en) | Cluster system, computer, and failure recovery method | |
| CN109257403B (en) | Data storage method and device and distributed storage system | |
| WO2023019953A1 (en) | Data synchronization method and system, server, and storage medium | |
| CN105511808A (en) | Data operation method, system and related device | |
| CN108279850B (en) | Data resource storage method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210902 Address after: 271024 Taishan science and Technology Industrial Park, high tech Zone, Tai'an City, Shandong Province Patentee after: Shandong whale shark Information Technology Co.,Ltd. Address before: 100195 Room 101, 1st floor, building 31, yuquanhuigu, No.3 minzhuang Road, Yuquanshan, Haidian District, Beijing Patentee before: PERABYTES TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |