Enterprise-level Distributed File Service Unified Management Method and System

Abstract

The present invention provides an enterprise-level unified management method and system for distributed file services, including: configuring a gateway service and distributed file system metadata, and the control center service constructs a management n-ary tree based on the metadata; the gateway service establishes a health monitoring with the distributed file system and registers the gateway service as a child node, and the corresponding distributed file system as a leaf node; the control center service obtains child node information according to the management n-ary tree and distributes meta-information to the corresponding child nodes, and the gateway service independently provides storage services externally; the control center service synchronizes the management n-ary tree to the request distribution center service, and according to the management n-ary tree information, the request distribution center service distributes the requests for the system-level user global files to the gateway services that meet the requirements. The present invention takes the control center service and the request distribution center service as the core, is compatible with multiple types of distributed file systems, and realizes the unified management of multi-location and multi-center distributed file systems and the high availability of file data storage.

Description

Technical Field

[0001] The present invention relates to the technical field of enterprise storage systems, and in particular to an enterprise-level distributed file service unified management method and system. Background Art

[0002] Currently, system services that require access to distributed file storage systems have varying requirements for underlying storage. When migrating existing storage systems, it's important to consider the usage habits of the development and operations personnel of the accessed systems to avoid issues with the storage system after the switch. When file storage services rely on a single distributed storage system, they inevitably encounter issues that require rapid repair and response. While manual maintenance can be used for remedial, unremediable system-level issues, replacing the underlying distributed storage is the only option. This creates immeasurable systemic risks.

[0003] Chinese patent publication CN114490536 A discloses a centralized management and control design for a single storage system, "Distributed File Management Service Center Based on the Lightweight File System FastDFS." While this design supports the management and control of a distributed file storage system in a single computer room, it cannot guarantee effective disaster recovery switching and rapid response in the event of a zero-day failure for FastDFS. Furthermore, the deployment of management and control in each computer room prevents effective single-entry management and control, effectively reducing operational and maintenance tasks. Summary of the invention

[0004] In view of the deficiencies in the prior art, the present invention aims to provide an enterprise-level distributed file service unified management method and system.

[0005] According to the present invention, a method for unified management of enterprise-level distributed file services includes the following steps:

[0006] Step S1: Configure the gateway service and the corresponding distributed file system metadata, and the control center service builds a management n-ary tree based on the metadata;

[0007] Step S2: The gateway service establishes a health monitoring relationship with the distributed file system it manages, and registers the gateway service as a child node and the corresponding distributed file system as a leaf node.

[0008] Step S3: The control center service obtains the child node information according to the management n-ary tree and distributes the metadata to the corresponding child nodes. The gateway service independently provides storage services to the outside world.

[0009] Step S4: The control center service synchronously manages the n-ary tree to request the distribution center service, and requests the distribution center service to distribute the system-level user global file request to the gateway service that meets the requirements according to the management n-ary tree information.

[0010] Preferably, step S1 includes:

[0011] Step S1.1: Configure gateway service metadata, including: service unique encoding, managed interface path, storage capacity, deployment area, access type, storage type, accessing users, and user permissions;

[0012] Step S1.2: Configure distributed file system metadata, including: connection information, storage capacity, system type, and deployment information;

[0013] Step S1.3: Use the service number of the management and control center service itself as the root node, and subsequent child nodes and leaf nodes are registered in the management and control center service.

[0014] Preferably, step S2 includes:

[0015] Step S2.1: Through the registration of the gateway service, the management and control center service adds the gateway service number information under the management n-ary tree;

[0016] Step S2.2: Generate an n-ary tree with horizontal sorting of child nodes according to the breadth-first traversal algorithm;

[0017] Step S2.3: The gateway service performs health monitoring on the distributed file system within its jurisdiction through the self-carried metadata information;

[0018] Step S2.4: The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management n-ary tree;

[0019] Step S2.5: When the distributed file system type is FastDFS, adopt the reserved strategy. When the distributed file system type is MinIO, the file number takes the bucket as the core, and adopt the strategy of manual complement to synchronize with the file number of FastDFS;

[0020] Step S2.6: According to the types of master and slave nodes, construct the automatic synchronization and disaster recovery tasks of master and slave nodes;

[0021] Step S2.7: Based on the health monitoring strategy, the gateway service promptly alarms the downed service and establishes a master-slave switching mechanism.

[0022] Preferably, step S3 includes:

