CN117201284A - Gateway management method, system, device and medium - Google Patents
Gateway management method, system, device and medium Download PDFInfo
- Publication number
- CN117201284A CN117201284A CN202311316793.3A CN202311316793A CN117201284A CN 117201284 A CN117201284 A CN 117201284A CN 202311316793 A CN202311316793 A CN 202311316793A CN 117201284 A CN117201284 A CN 117201284A
- Authority
- CN
- China
- Prior art keywords
- gateway
- file system
- main
- primary
- standby
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 41
- 238000000034 method Methods 0.000 claims description 23
- 239000007787 solid Substances 0.000 claims description 21
- 230000003993 interaction Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000007246 mechanism Effects 0.000 abstract description 12
- 238000012545 processing Methods 0.000 abstract description 8
- 238000013461 design Methods 0.000 abstract description 4
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000010076 replication Effects 0.000 abstract description 4
- 230000001276 controlling effect Effects 0.000 description 18
- 230000006870 function Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000000875 corresponding effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Abstract
The application discloses a gateway management method, a gateway management system, a gateway management device and a gateway management medium, and relates to the field of data processing. Acquiring the state of a main gateway of a file system on current mounting block equipment, and determining the fault condition of the main gateway according to the state of the main gateway; controlling the main gateway to unload the file system when the main gateway is determined to be faulty; and after the main gateway uninstalls the file system, controlling the standby gateway to mount the file system. Therefore, the application determines the fault condition by acquiring the state of the main gateway, then uninstalls the main gateway with fault, and mounts the standby gateway to replace the main gateway; in this way, even if the primary gateway fails, the client can still communicate with the file system of the block device, thereby improving the availability of the file storage system. The application can also reduce the introduction of complex data synchronization and consistency mechanisms, reduce the complexity and the cost of the system, and avoid the data synchronization and consistency mechanisms brought by the data replication and the distributed file system, thereby simplifying the design and maintenance of the system.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a gateway management method, system, device, and medium.
Background
In a traditional file storage system, data interaction is usually carried out between a client and block equipment by means of a single storage gateway, and when the storage gateway fails, communication between the client and the block equipment cannot be carried out, so that the reliability of the file storage system is low. To solve these problems, some solutions in the prior art are: availability and fault tolerance of file storage systems are improved by copying data or employing a distributed file system. However, these schemes often introduce complex data synchronization and consistency mechanisms, adding complexity and overhead to the system.
Therefore, there is a need for a new block device based file storage system and method to improve the availability and data consistency of the file storage system while minimizing the introduction of complex data synchronization and consistency mechanisms to reduce the complexity and overhead of the system.
Disclosure of Invention
The application aims to provide a gateway management method, a system, a device and a medium, wherein the fault condition of a main gateway is determined by acquiring the state of the main gateway, then the main gateway with fault is unloaded, and finally a standby gateway is mounted to replace the main gateway; in this way, even if the primary gateway fails, the client can still communicate with the block device, thereby improving the availability of the file storage system. The application can also reduce the introduction of complex data synchronization and consistency mechanisms, reduce the complexity and the cost of the system, and avoid the data synchronization and consistency mechanisms brought by the data replication and the distributed file system, thereby simplifying the design and maintenance of the system.
In order to solve the technical problem, the present application provides a gateway management method, which is applied to a processor in a file storage system, the file storage system further includes a client, a block device, a primary gateway and a standby gateway, the client performs data interaction with a file system on the block device through the primary gateway or the standby gateway, and the method includes:
acquiring the state of a main gateway of a file system currently mounted on the block equipment, and determining the fault condition of the main gateway according to the state of the main gateway;
when the main gateway is determined to be faulty, controlling the main gateway to unload the file system;
and after the main gateway finishes unloading the file system, controlling the standby gateway to mount the file system.
In one embodiment, obtaining a state of a primary gateway currently mounting a file system on the block device, and determining a fault condition of the primary gateway according to the state of the primary gateway includes:
monitoring whether the virtual IP address on the main gateway drifts or not through the standby gateway;
and if drift occurs, determining that the main gateway fails.
In one embodiment, upon determining that the primary gateway fails, controlling the primary gateway to offload the file system includes:
when the main gateway is determined to be faulty, an unloading instruction is sent to the main gateway so as to trigger the main gateway to unload the file system;
after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system, including:
and after the main gateway finishes unloading the file system, sending a mounting instruction to the standby gateway so as to trigger the standby gateway to mount the file system.
In one embodiment, after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system further comprises:
and updating the primary and secondary gateway role table to update the standby gateway of the primary and secondary gateway role table after the file system is mounted as a primary gateway.
In one embodiment, the block device comprises a solid state disk device and a mechanical hard disk device; the process of writing data to the file system of the block device by the client comprises the following steps:
the client writes data into the solid state disk device through the main gateway or the standby gateway;
and after the solid state disk equipment is fully written, refreshing the data in the solid state disk equipment into the solid state disk equipment.
In one embodiment, further comprising:
acquiring the performance requirement of the client and the configuration parameters of a main gateway currently mounting the file system;
and if the configuration parameters cannot meet the performance requirements, performing thermal expansion on the main gateway.
In one embodiment, if the primary gateway is thermally expanded, after determining that the primary gateway fails, controlling the primary gateway to offload the file system further includes:
performing thermal shrinkage on the main gateway;
after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system, and further comprising:
and carrying out thermal expansion on the standby gateway.
In order to solve the technical problem, the present application also provides a gateway management system, which is applied to a processor in a file storage system, the file storage system further comprises a client, a block device, a main gateway and a standby gateway, the client performs data interaction with the block device through the main gateway or the standby gateway, and the system comprises:
the acquisition unit is used for acquiring the state of a main gateway of the file system currently mounted on the block equipment and determining the fault condition of the main gateway according to the state of the main gateway;
an unloading unit, when determining that the main gateway fails, controlling the main gateway to unload the file system;
and the mounting unit is used for controlling the standby gateway to mount the file system after the main gateway finishes unloading the file system.
In order to solve the technical problem, the present application further provides a gateway management device, including:
a memory for storing a computer program;
a processor for implementing the steps of the gateway management method as described above when storing a computer program.
To solve the above technical problem, the present application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the gateway management method as described above.
The application provides a gateway management method, a gateway management system, a gateway management device and a gateway management medium, and relates to the field of data processing. Acquiring the state of a main gateway currently mounted on a client, and determining the fault condition of the main gateway according to the state of the main gateway; unloading the primary gateway from the client when determining that the primary gateway is faulty; and after the main gateway is unloaded from the client, the standby gateway is mounted to the client. Therefore, the application determines the fault condition by acquiring the state of the main gateway, then uninstalls the main gateway with fault, and finally installs the standby gateway to replace the main gateway; in this way, even if the primary gateway fails, the client can still communicate with the block device, thereby improving the availability of the file storage system. The application can also reduce the introduction of complex data synchronization and consistency mechanisms, reduce the complexity and the cost of the system, and avoid the data synchronization and consistency mechanisms brought by the data replication and the distributed file system, thereby simplifying the design and maintenance of the system.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required in the prior art and the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a gateway management method provided by the present application;
FIG. 2 is a block diagram of a file storage system according to the present application;
fig. 3 is a specific logic schematic diagram of a gateway management method according to the present application;
fig. 4 is a schematic diagram of a gateway management system according to the present application;
fig. 5 is a schematic diagram of a gateway management apparatus according to the present application.
Detailed Description
The core of the application is to provide a gateway management method, system, device and medium, which can determine the fault condition of the main gateway by acquiring the state of the main gateway, then unload the main gateway which is faulty, and finally mount the standby gateway to replace the main gateway; in this way, even if the primary gateway fails, the client can still communicate with the block device, thereby improving the availability of the file storage system. The application can also reduce the introduction of complex data synchronization and consistency mechanisms, reduce the complexity and the cost of the system, and avoid the data synchronization and consistency mechanisms brought by the data replication and the distributed file system, thereby simplifying the design and maintenance of the system.
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The application provides a gateway management method, as shown in figure 1, applied to a processor in a file storage system, wherein the file storage system (shown in figure 2) also comprises a client, a block device, a main gateway and a standby gateway, and the client performs data interaction with the file system of the block device through the main gateway or the standby gateway, and the method comprises the following steps:
s1: acquiring the state of a main gateway of a file system on current mounting block equipment, and determining the fault condition of the main gateway according to the state of the main gateway;
the main purpose of this step is to obtain the state of the primary gateway of the file system currently mounted on the block device, and determine whether the primary gateway has failed according to the state of the primary gateway. The primary gateway is a key component in the file storage system responsible for data interactions between clients and block devices.
Specifically, the status of the primary gateway may be obtained by the processor sending a query request to an interface in communication with the primary gateway. This query request will contain identification information of the primary gateway so that the system can accurately identify and communicate with the primary gateway. Waiting for a response from the primary gateway. The master gateway returns its own status information to the processor via a response. This status information may include the operational status, connection status, operational status, etc. of the primary gateway. Once the processor receives the primary gateway's response, it parses the response data and determines the current state of the primary gateway. For example, if the response indicates that the primary gateway is not connected or in a failed state, the processor will determine that the primary gateway has failed. Based on the determined primary gateway state, the processor may take corresponding action. For example, if the primary gateway is determined to be in a failure state, the processor may trigger subsequent steps S2 and S3 to offload the file system and mount the standby gateway.
By executing the steps, the availability of the file storage system can be improved, the situation that the backup gateway can be switched to in time under the condition of the failure of the main gateway is ensured, and the normal operation of communication between the client and the block equipment is ensured.
S2: when the main gateway fault is determined, controlling the main gateway to unload a file system;
the purpose of this step is to control the primary gateway to offload the file system after determining that the primary gateway has failed.
In a file storage system, the primary gateway is responsible for managing and controlling data interactions between clients and block devices. When the primary gateway fails, the client cannot communicate with the block device, resulting in reduced reliability of the file storage system. Therefore, in the event of a failure of the primary gateway, some measures need to be taken to ensure proper operation of the system.
Wherein file system offloading refers to stopping access and use of the file system and removing the file system from the primary gateway. Thus, the main gateway which is in fault can be ensured not to continuously influence the normal operation of the system.
In conclusion, the usability of the file storage system can be effectively improved by controlling the unloading of the main gateway.
S3: and after the main gateway uninstalls the file system, controlling the standby gateway to mount the file system.
The step is to control the spare gateway to mount the file system after the main gateway successfully uninstalls the file system. In the conventional file storage system, when the primary gateway fails, the client cannot communicate with the block device, resulting in lower reliability of the file storage system. Specifically, if the primary gateway in the above step successfully uninstalls the file system, the standby gateway can be controlled to mount the file system through the step. In this way, even if the primary gateway fails, the client is still able to communicate with the block device through the backup gateway. By quickly mounting the file system to the standby gateway after the primary gateway fails, the availability and data consistency of the file storage system can be greatly improved.
This approach has the advantage over conventional solutions of reducing complex data synchronization and consistency mechanisms, thereby reducing the complexity and overhead of the system. At the same time, by using the standby gateway to provide continuous data services, the reliability of the file storage system may be increased.
In one embodiment, obtaining a state of a primary gateway of a file system on a current mounting block device, and determining a failure condition of the primary gateway according to the state of the primary gateway includes:
monitoring whether the virtual IP address on the main gateway drifts or not through the standby gateway;
if drift occurs, the primary gateway is determined to be faulty.
In this embodiment, an implementation manner is described, which is used to obtain the state of the primary gateway of the file system on the current mounting block device, and determine the fault condition of the primary gateway according to the state of the primary gateway. Specifically, in a file storage system, the same virtual IP address is typically assigned to the primary gateway and the backup gateway. The method monitors whether the virtual IP address on the main gateway drifts from the main gateway through the standby gateway to judge the state of the main gateway. Drift refers to the process of transferring a virtual IP address from one node to another (e.g., from a primary gateway to a backup gateway). When the standby gateway detects that the virtual IP address on the main gateway drifts, the fault of the main gateway can be deduced. The occurrence of drift means that the primary gateway has not continued to function properly, while the backup gateway will take over the function of the primary gateway. Thus, by monitoring the drift of the virtual IP address, the failure condition of the primary gateway can be determined.
The aim of this embodiment is to ensure a reliable communication channel between the block devices and clients in the file storage system at all times. The availability and data consistency of the file storage system can be improved by detecting the failure of the main gateway in time and mounting the spare gateway on the file system. Meanwhile, the method avoids the introduction of complex data synchronization and consistency mechanisms, and reduces the complexity and the cost of the system.
In one embodiment, upon determining a primary gateway failure, controlling the primary gateway to offload a file system includes:
when the main gateway fault is determined, an unloading instruction is sent to the main gateway so as to trigger the main gateway to unload a file system;
after the primary gateway uninstalls the file system, controlling the standby gateway to mount the file system, wherein the method comprises the following steps:
and after the main gateway uninstalls the file system, sending a mounting instruction to the standby gateway so as to trigger the standby gateway to mount the file system.
In this embodiment, when the system detects that the primary gateway fails, an offload command is sent to the primary gateway. The purpose of this instruction is to trigger the primary gateway to offload the file system. By offloading the file system, it can be ensured that the primary gateway no longer handles file storage requests from clients.
Once the primary gateway successfully unloads the file system, a mount command is sent to the standby gateway. The purpose of this instruction is to trigger the standby gateway to mount the file system. By mounting the file system, the standby gateway will be able to receive and process file storage requests from clients.
In this way, the file storage system may implement failover, and the standby gateway may take over the functions of the primary gateway when the primary gateway fails. By controlling the primary gateway to offload file systems and to mount file systems on the backup gateway, continuous availability of the file storage system in the event of a failure can be ensured and data consistency maintained.
In one embodiment, after the primary gateway uninstalls the file system, the backup gateway is controlled to mount the file system, the method further comprises:
and updating the primary and secondary gateway role table to update the standby gateway after the file system is mounted in the primary and secondary gateway role table as the primary gateway.
Further, once the backup gateway successfully mounts the file system, the method updates the role table of the primary and backup gateways, and updates the role of the backup gateway to the primary gateway. In this way, the primary and backup gateway role table will reflect that the current backup gateway has become the new primary gateway and is responsible for handling data interactions between clients and block devices, such as removing the original primary gateway from the table. This is done to ensure that the system correctly recognizes the new primary gateway role after the standby gateway is mounted to the client, and updates the management and scheduling of the primary and standby gateways in the system.
Through the steps of the embodiment, the system can be effectively switched to the standby gateway after the main gateway fails, and the availability and data consistency of the file storage system are maintained. Updating the primary and backup gateway role table also ensures that the system properly tracks and records role changes between the primary and backup gateways in order to properly assign tasks and functions.
In one embodiment, the block device includes a solid state disk device and a mechanical hard disk device; the process of writing data to the file system of the block device by the client comprises the following steps:
the client writes data into the solid state disk device through the main gateway or the standby gateway;
and after the solid state disk device is fully written, refreshing the data in the solid state disk device into the solid state disk device.
Specifically, when the block device includes a solid state hard disk device and a mechanical hard disk device. The client writes data to the file system of the block device. This process can be divided into two steps. The client chooses to write data to the file system of the block device through either the primary gateway or the backup gateway. When the client selects to write data, the data can be written into the solid state disk device. The solid state disk device is a high-performance storage medium and has a rapid data reading and writing speed. And refreshing the data in the solid state disk device to the mechanical hard disk device when the solid state disk device is full. A mechanical hard disk device is a high-capacity inexpensive storage medium that can provide more storage space.
Thus, by the present embodiment, the performance and capacity of the shared file system can be improved at the same time. The solid state disk device is used as the log device, so that the performance of writing logs can be improved, and the mechanical hard disk device is used as the data device, so that the cost of the system can be reduced. This approach balances storage costs and performance requirements while improving the performance of the shared file system.
In one embodiment, further comprising:
acquiring the performance requirement of a client and the configuration parameters of a main gateway of a current file system;
and if the configuration parameters can not meet the performance requirements, performing thermal expansion on the main gateway.
Further, this embodiment also describes the step of obtaining the performance requirement of the client and the configuration parameters of the primary gateway of the current mount file system. If the configuration parameters cannot meet the performance requirements, the main gateway can be subjected to thermal expansion.
Where the performance requirements of the client are obtained, these performance requirements may be various metrics, such as processing power, storage capacity, throughput, etc. When the configuration parameters of the main gateway of the current mounted file system are obtained, the configuration parameters can comprise related information such as hardware specification, network bandwidth, processing capacity and the like of the main gateway.
Once the performance requirements of the client and the configuration parameters of the primary gateway are obtained, the two are compared to determine if the configuration parameters can meet the performance requirements. And if the configuration parameters are insufficient to meet the performance requirements, performing thermal expansion on the main gateway. Thermal expansion refers to expanding the primary gateway without interrupting service. In this case, the primary gateway may add more hardware resources, such as more processors, storage devices, or network bandwidth, to meet the performance requirements of the client. This ensures that the file storage system provides the required performance and maintains the reliability and availability of the system.
In summary, the embodiment can dynamically adjust according to the performance requirement of the client and the configuration parameters of the primary gateway, so as to provide a file storage system meeting the performance requirement, and thermally expand the primary gateway when required.
In one embodiment, if the primary gateway is thermally expanded, when determining that the primary gateway fails, controlling the primary gateway to offload the file system further includes:
performing thermal shrinkage on the main gateway;
after the primary gateway uninstalls the file system, the backup gateway is controlled to mount the file system, and the method further comprises the following steps:
and performing thermal expansion on the standby gateway.
Further, the primary gateway uninstalls the file system after determining the primary gateway failure. This means that the primary gateway cannot continue to provide data interaction functionality and needs the standby gateway to take over its tasks. After the primary gateway uninstalls the file system, the backup gateway mounts the file system. This means that the standby gateway will replace the primary gateway and interact data with the client. The standby gateway will take over all the functions and responsibilities of the primary gateway, ensuring that the client is able to communicate with the file system of the block device.
If the main gateway performs thermal expansion, after the main gateway uninstalls the file system, the main gateway is not needed, so that the resources and processing capacity of the main gateway can be reduced, and the complexity and the cost of the system can be reduced as much as possible. Thus shrinking the volume of the primary gateway. After the spare gateway mounts the file system, since the primary gateway is capacity-expanded before, the initial configuration of the spare gateway should not meet the performance requirement either, so the performance requirement of the client needs to be met by increasing the resources and processing capacity of the spare gateway. That is, the spare gateway is thermally expanded, so that the processing capacity of the spare gateway can be improved, and the performance and usability of the system are improved.
In summary, the embodiment realizes seamless replacement and thermal expansion of the main gateway through the standby gateway, thereby improving availability and data consistency of the system. Meanwhile, unnecessary resource occupation can be reduced through thermal shrinkage, and complexity and cost of a system are reduced.
One embodiment of the present application is described as follows:
as shown in fig. 2, the high availability shared file storage system based on block devices is logically divided into three layers, client, gateway, block devices, respectively. The client uses a mount command to mount a shared file system (NFS (Network File System, network file system) or SMB (Server Message Block ) file system) through the vip of the gateway, and performs read-write operation on the shared file system through a POSIX API; the vip of the gateway can drift between the main gateway and the standby gateway, can provide high availability characteristic, and provides NFS or SMB shared file system service by using NFS-Ganesha or Samba software for client side mounting; the block devices may be provided by distributed storage, centralized storage, or local hard disk, with the gateway mounting the block devices for carrying data in a shared file system, the block devices being formatted as an XFS file system.
The gateway is logically divided into three layers, wherein the uppermost layer is a network layer and is responsible for providing a mounting point for a client to mount, the client uses vip to mount a shared file system, and vip is provided by keepalive software; the middle layer is a protocol conversion layer, and NFS and SMB sharing file system protocols can be converted into VFS (Virtual File System ) by running NFS-Ganesha and Samba software; the lowest layer is the data persistence layer, responsible for converting the VFS and XFS file systems.
Although the block device can be mounted on a plurality of gateways, since the XFS file system on the block device is not a cluster file system, writing files into the file system of one block device by a plurality of gateways at the same time can cause that the data of the plurality of gateways cannot be synchronized, which can cause damage to the file system and further cause data loss. Therefore, the block device is simultaneously mounted on the main gateway and the standby gateway, but only the main gateway mounts the XFS file system of the block device, so that the file system on the block device can be read and written by only one gateway at the same moment, and the file system damage caused by writing files into the file system of one block device at the same time is prevented.
As shown in fig. 3, the vip of the gateway is provided by keepaled software, and the vip can be automatically switched to the standby gateway when the main gateway fails, so that the client does not feel the vip. In order to ensure that only one gateway still mounts the XFS file system on the block device during vip handover, i.e. primary and backup gateway handover, the following logic needs to be executed:
when the main gateway fails, the vip drifts, at the moment, a notify_master script of the keydrive software on the standby gateway is triggered to execute, and the notify_master script informs a processor to update the roles of the main gateway and the standby gateway; when the processor receives the request of converting the standby gateway into the main gateway, in order to ensure that only one gateway mounts the XFS file system on the block device, the processor sends an unloading instruction to the main gateway, informs the main gateway to unload the XFS file system, returns the result to the processor after the main gateway successfully unloads the XFS file system, at this time, the processor sends a mounting instruction to the standby gateway again, informs the standby gateway to mount the XFS file system, returns the result to the processor after the mounting is successful, maintains a part of the role table of the main and standby gateways in the processor, and finishes the main and standby switching flow after the role table is updated. If the master gateway fails to unload the XFS file system, the master-slave switching process fails, and the system cannot judge the states of the master gateway and the XFS file system, and prompt information needs to be output at the moment so as to facilitate manual intervention.
In order to solve the above technical problem, the present application further provides a gateway management system, as shown in fig. 4, applied to a processor in a file storage system, where the file storage system further includes a client, a block device, a main gateway, and a standby gateway, and the client performs data interaction with the block device through the main gateway or the standby gateway, where the system includes:
an obtaining unit 41, configured to obtain a state of a primary gateway of a file system on a current mounting block device, and determine a failure condition of the primary gateway according to the state of the primary gateway;
an uninstalling unit 42 for controlling the main gateway to uninstall the file system when the main gateway is determined to be failed;
and the mounting unit 43 is configured to control the standby gateway to mount the file system after the primary gateway finishes unloading the file system.
For the description of the gateway management system, please refer to the above embodiment, and the description of the present application is omitted herein.
In order to solve the above technical problem, the present application further provides a gateway management apparatus, as shown in fig. 5, including:
a memory 51 for storing a computer program;
the processor 52 is configured to implement the steps of the gateway management method as described above when storing the computer program. For the description of the gateway management apparatus, please refer to the above embodiment, and the description of the present application is omitted herein.
In order to solve the above technical problem, the present application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the gateway management method as described above. For the description of the computer-readable storage medium, refer to the above embodiments, and the disclosure is not repeated here.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A gateway management method, characterized by being applied to a processor in a file storage system, the file storage system further comprising a client, a block device, a primary gateway and a standby gateway, wherein the client performs data interaction with a file system on the block device through the primary gateway or the standby gateway, the method comprising:
acquiring the state of a main gateway of a file system currently mounted on the block equipment, and determining the fault condition of the main gateway according to the state of the main gateway;
when the main gateway is determined to be faulty, controlling the main gateway to unload the file system;
and after the main gateway finishes unloading the file system, controlling the standby gateway to mount the file system.
2. The gateway management method according to claim 1, wherein obtaining a state of a primary gateway currently mounting a file system on the block device, and determining a failure condition of the primary gateway according to the state of the primary gateway, comprises:
monitoring whether the virtual IP address on the main gateway drifts or not through the standby gateway;
and if drift occurs, determining that the main gateway fails.
3. The gateway management method of claim 1, wherein upon determining that the primary gateway failed, controlling the primary gateway to offload the file system comprises:
when the main gateway is determined to be faulty, an unloading instruction is sent to the main gateway so as to trigger the main gateway to unload the file system;
after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system, including:
and after the main gateway finishes unloading the file system, sending a mounting instruction to the standby gateway so as to trigger the standby gateway to mount the file system.
4. The gateway management method according to claim 1, wherein after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system, further comprising:
and updating the primary and secondary gateway role table to update the standby gateway of the primary and secondary gateway role table after the file system is mounted as a primary gateway.
5. The gateway management method according to claim 1, wherein the block device includes a solid state disk device and a mechanical hard disk device; the process of writing data to the file system of the block device by the client comprises the following steps:
the client writes data into the solid state disk device through the main gateway or the standby gateway;
and after the solid state disk equipment is fully written, refreshing the data in the solid state disk equipment into the solid state disk equipment.
6. The gateway management method according to any one of claims 1 to 5, further comprising:
acquiring the performance requirement of the client and the configuration parameters of a main gateway currently mounting the file system;
and if the configuration parameters cannot meet the performance requirements, performing thermal expansion on the main gateway.
7. The gateway management method according to claim 6, wherein if the primary gateway is thermally expanded, after controlling the primary gateway to offload the file system when determining that the primary gateway fails, further comprising:
performing thermal shrinkage on the main gateway;
after the primary gateway finishes unloading the file system, controlling the standby gateway to mount the file system, and further comprising:
and carrying out thermal expansion on the standby gateway.
8. A gateway management system, characterized by a processor applied in a file storage system, the file storage system further comprising a client, a block device, a primary gateway and a backup gateway, the client performing data interaction with the block device through the primary gateway or the backup gateway, the system comprising:
the acquisition unit is used for acquiring the state of a main gateway of the file system currently mounted on the block equipment and determining the fault condition of the main gateway according to the state of the main gateway;
an unloading unit, when determining that the main gateway fails, controlling the main gateway to unload the file system;
and the mounting unit is used for controlling the standby gateway to mount the file system after the main gateway finishes unloading the file system.
9. A gateway management apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the gateway management method according to any of claims 1-7 when storing a computer program.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the gateway management method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311316793.3A CN117201284A (en) | 2023-10-12 | 2023-10-12 | Gateway management method, system, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311316793.3A CN117201284A (en) | 2023-10-12 | 2023-10-12 | Gateway management method, system, device and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117201284A true CN117201284A (en) | 2023-12-08 |
Family
ID=88996231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311316793.3A Pending CN117201284A (en) | 2023-10-12 | 2023-10-12 | Gateway management method, system, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117201284A (en) |
-
2023
- 2023-10-12 CN CN202311316793.3A patent/CN117201284A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11360854B2 (en) | Storage cluster configuration change method, storage cluster, and computer system | |
| US11320991B2 (en) | Identifying sub-health object storage devices in a data storage system | |
| US7340637B2 (en) | Server duplexing method and duplexed server system | |
| US7058731B2 (en) | Failover and data migration using data replication | |
| US6134673A (en) | Method for clustering software applications | |
| WO2016070375A1 (en) | Distributed storage replication system and method | |
| CN109446169B (en) | Double-control disk array shared file system | |
| WO2022037171A1 (en) | Data request method, device and medium | |
| CN110597910A (en) | Remote data synchronization method, device and system | |
| WO2017215502A1 (en) | Cloud-desktop disaster recovery method, client, server, cloud-desktop disaster recovery system, and storage medium | |
| CN106850255B (en) | Method for implementing multi-machine backup | |
| CN111327467A (en) | Server system, disaster recovery backup method thereof and related equipment | |
| CN101079896A (en) | A multi-availability mechanism coexistence framework of concurrent storage system | |
| WO2018010501A1 (en) | Global transaction identifier (gtid) synchronization method, apparatus and system, and storage medium | |
| WO2014177085A1 (en) | Distributed multicopy data storage method and device | |
| CN111240901B (en) | Node dynamic expansion system, method and equipment of distributed block storage system | |
| CN111935244A (en) | Service request processing system and super-integration all-in-one machine | |
| CN115292283A (en) | Master-slave high-availability switching method based on disk cabinet | |
| US20080301777A1 (en) | Hot standby server system | |
| CN111858190A (en) | Method and system for improving cluster availability | |
| CN113190619B (en) | Data read-write method, system, equipment and medium for distributed KV database | |
| CN111400285B (en) | mySQL data fragment processing method, device, computer equipment and readable storage medium | |
| CN107357800A (en) | A kind of database High Availabitity zero loses solution method | |
| JP4512386B2 (en) | Backup system and method | |
| CN117201284A (en) | Gateway management method, system, device and medium |
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 |