CN110247937B - Method for managing and accessing shared file of elastic storage system and related equipment - Google Patents

Method for managing and accessing shared file of elastic storage system and related equipment Download PDF

Info

Publication number
CN110247937B
CN110247937B CN201810188002.6A CN201810188002A CN110247937B CN 110247937 B CN110247937 B CN 110247937B CN 201810188002 A CN201810188002 A CN 201810188002A CN 110247937 B CN110247937 B CN 110247937B
Authority
CN
China
Prior art keywords
node
nfs
publishing
shared file
configuration data
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.)
Active
Application number
CN201810188002.6A
Other languages
Chinese (zh)
Other versions
CN110247937A (en
Inventor
王东旭
孟令坤
张松
许声红
张德龙
张卓豫
陈盼
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Suzhou Software Technology Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Suzhou Software Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Suzhou Software Technology Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN201810188002.6A priority Critical patent/CN110247937B/en
Publication of CN110247937A publication Critical patent/CN110247937A/en
Application granted granted Critical
Publication of CN110247937B publication Critical patent/CN110247937B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • 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
    • 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
    • G06F16/183—Provision of network file services by network file servers, e.g. by using NFS, CIFS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (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 relates to the field of storage, in particular to a method for managing and accessing a shared file of an elastic storage system and related equipment. According to the scheme provided by the embodiment of the invention, when the shared file instance is created, a unique publishing identifier is distributed to the shared file instance, the publishing state of each NFS node in the NFS service cluster is updated by using the publishing identifier, the consistency of the publishing state of each NFS node is ensured, the publishing configuration data corresponding to the shared file instance is loaded to each NFS node, and the consistency of the publishing configuration data in each NFS node is ensured. The client can realize service access through any NFS node in the NFS service cluster, high availability of the NFS service cluster is realized, and service access continuity is ensured.

Description

Method for managing and accessing shared file of elastic storage system and related equipment
Technical Field
The invention relates to the field of storage, in particular to a method for managing and accessing a shared file of an elastic storage system and related equipment.
Background
The elastic storage system provides a user-defined shared file storage service for users. Fig. 1 is a schematic diagram of a management plane of the elastic storage system. The shared file is created by which shared driver node in the storage resource pool managed by the shared driver node is decided by a scheduling algorithm controlling the scheduling node. The shared driving node manages a storage resource pool, and all shared files are created and maintained in the storage resource pool. A shared drive node manages one or more storage resource pools, each storage resource pool is used for storing one or more user-defined shared files, and for a shared file, the shared file is only stored in one storage resource pool.
FIG. 2 is a schematic diagram of the general architecture of the data plane of the elastic storage system. In order to improve the service performance of the data plane, the shared files in the storage resource pool provide a shared file access service to the client through a Network File System (NFS) service cluster.
Currently, an NFS service cluster provides a shared file access service to a client in a master/standby mode. A pair of active service nodes and standby service nodes communicate according to a prescribed communication protocol, thereby maintaining a consistent distribution state. The release states of the main service node and the standby service node are kept consistent in real time, so that seamless switching between the main service node and the standby service node can be realized. The monitoring system is used for monitoring the main service node, when the main service node is monitored to have a fault, the service access address is switched to the standby service node, namely the standby service node is switched to the main service node, so that the service continuity of a user is ensured, and the single-point fault is avoided.
However, the current active/standby mode can only avoid the problem of single point of failure, and if the standby service node also fails, the shared file access service cannot be provided to the client, which may cause interruption of service access of the client.
Disclosure of Invention
The embodiment of the invention provides a method for managing and accessing a shared file of an elastic storage system and related equipment, which are used for ensuring the continuity of service access in the elastic storage system.
A method of elastic storage system shared file management, the method comprising:
creating a shared file instance in a storage resource pool, creating publishing configuration data for the shared file instance, wherein the publishing configuration data is configuration data used for publishing of the shared file instance, and distributing a publishing identifier for the shared file instance, and the publishing identifier has uniqueness;
and updating the publishing state of each NFS node in the Network File System (NFS) service cluster by using the publishing identification, and loading the publishing configuration data to each NFS node.
A method of shared file access for a flexible storage system, the method comprising:
determining whether an NFS node in a Network File System (NFS) service cluster providing shared file access fails;
and when the NFS node fails, switching the shared file access address to any other NFS node in the NFS service cluster that normally works, wherein the publishing state of each NFS node in the NFS service cluster is updated according to a unique publishing identifier allocated to each shared file instance, and each NFS node loads publishing configuration data corresponding to each shared file instance.
A shared driver node or a proxy node for a shared driver node, the node comprising:
the system comprises a creating module, a storing module and a sending module, wherein the creating module is used for creating a shared file instance in a storage resource pool, creating publishing configuration data for the shared file instance, the publishing configuration data is configuration data used for publishing of the shared file instance, and distributing a publishing identifier for the shared file instance, and the publishing identifier has uniqueness;
and the management module is used for updating the publishing state of each NFS node in the network file system NFS service cluster by using the publishing identification, and loading the publishing configuration data to each NFS node.
A shared driver node or a proxy node for a shared driver node, the node comprising:
the fault confirmation module is used for determining whether an NFS node which provides shared file access in the NFS service cluster of the network file system has a fault;
and a switching module, configured to switch the shared file access address to any other NFS node that normally operates in the NFS service cluster when the fault confirmation module confirms that the NFS node has a fault, where an issue state of each NFS node in the NFS service cluster is updated according to an issue identifier that is assigned to each shared file instance and has uniqueness, and each NFS node loads issue configuration data corresponding to each shared file instance.
A non-volatile computer storage medium storing an executable program for execution by a processor to perform the steps of implementing the above-described flexible storage system shared file management method, or to implement the above-described flexible storage system shared file access method.
A kind of elastic storage system shared file management apparatus, including memorizer, processor and computer program stored on memorizer, the said processor implements the step of the above-mentioned elastic storage system shared file management method when carrying out the said program, or implement the step of the above-mentioned elastic storage system shared file access method.
According to the scheme provided by the embodiment of the invention, when the shared file instance is created, a unique publishing identifier is distributed to the shared file instance, the publishing state of each NFS node in the NFS service cluster is updated by using the publishing identifier, the consistency of the publishing state of each NFS node is ensured, the publishing configuration data corresponding to the shared file instance is loaded to each NFS node, and the consistency of the publishing configuration data in each NFS node is ensured. The client can realize service access through any NFS node in the NFS service cluster, high availability of the NFS service cluster is realized, and service access continuity is ensured.
Drawings
FIG. 1 is a schematic diagram of a management plane of a flexible storage system provided in the prior art;
FIG. 2 is a schematic diagram of a data plane architecture of a flexible storage system provided in the prior art;
FIG. 3 is a flowchart illustrating steps of a method for managing shared files in an elastic storage system according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram illustrating an implementation of managing shared files of an elastic storage system by using a shared driver node according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a method for accessing a shared file in an elastic storage system according to a second embodiment of the present invention;
fig. 6 is a schematic diagram illustrating a shared driving node determining whether an NFS node fails according to a second embodiment of the present invention;
fig. 7 is a schematic structural diagram of a shared driver node or a proxy node of the shared driver node according to a third embodiment of the present invention;
fig. 8 is a schematic structural diagram of a shared driver node or a proxy node of the shared driver node according to a fourth embodiment of the present invention;
fig. 9 is a schematic structural diagram of a shared file management apparatus of an elastic storage system according to a seventh embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a high-availability scheme of a rear-end storage cluster of an elastic storage system. In the scheme of the invention, when the shared file instance is created in the storage resource pool, a unique publishing identifier is allocated to the shared file instance, each NFS node in the NFS service cluster keeps a consistent publishing state through the publishing identifier, and the publishing configuration data corresponding to the shared file instance can be loaded to each NFS node, so that each NFS node keeps consistent publishing configuration data. Therefore, when one NFS node fails, any other NFS node in the NFS service cluster can continue to provide service access service for the client, thereby avoiding interruption of service access and ensuring continuity of service access.
The embodiments of the present invention will be described in further detail with reference to the drawings attached hereto.
The first embodiment,
As shown in fig. 3, a flowchart of steps of a method for managing shared files in an elastic storage system according to an embodiment of the present invention is provided, where the method includes the following steps:
step 101, creating a shared file instance.
In this embodiment, the execution subject of the elastic storage system shared file management method may be a shared drive node, or may be a proxy node of the shared drive node. In this embodiment, an execution subject is taken as a shared driving node as an example for explanation.
In this step, the shared driver node creates a shared file instance in the storage resource pool.
Step 102, creating release configuration data and a release identification.
In this step, the sharing driver node creates NFS service cluster shared data, specifically, the sharing driver node creates publishing configuration data for the shared file instance created in step 101, and the publishing configuration data (export configuration data) may be understood as a configuration data for publishing of the shared file instance. And distributing a publishing identifier for the shared file instance, wherein the publishing identifier has uniqueness. Preferably, the release configuration data and the release identification may both be stored in the database system, and the database system stores and maintains the created shared data. In this embodiment, the following description will be given taking an example in which the distribution configuration data and the distribution identifier are both stored in the database system.
And step 103, updating the release state.
In this step, the shared driver node may update the publishing state of each NFS node in the NFS service cluster by using the publishing identifier allocated to the shared file instance in step 102, so that each NFS node may maintain a consistent publishing state.
And 104, loading and releasing configuration data.
In this step, the shared driver node may load the publishing configuration data created for the shared file instance in step 102 to each NFS node in the NFS service cluster, so that each NFS node may maintain consistent publishing configuration data. Therefore, the publishing state and the publishing configuration data of each NFS node in the NFS service cluster are kept consistent, the client can realize service access through any NFS node, and high availability of the NFS service cluster is really realized.
After the shared file is created, changes may be made to the shared file, including but not limited to, updates and deletions. Specifically, the shared file instance may be changed, the publishing configuration data corresponding to the shared file instance may be changed, the publishing state of each NFS node may be changed according to the changed publishing configuration data, and the changed publishing configuration data may be loaded to each NFS node or unloaded from each NFS node.
Specifically, after the shared file creation process is implemented, an update operation may be performed on the shared file. The following further describes a method for managing shared files in the elastic storage system after updating the shared files.
Step 201, updating the shared file instance.
After the shared file instance is created, the shared file instance may be updated.
Step 202, updating the release configuration data.
After the shared file instance is updated, the published configuration data needs to be updated accordingly.
And step 203, updating the release state.
In this step, the publishing state of each NFS node in the NFS service cluster may be updated according to the updated publishing configuration data. And ensuring that the publishing state of each NFS node in the NFS service cluster is matched with the updated publishing configuration data.
And step 204, loading the updated release configuration data.
In this step, the updated publishing configuration data may be loaded to each NFS node in the NFS service cluster, so as to ensure that each NFS node in the NFS service cluster loads the latest publishing configuration data.
Through steps 201-204, after the shared file instance is updated, each NFS node in the NFS service cluster can correspondingly maintain a consistent publishing state and publishing configuration data.
Specifically, after the shared file creation process is implemented, a deletion operation may be performed on the shared file. Of course, the deletion of the shared file may be performed after the update of the shared file. The following further describes a method for managing shared files in the elastic storage system after deleting the shared files.
Step 301, delete the shared file instance.
After the shared file instance is created, the shared file instance may be deleted.
And step 302, deleting the shared data.
In this step, after the shared file instance is deleted, the publishing configuration data and the publishing identifier corresponding to the shared file instance may be deleted.
Step 303, updating the release state.
In this step, the publishing state of each NFS node in the NFS service cluster may be updated according to the deleted publishing configuration data and the publishing identifier.
And step 304, unloading the distribution configuration data.
In this step, the deleted publishing configuration data may be offloaded from each NFS node in the NFS service cluster.
Through steps 301 to 304, after the shared file instance is deleted, each NFS node in the NFS service cluster can still correspond to each other, and a consistent release state and release configuration data are maintained.
It should be noted that the execution subject in the first embodiment of the present invention may be a shared driver node, or may be a proxy node of the shared driver node. Taking an agent node whose execution subject is a shared driver node as an example, an architectural diagram for implementing shared file management of the elastic storage system by using the shared driver node may be as shown in fig. 4. The shared driving node is driven by the NAS, and the agent node of the shared driving node and the shared driving node are interacted through a message queue protocol. And the proxy node of the shared driving node realizes three functions of managing a storage resource pool, managing the release state of the NFS service cluster during operation and managing shared data. The management of the shared data can be realized by the management of the publishing configuration data and the mapping relation between the shared file instance and the publishing identification.
Further, on the basis of implementing the management of the shared file of the elastic storage system according to the scheme provided by the first embodiment, a second embodiment of the present invention further provides a method for accessing the shared file of the elastic storage system.
Example II,
As shown in fig. 5, a schematic flowchart of a method for accessing a shared file in an elastic storage system according to a second embodiment of the present invention is shown, where the method includes the following steps:
step 401, determine whether the NFS node fails.
In this step, it may be determined whether an NFS node in the NFS service cluster that is providing shared file access has failed. Specifically, a status query request may be sent to an NFS node that is providing shared file access in an NFS service cluster, and whether the NFS node fails is determined according to status information fed back by the NFS node; or receiving state information reported by an NFS node providing shared file access in an NFS service cluster, and determining whether the NFS node fails according to the state information.
It should be noted that the execution subject in the second embodiment of the present invention may be a shared driver node, as shown in fig. 5, where the shared driver node monitors the states of all nodes in the NFS service cluster in real time and allocates a service access address to the nodes. Or may be a proxy node sharing the driver node. Taking an example in which the execution subject is a proxy node of a shared driver node, a schematic diagram of the shared driver node determining whether an NFS node that is providing shared file access in an NFS service cluster fails may be shown in fig. 6.
Step 402, switching service access addresses.
In this step, if it is determined in step 401 that the NFS node fails, the shared file access address may be switched to any other NFS node in the NFS service cluster that normally operates.
The publishing state of each NFS node in the NFS service cluster is updated according to the unique publishing identifier allocated to each shared file instance, and each NFS node loads publishing configuration data corresponding to each shared file instance.
Based on the same inventive concept, the embodiment of the present invention further provides a shared driving node or a proxy node of the shared driving node corresponding to the embodiment, and since the principle of solving the problem of the node is similar to the method provided in the first embodiment of the present invention, the implementation of the node may refer to the implementation of the method, and repeated details are omitted.
Example III,
As shown in fig. 7, a schematic structural diagram of a shared driver node or a proxy node of the shared driver node according to a third embodiment of the present invention is shown, where the node includes:
the creating module 11 is configured to create a shared file instance in a storage resource pool, create publishing configuration data for the shared file instance, where the publishing configuration data is configuration data for publishing of the shared file instance, and allocate a publishing identifier to the shared file instance, where the publishing identifier has uniqueness; the management module 12 is configured to update the publishing state of each NFS node in the network file system NFS service cluster by using the publishing identifier, and load the publishing configuration data to each NFS node.
The creating module 11 is specifically configured to store the created release configuration data and the assigned release identifier in a database system.
The node further includes a changing module 13 configured to change the shared file instance and change the distribution configuration data corresponding to the shared file instance;
the management module 12 is further configured to change the publishing state of each NFS node according to the changed publishing configuration data, and load the changed publishing configuration data to each NFS node or unload the changed publishing configuration data from each NFS node.
The changing module may include an updating sub-module 131, configured to update the shared file instance and update the publishing configuration data corresponding to the shared file instance;
the management module 12 is specifically configured to update the publishing state of each NFS node according to the updated publishing configuration data, and load the updated publishing configuration data to each NFS node.
The changing module may further include a deleting submodule 132, configured to delete the shared file instance, and delete the publishing configuration data and the publishing identifier corresponding to the shared file instance;
the management module 12 is specifically configured to update the publishing state of each NFS node according to the deleted publishing configuration data and the publishing identifier, and uninstall the deleted publishing configuration data from each NFS node.
Based on the same inventive concept, the embodiment of the present invention further provides a shared driving node or a proxy node of the shared driving node corresponding to the embodiment, and since the principle of solving the problem of the node is similar to the method provided in the first embodiment of the present invention, the implementation of the node may refer to the implementation of the method, and repeated details are omitted.
Example four,
As shown in fig. 8, a schematic structural diagram of a shared driver node or a proxy node of the shared driver node according to a fourth embodiment of the present invention is shown, where the node includes:
the failure confirmation module 21 is configured to determine whether an NFS node that is providing shared file access in the network file system NFS service cluster fails; the switching module 22 is configured to switch the shared file access address to any other NFS node in the NFS service cluster that normally works when the fault confirmation module confirms that the NFS node has a fault, where an issue state of each NFS node in the NFS service cluster is updated according to an issue identifier that is allocated to each shared file instance and has uniqueness, and each NFS node loads issue configuration data corresponding to each shared file instance.
The failure confirmation module 21 is specifically configured to send a status query request to an NFS node that is providing shared file access in the NFS service cluster, and determine whether the NFS node fails according to status information fed back by the NFS node; or receiving state information reported by an NFS node providing shared file access in an NFS service cluster, and determining whether the NFS node fails according to the state information.
An embodiment five of the present invention provides a nonvolatile computer storage medium, where the computer storage medium stores an executable program, and the executable program is executed by a processor to implement the steps of the method for managing shared files in an elastic storage system provided in the first embodiment.
A sixth embodiment of the present invention provides a nonvolatile computer storage medium, where the computer storage medium stores an executable program, and the executable program is executed by a processor to implement the steps of the method for accessing a shared file in an elastic storage system provided in the second embodiment.
The media provided in the fifth embodiment and the sixth embodiment of the present invention may be integrated into the same medium, and the computer storage medium stores an executable program, and the executable program is executed by a processor to implement the step of the method for managing shared files in the elastic storage system provided in the first embodiment, or to implement the step of the method for accessing shared files in the elastic storage system provided in the second embodiment.
A seventh embodiment of the present invention provides a device for managing shared files in an elastic storage system, as shown in fig. 9, which includes a memory 31, a processor 32, and a computer program stored in the memory 31, where the processor 32 implements the steps of the method for managing shared files in an elastic storage system provided in the first embodiment when executing the computer program.
An eighth embodiment of the present invention provides an elastic storage system shared file access device, where a schematic structural diagram of the device may also be as shown in fig. 9, and the device includes a memory, a processor, and a computer program stored in the memory, where the processor implements the steps of the elastic storage system shared file access method provided in the second embodiment when executing the program.
The devices provided in the seventh embodiment and the eighth embodiment of the present invention may be integrated into the same device, and a schematic structural diagram of the device may also be as shown in fig. 9, where the device includes a memory, a processor, and a computer program stored in the memory, and when the processor executes the program, the processor implements the steps of the method for managing shared files in the elastic storage system provided in the first embodiment, or implements the steps of the method for accessing shared files in the elastic storage system provided in the second embodiment.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (10)

1. A method for managing shared files in a flexible storage system is characterized by comprising the following steps:
creating a shared file instance in a storage resource pool, creating publishing configuration data for the shared file instance, wherein the publishing configuration data is configuration data used for publishing of the shared file instance, and distributing a publishing identifier for the shared file instance, and the publishing identifier has uniqueness;
and updating the publishing state of each NFS node in the Network File System (NFS) service cluster by using the publishing identification, and loading the publishing configuration data to each NFS node.
2. The method of claim 1, wherein the method further comprises:
changing the shared file instance and the release configuration data corresponding to the shared file instance;
and changing the publishing state of each NFS node according to the changed publishing configuration data, and loading the changed publishing configuration data to each NFS node or unloading the changed publishing configuration data from each NFS node.
3. A method for accessing a shared file in a flexible storage system, the method comprising:
determining whether an NFS node in a Network File System (NFS) service cluster providing shared file access fails;
and when the NFS node fails, switching the shared file access address to any other NFS node in the NFS service cluster that normally works, wherein the publishing state of each NFS node in the NFS service cluster is updated according to a unique publishing identifier allocated to each shared file instance, and each NFS node loads publishing configuration data corresponding to each shared file instance, where the publishing configuration data is configuration data for publishing of the shared file instance.
4. The method according to claim 3, wherein determining whether an NFS node in an NFS service cluster that is providing shared file access fails comprises:
sending a state query request to an NFS node which is providing shared file access in an NFS service cluster, and determining whether the NFS node fails according to state information fed back by the NFS node; or receiving state information reported by an NFS node providing shared file access in an NFS service cluster, and determining whether the NFS node fails according to the state information.
5. A shared driver node or a proxy node for a shared driver node, the node comprising:
the system comprises a creating module, a storing module and a sending module, wherein the creating module is used for creating a shared file instance in a storage resource pool, creating publishing configuration data for the shared file instance, the publishing configuration data is configuration data used for publishing of the shared file instance, and distributing a publishing identifier for the shared file instance, and the publishing identifier has uniqueness;
and the management module is used for updating the publishing state of each NFS node in the network file system NFS service cluster by using the publishing identification, and loading the publishing configuration data to each NFS node.
6. The node of claim 5, wherein the node further comprises a change module configured to change the shared file instance and to change the publishing configuration data corresponding to the shared file instance;
the management module is further configured to change the publishing state of each NFS node according to the changed publishing configuration data, and load the changed publishing configuration data to each NFS node or unload the changed publishing configuration data from each NFS node.
7. A shared driver node or a proxy node for a shared driver node, the node comprising:
the fault confirmation module is used for determining whether an NFS node which provides shared file access in the NFS service cluster of the network file system has a fault;
and a switching module, configured to switch the shared file access address to any other NFS node that normally works in the NFS service cluster when the fault confirmation module confirms that the NFS node has a fault, where an issue state of each NFS node in the NFS service cluster is updated according to an issue identifier that is allocated to each shared file instance and has uniqueness, and each NFS node loads issue configuration data corresponding to each shared file instance, where the issue configuration data is configuration data for issuing of the shared file instance.
8. The node according to claim 7, wherein the failure confirmation module is specifically configured to send a status query request to an NFS node that is providing shared file access in an NFS service cluster, and determine whether the NFS node fails according to status information fed back by the NFS node; or receiving state information reported by an NFS node providing shared file access in an NFS service cluster, and determining whether the NFS node fails according to the state information.
9. A non-transitory computer storage medium storing an executable program for execution by a processor to perform the steps of the method of any one of claims 1 to 4.
10. An elastic storage system shared file management device, comprising a memory, a processor and a computer program stored on the memory, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 4.
CN201810188002.6A 2018-03-07 2018-03-07 Method for managing and accessing shared file of elastic storage system and related equipment Active CN110247937B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810188002.6A CN110247937B (en) 2018-03-07 2018-03-07 Method for managing and accessing shared file of elastic storage system and related equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810188002.6A CN110247937B (en) 2018-03-07 2018-03-07 Method for managing and accessing shared file of elastic storage system and related equipment

Publications (2)

Publication Number Publication Date
CN110247937A CN110247937A (en) 2019-09-17
CN110247937B true CN110247937B (en) 2021-08-13

Family

ID=67882516

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810188002.6A Active CN110247937B (en) 2018-03-07 2018-03-07 Method for managing and accessing shared file of elastic storage system and related equipment

Country Status (1)

Country Link
CN (1) CN110247937B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111126940B (en) * 2019-11-22 2023-07-11 泰康保险集团股份有限公司 Service application processing method, device, equipment and computer readable storage medium
CN112003892B (en) * 2020-07-19 2022-12-13 苏州浪潮智能科技有限公司 Tgt iSCSI-target configuration global management method

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101699825A (en) * 2009-10-28 2010-04-28 成都市华为赛门铁克科技有限公司 Network file system access method, device and system
CN102870101A (en) * 2009-10-26 2013-01-09 韦尔埃布尔股份有限公司 Concurrent access to memory pool shared between block access device and graph access device
US8812566B2 (en) * 2011-05-13 2014-08-19 Nexenta Systems, Inc. Scalable storage for virtual machines
CN105554074A (en) * 2015-12-07 2016-05-04 上海爱数信息技术股份有限公司 NAS resource monitoring system and monitoring method based on RPC communication
CN106815298A (en) * 2016-12-09 2017-06-09 中电科华云信息技术有限公司 Distributed sharing file system based on block storage

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2513503A1 (en) * 2003-01-17 2004-08-12 Tacit Networks, Inc. Method and system for use of storage caching with a distributed file system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102870101A (en) * 2009-10-26 2013-01-09 韦尔埃布尔股份有限公司 Concurrent access to memory pool shared between block access device and graph access device
CN101699825A (en) * 2009-10-28 2010-04-28 成都市华为赛门铁克科技有限公司 Network file system access method, device and system
US8812566B2 (en) * 2011-05-13 2014-08-19 Nexenta Systems, Inc. Scalable storage for virtual machines
CN105554074A (en) * 2015-12-07 2016-05-04 上海爱数信息技术股份有限公司 NAS resource monitoring system and monitoring method based on RPC communication
CN106815298A (en) * 2016-12-09 2017-06-09 中电科华云信息技术有限公司 Distributed sharing file system based on block storage

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
《Linux实现文件共享方法分析》;胡兰兰;《三门峡职业技术学院学报》;20100322;第9卷(第2期);107-110页 *

Also Published As

Publication number Publication date
CN110247937A (en) 2019-09-17

Similar Documents

Publication Publication Date Title
JP6073246B2 (en) Large-scale storage system
CN106663030B (en) Scalable failover communication in distributed clusters
US10177994B2 (en) Fault tolerant federation of computing clusters
CN109683826B (en) Capacity expansion method and device for distributed storage system
US7685227B2 (en) Message forwarding backup manager in a distributed server system
EP2810164B1 (en) Managing partitions in a scalable environment
US20160275123A1 (en) Pipeline execution of multiple map-reduce jobs
US10908834B2 (en) Load balancing for scalable storage system
CN111125261B (en) Data transmission method based on distributed cache
US20140025909A1 (en) Large scale storage system
CN110247937B (en) Method for managing and accessing shared file of elastic storage system and related equipment
CN112052230B (en) Multi-machine room data synchronization method, computing device and storage medium
CN104793981A (en) Online snapshot managing method and device for virtual machine cluster
CN111045778B (en) Virtual machine creation method, device, server and storage medium
JP5530878B2 (en) Data replication management method in distributed system
CN112732809B (en) ETL system and data processing method based on ETL system
US8898289B1 (en) Distributed event processing method and architecture
CN117009068A (en) Container management method and device
CN115550317A (en) Network resource management method, device, computer equipment and storage medium
JP2019095995A (en) Information processing device, information processing method, and program
IL227415A (en) Large scale storage system

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
GR01 Patent grant
GR01 Patent grant