[0023] Step S3.1: The management and control center service distributes the newly created and changed gateway service metadata according to the management n-ary tree;

[0024] Step S3.2: Based on the user information distributed by the management and control center service, the gateway service completes the permission judgment and capacity determination during user access;

[0025] Step S3.3: The gateway service monitors the disk status of the server where the distributed system is located based on the distributed system connection information.

[0026] Preferably, step S4 includes:

[0027] Step S4.1: When the control center service synchronizes the management n-tree with the request distribution center service through the shared cache, the request distribution center service periodically synchronizes the management n-tree to the backup database; when the request distribution center service cannot obtain the management n-tree in the shared cache, it directly calls the control center service interface to obtain the latest management n-tree

[0028] Step S4.2: When the latest management n-ary tree can be obtained, synchronize the current management n-ary tree to the backup database and update the backup time. If the latest management n-ary tree cannot be obtained, request the distribution center service to obtain the scheduled backup management n-ary tree from the database;

[0029] Step S4.3: When a system-level user requests a file in high-availability mode, the distribution center service is requested to retrieve and manage the n-ary tree, obtain and request a gateway service that is redirected to the nearest area.

[0030] An enterprise-level distributed file service unified management system provided by the present invention includes the following modules:

[0031] Module M1: Configures the gateway service and the corresponding distributed file system metadata. The control center service builds a management n-ary tree based on the metadata.

[0032] Module M2: The gateway service establishes health monitoring with the distributed file system it manages, and registers the gateway service as a child node, and the corresponding distributed file system as a leaf node;

[0033] Module M3: The control center service obtains child node information based on the management n-ary tree and distributes metadata to the corresponding child nodes. The gateway service independently provides storage services to the outside world.

[0034] Module M4: The control center service synchronously manages the n-ary tree to request the distribution center service, and requests the distribution center service to distribute the system-level user global file request to the gateway service that meets the requirements based on the management n-ary tree information.

[0035] Preferably, the module M1 includes:

[0036] Module M1.1: Configure the gateway service metadata, including: service unique code, management interface path, storage capacity, deployment area, access type, storage type, access user, and user permissions;

[0037] Module M1.2: Configuring the metadata of the distributed file system includes: connection information, storage capacity, system type, and deployment information;

[0038] Module M1.3: Using the service ID of the control center itself as the root node, subsequent child nodes and leaf nodes are registered in the control center service.

[0039] Preferably, the module M2 includes:

[0040] Module M2.1: The control center service adds the gateway service ID information under the management n-ary tree through the registration of the gateway service;

[0041] Module M2.2: Generating an n-ary tree with horizontally sorted child nodes according to the breadth-first traversal algorithm;

[0042] Module M2.3: The gateway service performs health monitoring on the distributed file system within its jurisdiction through the self-carried metadata information;

[0043] Module M2.4: The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management n-ary tree;

[0044] Module M2.5: When the distributed file system type is FastDFS, a reserved strategy is adopted. When the distributed file system type is MinIO, the file number takes the bucket as the core, and an artificial filling strategy is adopted to synchronize with the file number of FastDFS;

[0045] Module M2.6: Constructing the automatic synchronization and disaster recovery tasks of the master and slave nodes according to the types of the master and slave nodes;

[0046] Module M2.7: Based on the health monitoring strategy, the gateway service promptly alarms the downed service and establishes a master-slave switching mechanism.

[0047] Preferably, the module M3 includes:

[0048] Module M3.1: The control center service distributes the metadata of the newly created and changed gateway services according to the management n-ary tree;

[0049] Module M3.2: The gateway service completes the permission judgment and capacity determination during user access based on the user information distributed by the control center service;

[0050] Module M3.3: The gateway service monitors the disk conditions of the servers where the distributed systems are located according to the distributed system connection information.

[0051] Preferably, the module M4 includes:

[0052] Module M4.1: When the control center service synchronizes the management of the n-ary tree with the request distribution center service through the shared cache, the request distribution center service regularly synchronizes the management of the n-ary tree to the backup database; when the request distribution center service cannot obtain the management of the n-ary tree in the shared cache, it directly calls the control center service interface to obtain the latest management of the n-ary tree

[0053] Module M4.2: When the latest management of the n-ary tree can be obtained, synchronize the current management of the n-ary tree to the backup database and update the backup time; when the latest management of the n-ary tree cannot be obtained, the request distribution center service retrieves the regularly backed-up management of the n-ary tree from the database

