Patent AU-2015408848-B2 (AU)
Title: Method for processing acquire lock request and server
Inventor: FENG RUI
IPC: G06F9/00
Filed: 2015-12-30
Granted: 2018-10-18
Abstract: (12) tflIA*&PieSA *iW (10) (43)E~# WO 2017/113261 A1 2017 * 7,P] 6 (06.07.2017) W IPO I PCT (51) 0 3 * : CU, CZ, DE, DK, DM, DO, DZ, EC, EE, EG, ES, Fl, GB, H04L 12/24 (2006.01) GD, GE, GH, GM, GT, HN, HR, HU, ID, IL, IN, IR, IS, JP, KE, KG, KN, KP, KR, KZ, LA, LC, LK, LR, LS, LU, (21) RI$ tI: PCT/CN2015/100006 LY, MA, MD, ME, MG, MK, MN, MW, MX, MY, MZ, (22) l : 2015 12 A 30 H (30.12.2015) NA, NG, NI, NO, NZ, OM, PA, PE, PG, PH, PL, PT, QA, RO, RS, RU, RW, SA, SC, SD, SE, SG, SK, SL, SM, ST, (25) $4*c: SV, SY, TH, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, (26) VC, VN, ZA, ZM, ZWO (26) IP* : $Thkq HttPW{8 (71) $ CA: $ LTD)[NCN (HUAWEI TECHNO- tV[): ARIPO (BW, GH, GM, KE, LR, LS, MW, MZ, NA, LOGIES CO., LTD.) [CN/CN]; , G 5129 RW, SD, SL, ST, SZ, TZ, UG, ZM, ZW), rV A (AM, AZ, sj 2 I t& H % -N & Guangdong 518129 BY, KG, KZ, RU, TJ, TM), rU)II (AL, AT, BE, BG, CH, (CN)o CY, CZ, DE, DK, EE, ES, Fl, FR, GB, GR, HR, HU, IE, (72) TLA: A (FENG, Rui); : N F_ IV [ R2 IS, IT, LT, LU, LV, MC, MK, MT, NL, NO, PL, PT, RO, I N tAftlt , Guangdong 518129 (CN) o RS, SE, SI, SK, SM, TR), OAPI (BF, BJ, CF, CG, CI, CM, I$ (CHEN, Guang); [FF I' W1[11TIM N l GA, GN, GQ, GW, KM, ML, MR, NE, SN, TD, TG)O H $ht9d$$t&Ak, Guangdong 518129 (CN) o tIkj & |[ijDJ 4.17 flM#fl: (LIU, Jun); :FF1N [- ST Vt HR _) I [ M ExdN4.17(i) )mt, Guangdong 518129 (CN)o t) AE, AG, AL, AM, AO, AT, AU, AZ, BA, BB, BG, i 21 ( BH, BN, BR, BW, BY, BZ, CA, CH, CL, CN, CO, CR, (54) Title: LOCKING REQUEST PROCESSING METHOD AND SERVER =(54) U# ntt S K4 tm 2Frl ,i T I 1(57) Abstract: Proposed is a lock request pro -um , m+Tna?' cessing technology. A first lock server is a takeover 309 lock server of a second lock server; the first lock server enters a silence state after learning that the second lock server has a fault; a silence range is a 303 resource, to which the second lock server has alloc ated a permission, and the first lock server receives a locking request originally sent to the second lock BB server; and if the second lock server has not alloc H01 MANAGKERSENA ANTFICATION ated a permission to the resource, the first lock serv S'A t MESSAGE TOATARGET OCO SERVER ANDTHE er allocates a lock permission to the corresponding 302 THE TARGET LOCK SERVER RECEIVING A LOCKING REITA T LOF AUSER WERECEIN A LOCKING resource according to the locking request. By apply ;6 REQUEST CARRIES FIRST RESOURCE -. tharngby he '"' DENT F AN OFA F ESURCE ing the solution, a range affected by the occurrence - ~~~~~~~~~REQUETING LOCKINOGfafuti ok cnb hrb TH TARGET LOCK SERVER QUERYING WHETHER of a fault in a lock server can be reduced, thereby A FIRST RESOURCE INFORMATION LIST RECORDS improving the stability of the management system. 307 nas ALOCATINO THE LOCK PERM SS ON ACCORDING (57) : A I, rn R IA A t ~~~TO THELOCKING REQUEST ANDAVING THE (5)jq: M 4 t >v FSREOREOBJECT IENTIFICAION IN THE F RST RESOURCE INFORMATION LSFTT _tnJvt~A--f~ t F:V"E ' 306 THE FIRST LOCK SERVE BCKING UP THE FIRST 3O 3 RESOURCE DENTIFCATION TO ASECOND ~ ~ td~ ~~~~i if~td7 DR.M -%f~ RESOURCE INFORMATION RECORD LIST 4 307 THE FIRST LOCK SERVER LEAVING AS NSHIP 07STATE ANDTUPDATING TAKEOVER ETOkSON-13 Y ~ l 30 EETING THE FIRST RESOURCE INFORMATION rsl ~~RECORD LISTKOATN 309 RECEIVING A LOCK RE-APPJCATION REQUEST RE MISSIONN INFORMATION CARRIED INTHE LOCKMRf,1 -/ RE-APPLICATION REQUEST AS NO~ o Z~tfr~j ,rMtktWtWfl