[0054] Module M4.3: When the system-level user requests a file in the high-availability mode, the request distribution center service retrieves the management of the n-ary tree, obtains and requests to redirect to the gateway service in the nearest area

[0055] Compared with the prior art, the present invention has the following beneficial effects

[0056] 1. Compared with the previous mode of deploying a single type of distributed file system and control middleware in a single center, the unified management method disclosed in the present invention further improves the security of file storage and data high availability through the method of combining n-ary tree service distribution and master-slave structure of leaf nodes. Moreover, the gateway service, as the main body of the traffic service, complements the coverage of the request distribution center service, avoiding the single point of failure of file and service cross-region transmission for system-level users

[0057] 2. The present invention realizes the hierarchical management and utilization of services through the combination of the n-ary tree management structure and Master-Slave distributed high availability

[0058] 3. Through the distributed storage structure with multiple compatibilities, the present invention uses multiple types of distributed storage systems as underlying storage disaster recovery for each other, solving the problem that quick switching or upgrading is required when a single distributed storage system has a 0-DAY bug

[0059] 4. By adding the deployment structure of the intermediate service layer, the present invention solves the problems of no traffic audit and no tenant mode control access system in the traditional distributed file system

[0060] 5. By adopting a structure in which the storage service separates the control from the traffic inlet and outlet, the present invention solves the problems that the single body structure is large, and it is impossible to quickly expand the main traffic service and provide distributed services BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Other features, objects and advantages of the present invention will become more apparent by reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings

[0062] Figure 1 Schematic diagram of the management n-ary tree structure in the present invention;

[0063] Figure 2 Flow chart of user file data transmission in the present invention;

[0064] Figure 3 Functional architecture diagram of the control service center in the present invention;

[0065] Figure 4 Functional architecture diagram of the SDK and service gateway in the present invention. Detailed implementation manners

[0066] The present invention will be described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several changes and improvements can still be made. These all belong to the protection scope of the present invention.

[0067] The present invention discloses an enterprise-level distributed file service unified management method, which takes the control center service and the request distribution center service as the core, is compatible with multiple types of distributed file systems, and realizes the unified management of distributed file systems in multiple locations and multiple centers and the high availability of file data storage. The present invention constructs a management n-ary tree with the control center service as the root node, each center gateway service as the child node, and multiple types of distributed file systems as the leaf nodes based on the n-ary tree data structure and the Master-Slave distributed high availability theory. Among them, each type of distributed file system on the leaf node is a disaster recovery backup for each other and serves as the storage base of the child node gateway service. Compared with the previous mode of deploying a single type of distributed file system and control middleware in a single center, the unified management method of the present invention further improves the security of file storage and data high availability through the combination of the n-ary tree service distribution and the master-slave structure of the leaf nodes. Moreover, the gateway service, as the main body of the traffic service, complements the coverage of the request distribution center service, avoiding the single point of failure of the system-level user's cross-regional file transmission and service.

[0068] Specifically, referring to Figures 1-4 , the present invention includes the following steps:

[0069] Step 1: Configure the gateway service and the corresponding distributed file system metadata, and the control center service constructs a management n-ary tree based on the metadata.

[0070] Specifically, Step 1 includes the following steps:

[0071] 1.1. Configure the following metadata for the gateway service: service unique code, management interface path, storage capacity, deployment area, access type, storage type, access user, and user permissions.

[0072] The unique service code consists of 12 digits: the first four digits represent the area code, digits 5-8 represent the center number, and the last four digits represent the service number.

[0073] 1.2. Configure distributed file system metadata: connection information, storage capacity, system type, and deployment information.

[0074] 1.3. The control center service number itself is used as the root node, waiting for the registration of subsequent child nodes and leaf nodes.

[0075] Step 2: The gateway service establishes health monitoring with the distributed file system under its jurisdiction, and registers itself as a child node through the management tree of the control center service, and the corresponding distributed file system is a leaf node.

[0076] Specifically, step 2 includes the following steps:

[0077] 2.1. The control center service registers the gateway service and adds the gateway service number information under the n-ary tree with it as the root node.

[0078] 2.2. Based on the unordered n-ary tree formed in step 2.1 above, generate an n-ary tree with horizontally sorted child nodes according to the breadth-first traversal algorithm.

[0079] 2.3. The gateway service establishes health monitoring of the distributed systems under its jurisdiction through the metadata information it carries.

[0080] 2.4. The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management tree of the control center.

[0081] 2.5. Based on the type of distributed file system, the following will be explained:

[0082] FastDFS: The file numbering format is rather special and adopts a retention strategy.

[0083] MinIO: File numbering is based on buckets and uses a manual padding strategy to synchronize file numbering with FastDFS.

[0084] 2.6. Perform corresponding operations according to the type of master and slave nodes:

[0085] When the master and slave nodes are of the same type: Use a clustering solution for the corresponding distributed file system. For example, the underlying FastDFS Group synchronization policy is distributed across the master and slave nodes to achieve automatic synchronization and disaster recovery.

[0086] When the master and slave node types are different: By implementing an asynchronous monitoring thread for a folder, a method of automatically synchronizing the folder changes to the slave node when the folder changes occurs.

[0087] 2.7. Based on the health monitoring policy, the gateway service promptly alerts the downed service and establishes a master-slave switching mechanism.

[0088] Step 3: The management center obtains the child node information according to the management tree and distributes the meta-information to the corresponding child nodes. The gateway service independently provides storage services externally based on this.

[0089] Specifically, Step 3 includes the following steps:

[0090] 3.1. The management center service distributes the metadata of the gateway service that has new creations and changes according to the management tree.

[0091] 3.2. The gateway service completes the permission judgment and capacity determination during user access based on the user information distributed by the management center service.

[0092] 3.3. The gateway service monitors the disk conditions of the servers where the distributed systems are located according to the distributed system connection information.

[0093] Step 4: The management center synchronizes the management tree to the request distribution center service. According to the management tree information, the request distribution center service distributes the requests for the system-level user global files to the eligible gateway services.

[0094] Specifically, Step 4 includes the following two situations, which will be described separately:

[0095] Situation 1: Adopt the shared cache strategy: The management center service synchronizes the management tree with the request distribution center service through the shared cache. The request distribution center service synchronizes the management tree to the backup database in the form of a scheduled task.

[0096] Situation 2: Adopt the active acquisition strategy: When the request distribution center service cannot obtain the management tree in the shared cache, it directly calls the management center service interface to obtain the latest management tree.

[0097] Depending on the data acquisition situation, corresponding execution methods are adopted: If the latest management tree can be obtained, synchronize the current management tree to the backup database and update the backup time; if the latest management tree cannot be obtained by calling the management center service interface, the request distribution center service obtains the periodically backed-up management tree from the database.

[0098] When the system-level user requests a file in the high-availability mode, the request distribution center service retrieves the management tree, obtains and requests to redirect to the gateway service in the nearest area.

[0099] The present invention also provides an enterprise-level distributed file service unified management system, which can be implemented by executing the process steps of the enterprise-level distributed file service unified management method, that is, those skilled in the art can understand the enterprise-level distributed file service unified management method as an optimal implementation method of the enterprise-level distributed file service unified management system.

[0100] Enterprise-level distributed file service unified management system, including the following modules:

[0101] Module M1: Configure the gateway service and the corresponding distributed file system metadata. The control center service builds a management n-ary tree based on the metadata.

[0102] Specifically, module M1 includes:

[0103] Module M1.1: Configure the gateway service metadata, including the service unique code, management interface path, storage capacity, deployment area, access type, storage type, access user, and user permissions.

[0104] Module M1.2: Configure distributed file system metadata including: connection information, storage capacity, system type, and deployment information.

[0105] Module M1.3: The control center service number itself is used as the root node, and subsequent child nodes and leaf nodes are registered in the control center service.

[0106] Module M2: The gateway service establishes health monitoring with the distributed file system under its jurisdiction, and registers the gateway service as a child node and the corresponding distributed file system as a leaf node.

[0107] Specifically, module M2 includes:

[0108] Module M2.1: The control center service registers the gateway service and adds the gateway service number information under the management n-ary tree.

[0109] Module M2.2: Generate an n-ary tree with horizontally sorted child nodes based on the breadth-first traversal algorithm.

[0110] Module M2.3: The gateway service monitors the health of the distributed file system under its jurisdiction through the metadata information it carries.

[0111] Module M2.4: The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management n-ary tree.

[0112] Module M2.5: When the distributed file system type is FastDFS, a reserved strategy is adopted. When the distributed file system type is MinIO, the file number takes the bucket as the core, and an artificial padding strategy is adopted to synchronize with the file number of FastDFS.

[0113] Module M2.6: Construct automatic synchronization and disaster recovery tasks for the master and slave nodes according to the types of the master and slave nodes.

[0114] Module M2.7: Based on the health monitoring strategy, the gateway service promptly alarms the downed service and establishes a master-slave switching mechanism.

[0115] Module M3: The control center service obtains the child node information according to the management n-ary tree and distributes the meta information to the corresponding child nodes. The gateway service independently provides storage services externally.

[0116] Specifically, Module M3 includes:

[0117] Module M3.1: The control center service distributes the metadata of the gateway service that generates new and changed data according to the management n-ary tree.

[0118] Module M3.2: The gateway service completes the permission judgment and capacity determination during user access based on the user information distributed by the control center service.

[0119] Module M3.3: The gateway service monitors the disk conditions of the servers where the distributed systems are located according to the distributed system connection information.

[0120] Module M4: The control center service synchronizes the management n-ary tree to the request distribution center service. According to the management n-ary tree information, the request distribution center service distributes the requests for the system-level user global files to the eligible gateway services.

[0121] Specifically, Module M4 includes:

[0122] Module M4.1: When the control center service synchronizes the management n-ary tree with the request distribution center service through the shared cache, the request distribution center service periodically synchronizes the management n-ary tree to the backup database. When the request distribution center service cannot obtain the management n-ary tree in the shared cache, it directly calls the control center service interface to obtain the latest management n-ary tree.

[0123] Module M4.2: When the latest management n-ary tree can be obtained, synchronize the current management n-ary tree to the backup database and update the backup time. When the latest management n-ary tree cannot be obtained, the request distribution center service obtains the periodically backed-up management n-ary tree from the database.

[0124] Module M4.3: When a system-level user requests a file in the high-availability mode, the request distribution center service retrieves and manages the n-ary tree, obtains and requests to redirect to the gateway service in the nearest area.

[0125] Those skilled in the art know that, in addition to implementing the system and its various devices, modules, and units provided by the present invention in the form of pure computer-readable program code, the method steps can be logically programmed to enable the system and its various devices, modules, and units provided by the present invention to be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers, etc. to achieve the same functions. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a kind of hardware component, and the devices, modules, and units included therein for implementing various functions can also be regarded as the structures within the hardware component; the devices, modules, and units for implementing various functions can also be regarded as software modules for implementing the method and the structures within the hardware component.

[0126] The specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the above specific implementation manners, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Without conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. An enterprise-level distributed file service unified management method, characterized in that The following steps are involved: Step S1: Configure the gateway service and the corresponding distributed file system metadata, and the control center service builds a management n-ary tree based on the metadata; Step S2: The gateway service establishes a health monitoring relationship with the distributed file system it manages, and registers the gateway service as a child node and the corresponding distributed file system as a leaf node. Step S3: The control center service obtains the child node information according to the management n-ary tree and distributes the metadata to the corresponding child nodes. The gateway service independently provides storage services to the outside world. Step S4: The control center service synchronously manages the n-ary tree to request the distribution center service, and requests the distribution center service to distribute the system-level user global file request to the gateway service that meets the requirements according to the management n-ary tree information; The step S2 comprises: Step S2.1: The control center service registers the gateway service and adds the gateway service number information under the management n-ary tree; Step S2.2: Generate an n-ary tree with horizontally sorted child nodes according to the breadth-first traversal algorithm; Step S2.3: The gateway service monitors the health of the distributed file system within its jurisdiction through the metadata information it carries; Step S2.4: The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management n-ary tree; Step S2.5: When the distributed file system type is FastDFS, the retention strategy is adopted. When the distributed file system type is MinIO, the file number is based on the bucket and the manual filling strategy is adopted to synchronize the file number with FastDFS. Step S2.6: Build master-slave node automatic synchronization and disaster recovery tasks based on the types of master and slave nodes; Step S2.7: Based on the health monitoring strategy, the gateway service promptly alerts the downtime service and establishes a master-slave switching mechanism; The step S3 comprises: Step S3.1: The control center service distributes the newly created and modified gateway service metadata based on the management n-ary tree; Step S3.2: The gateway service completes the user access authority and capacity determination based on the user information distributed by the control center service; Step S3.3: The gateway service monitors the disk status of the server where the distributed system is located based on the distributed system connection information.

2. The unified management method for enterprise-level distributed file services according to claim 1, wherein: The step S1 comprises: Step S1.1: Configure the gateway service metadata, including the service unique code, management interface path, storage capacity, deployment area, access type, storage type, access user, and user permissions. Step S1.2: Configure the distributed file system metadata including: connection information, storage capacity, system type, and deployment information; Step S1.3: The control center service number itself is used as the root node, and subsequent child nodes and leaf nodes are registered in the control center service.

3. The unified management method for enterprise-level distributed file services according to claim 1, characterized in that: The step S4 comprises: Step S4.1: When the control center service synchronizes the management n-tree with the request distribution center service through the shared cache, the request distribution center service periodically synchronizes the management n-tree to the backup database; when the request distribution center service cannot obtain the management n-tree in the shared cache, it directly calls the control center service interface to obtain the latest management n-tree Step S4.2: When the latest management n-ary tree can be obtained, synchronize the current management n-ary tree to the backup database and update the backup time. If the latest management n-ary tree cannot be obtained, request the distribution center service to obtain the scheduled backup management n-ary tree from the database; Step S4.3: When a system-level user requests a file in high-availability mode, the distribution center service is requested to retrieve and manage the n-ary tree, obtain and request a gateway service that is redirected to the nearest area.

4. An enterprise-level distributed file service unified management system, characterized in that, Includes the following modules: Module M1: Configures the gateway service and the corresponding distributed file system metadata. The control center service builds a management n-ary tree based on the metadata. Module M2: The gateway service establishes health monitoring with the distributed file system it manages, and registers the gateway service as a child node, and the corresponding distributed file system as a leaf node; Module M3: The control center service obtains child node information based on the management n-ary tree and distributes metadata to the corresponding child nodes. The gateway service independently provides storage services to the outside world. Module M4: The control center service synchronously manages the n-ary tree to the request distribution center service, and requests the distribution center service to distribute the system-level user global file request to the gateway service that meets the requirements based on the management n-ary tree information; The module M2 includes: Module M2.1: The control center service registers the gateway service and adds the gateway service number information under the management n-tree; Module M2.2: Generate an n-ary tree with horizontally sorted child nodes based on the breadth-first traversal algorithm; Module M2.3: The gateway service monitors the health of the distributed file system within its jurisdiction through its own metadata information; Module M2.4: The gateway service carries the information of the distributed file system under its jurisdiction and registers the leaf node information in the management n-ary tree; Module M2.5: When the distributed file system type is FastDFS, a retention strategy is adopted. When the distributed file system type is MinIO, file numbering is based on the bucket and a manual padding strategy is adopted to synchronize file numbering with FastDFS. Module M2.6: Build automatic synchronization and disaster recovery tasks for master and slave nodes based on the types of master and slave nodes; Module M2.7: Based on the health monitoring strategy, the gateway service promptly alerts the downtime service and establishes a master-slave switching mechanism; The module M3 includes: Module M3.1: The control center service distributes the metadata of newly created and modified gateway services based on the management n-ary tree; Module M3.2: The gateway service completes the authority and capacity determination for user access based on the user information distributed by the control center service; Module M3.3: The gateway service monitors the disk status of the server where the distributed system is located based on the distributed system connection information.

5. The enterprise-level distributed file service unified management system according to claim 4, characterized in that: The module M1 includes: Module M1.1: Configure the gateway service metadata, including: service unique code, management interface path, storage capacity, deployment area, access type, storage type, access user, and user permissions; Module M1.2: Configure distributed file system metadata including connection information, storage capacity, system type, and deployment information; Module M1.3: Using the service ID of the control center itself as the root node, subsequent child nodes and leaf nodes are registered in the control center service.

6. The enterprise-level distributed file service unified management system according to claim 4, characterized in that: The said module M4 includes: Module M4.1: When the control center service synchronizes the management of the n-ary tree with the request distribution center service through the shared cache, the request distribution center service periodically synchronizes the management of the n-ary tree to the backup database; when the request distribution center service cannot obtain the management of the n-ary tree from the shared cache, it directly calls the control center service interface to obtain the latest management of the n-ary tree Module M4.2: When the latest management of the n-ary tree can be obtained, synchronize the current management of the n-ary tree to the backup database and update the backup time; when the latest management of the n-ary tree cannot be obtained, the request distribution center service obtains the periodically backed-up management of the n-ary tree from the database; Module M4.3: When the system-level user requests a file in the high-availability mode, the request distribution center service retrieves the management of the n-ary tree, obtains and requests redirection to the gateway service in the nearest area.

Images