CN111737018B - ZooKeeper configuration file storage processing method, device, equipment and medium thereof - Google Patents

ZooKeeper configuration file storage processing method, device, equipment and medium thereof Download PDF

Info

Publication number
CN111737018B
CN111737018B CN202010867152.7A CN202010867152A CN111737018B CN 111737018 B CN111737018 B CN 111737018B CN 202010867152 A CN202010867152 A CN 202010867152A CN 111737018 B CN111737018 B CN 111737018B
Authority
CN
China
Prior art keywords
configuration
configuration item
slice data
file
child node
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
CN202010867152.7A
Other languages
Chinese (zh)
Other versions
CN111737018A (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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202010867152.7A priority Critical patent/CN111737018B/en
Publication of CN111737018A publication Critical patent/CN111737018A/en
Application granted granted Critical
Publication of CN111737018B publication Critical patent/CN111737018B/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
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • 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/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/162—Delete operations
    • 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

Abstract

The application discloses a method, a device, equipment and a medium for storing and processing a ZooKeeper configuration file, wherein the method comprises the steps of establishing a configuration item root node corresponding to a configuration file to be written; slicing the configuration file to be written according to a preset standard length to obtain slice data; and creating a configuration item child node according to the slice data, wherein the configuration item child node is used for storing the slice data corresponding to the configuration item child node, and writing the slice data into the configuration item child node. According to the technical scheme, the storage processing of the configuration files with any size can be realized under the condition that any operation parameter of the ZooKeeper is not required to be modified, and the storage efficiency of the ZooKeeper configuration files is effectively improved.

Description

ZooKeeper configuration file storage processing method, device, equipment and medium thereof
Technical Field
The present application relates generally to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for storing and processing a ZooKeeper configuration file.
Background
ZooKeeper is a distributed coordination service that manages large hosts. If some programs are deployed on multiple machines in a decentralized manner, it becomes difficult to change the configuration one by one. These configurations may be stored in a certain directory node of the ZooKeeper, and then all the related applications monitor this directory node, and once the configuration information changes, each application receives the notification of the ZooKeeper, and then acquires new configuration information from the ZooKeeper to apply to the system. The ZooKeeper as a configuration center has the advantage that the ZooKeeper can find the change of some data at any time by using its own watch mechanism, thereby achieving the timeliness of the data.
However, the ZooKeeper as the configuration management center office is subject to the size of the configuration file, resulting in inefficient processing of the configuration file by the ZooKeeper configuration management center.
Disclosure of Invention
In view of the above-mentioned drawbacks or deficiencies in the prior art, it is desirable to provide a ZooKeeper configuration file storage processing method, apparatus, device, and medium thereof to improve the configuration efficiency of a ZooKeeper configuration management center.
In one aspect, an embodiment of the present application provides a method for storing and processing a configuration file based on ZooKeeper, where the method includes:
creating a configuration item root node corresponding to the configuration file to be written, and storing a first message abstract in the configuration item root node, wherein the first message abstract is obtained by calculation based on a storage area of the configuration file to be written;
slicing the configuration file to be written according to a preset standard length to obtain slice data;
creating a configuration item sub-node according to the slice data, wherein the configuration item sub-node is used for storing the corresponding slice data;
and writing the slice data into the configuration item child node.
In one aspect, an embodiment of the present application provides a method for storing and processing a configuration file based on ZooKeeper, where the method includes:
reading slice data stored in a pre-created configuration item child node, wherein the slice data is obtained by slicing a configuration file to be read according to a standard length when the configuration file to be read is written into a storage area;
reading a first message digest stored in a pre-created configuration item root node, wherein the first message digest is obtained by calculation based on a storage area of a configuration file to be read;
and determining whether the configuration file to be read is successfully read or not based on the checksum of the first message digest.
In one aspect, an embodiment of the present application provides a method for storing and processing a configuration file based on ZooKeeper, where the method includes:
deleting the configuration item child nodes according to the number of the configuration item child nodes or the index paths of the configuration item child nodes, wherein the configuration item child nodes are used for storing slice data corresponding to the configuration files to be deleted, and the slice data are obtained by slicing the configuration files to be deleted according to the standard length when the configuration files to be deleted are written into a storage area;
and deleting the root node of the configuration item after all the child nodes of the configuration item corresponding to the configuration file to be deleted are deleted.
In one aspect, an embodiment of the present application provides a ZooKeeper-based configuration file storage processing apparatus, where the apparatus includes:
the root node creating module is used for creating a configuration item root node corresponding to the configuration file to be written, and storing a first message abstract in the configuration item root node, wherein the first message abstract is obtained by calculation based on a storage area of the configuration file to be written;
the slicing processing module is used for slicing the configuration file to be written according to the standard length to obtain slice data;
the child node creating module is used for creating a configuration item child node according to the slice data, and the configuration item child node is used for storing the corresponding slice data;
and the data writing module is used for writing the slice data into the configuration item child node.
In one aspect, an embodiment of the present application provides a ZooKeeper-based configuration file storage processing apparatus, where the apparatus includes:
the slice reading module is used for reading slice data stored in a pre-created configuration item child node, and the slice data is obtained by carrying out slice processing according to a standard length when a configuration file to be read is written into a storage area;
the abstract reading module is used for reading a first message abstract stored in a pre-created configuration item root node, wherein the first message abstract is obtained by calculation based on a storage area of a configuration file to be read;
and the reading determining module is used for determining whether the configuration file to be read is successfully read or not based on the checksum of the first message digest.
In one aspect, an embodiment of the present application provides a ZooKeeper-based configuration file storage processing apparatus, where the apparatus includes:
the subnode deleting module is used for deleting the configuration item subnode according to the number of the pre-created configuration item subnode or the index path of the configuration item subnode, the configuration item subnode is used for storing the slice data corresponding to the configuration file to be deleted, and the slice data is obtained by slicing the configuration file to be deleted according to the standard length when the configuration file to be deleted is written into the storage area;
and the root node deleting module is used for deleting the root node of the configuration item after all the child nodes of the configuration item corresponding to the configuration file to be deleted are deleted.
In one aspect, embodiments of the present application provide a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the program to implement the method as described in embodiments of the present application.
In one aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is configured to:
which when executed by a processor implements a method as described in embodiments of the present application.
According to the method, the device, the equipment and the medium for storing and processing the ZooKeeper configuration file, the root node of the configuration item corresponding to the configuration file to be written is created; slicing the configuration file to be written according to a preset standard length to obtain slice data; then, a configuration item child node is created from the slice data, and the slice data is written to the configuration item child node. By the technical scheme provided by the embodiment, the storage processing of the configuration file with any size can be realized without modifying any operation parameter of the ZooKeeper, and the storage efficiency of the ZooKeeper configuration file is effectively improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a diagram illustrating an implementation environment architecture of a ZooKeeper-based profile storage method according to an embodiment of the present application;
fig. 2 is a schematic flowchart illustrating a ZooKeeper-based configuration file writing processing method according to an embodiment of the present application;
fig. 3 is a schematic data structure diagram of a ZooKeeper storage configuration file provided in an embodiment of the present application;
fig. 4 is a schematic flowchart illustrating a ZooKeeper-based configuration file writing processing method according to an embodiment of the present application;
fig. 5 is a schematic data structure diagram of a ZooKeeper storage configuration file provided in an embodiment of the present application;
fig. 6 is a schematic flowchart illustrating a ZooKeeper-based configuration file reading processing method according to an embodiment of the present application;
fig. 7 is a schematic flowchart illustrating a ZooKeeper-based configuration file reading processing method according to an embodiment of the present application;
fig. 8 is a schematic flowchart illustrating a ZooKeeper-based profile deletion processing method according to an embodiment of the present application;
fig. 9 is a schematic flowchart illustrating a ZooKeeper-based profile deletion processing method according to an embodiment of the present application;
fig. 10 is a block diagram illustrating an exemplary structure of a ZooKeeper-based configuration file write processing apparatus according to an embodiment of the present application;
fig. 11 is a block diagram illustrating an exemplary structure of a ZooKeeper-based configuration file reading processing apparatus according to an embodiment of the present application;
fig. 12 is a block diagram illustrating an exemplary structure of a ZooKeeper-based profile deletion processing apparatus according to an embodiment of the present application;
FIG. 13 illustrates a schematic structural diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant disclosure and are not limiting of the disclosure. It should be further noted that, for the convenience of description, only the portions relevant to the disclosure are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Interpretation of related art terms
Zookeeper, a typical distributed data consistency solution, can provide functions of centralized management of configuration files, fault tolerance, load balancing, etc., and the internal data storage uses an organization structure of a file directory tree. The ZooKeeper can run on a single machine, and a plurality of zookeepers can be configured into a cluster mode to carry out disaster tolerance or improve the read-write performance.
The configuration management center is a module used for carrying out unified management, updating and issuing on configuration information in a large-scale distributed system. The large-scale distributed system comprises a plurality of different subsystems, a plurality of different functional modules, even the same functional module also comprises a plurality of different sub-nodes, the configuration requirements of each subsystem, functional module and sub-node are different, and the configuration management center is used for solving the configuration problem of the large-scale distributed system.
Referring to fig. 1, fig. 1 is a diagram illustrating an implementation environment architecture of a Zookeeper configuration file storage method according to an embodiment of the present application. As shown in fig. 1, the implementation environment architecture includes: a configuration management client 101, a configuration management center 102, and a worker node 103.
The configuration management client 101 is configured to obtain a configuration file and then write the configuration file into the configuration management center 102. The configuration management client may load the configuration file from the database.
And the configuration management center 102 is used for storing configuration files. The configuration management center adopts ZooKeeper. The ZooKeeper includes a plurality of nodes, some of which may be used to store configuration information, i.e., configuration files. Typically the profile size requires that a maximum of 1MB cannot be exceeded.
And the working node 103 is used for acquiring the configuration file stored in the configuration management center. Here, the working node 103 is a service subsystem that subscribes to a configuration file stored by the configuration management center according to requirements.
The configuration management client 101 and the configuration management center 102 described above may be configured in separate physical servers.
The working node 103 may be configured in an independent server, may also be a server cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform.
The working node 103 actively subscribes the configuration file, and when the configuration file in the configuration management center changes, the configuration node can obtain the configuration parameters contained in the new configuration file without redeploying or restarting, and when the configuration parameters need to be obtained each time, the latest configuration parameters are obtained in real time.
In the related art, if the configuration file exceeding 1MB is written into the ZooKeeper, the parameter "-djute. However, modifying only this parameter of the ZooKeeper can cause the ZooKeeper to be unstable or even rushing.
When the parameter "-djute. maxbuffer" of the ZooKeeper is modified to overcome the size limit of a single storage node, the ZooKeeper client needs to modify the size of the network read-write buffer and the size of the read-write request encoding buffer at the same time. If the sizes of the two buffers are not modified, the ZooKeeper client will cause the process to run due to buffer overflow.
Or when the ZooKeeper performs data migration or node expansion, the configuration parameters of the target ZooKeeper server need to be synchronously modified, otherwise the target ZooKeeper server may cause a start error due to a data loading error.
The embodiment of the application provides a method for storing configuration files with any size, which can effectively solve the problems, does not need to modify any parameters of the ZooKeeper, and effectively improves the processing efficiency of the configuration files.
The ZooKeeper-based configuration file storage method can be described in three aspects of a configuration file writing process, a configuration file reading process and a configuration file deleting process.
To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operation instruction steps as shown in the following embodiments or figures, more or less operation instruction steps may be included in the method based on the conventional or non-inventive labor. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application. The method can be executed in sequence or in parallel according to the method shown in the embodiment or the figure when the method is executed in an actual processing procedure or a device.
The ZooKeeper-based profile write processing method is described below in conjunction with fig. 2-5. Referring to fig. 2, fig. 2 is a schematic flowchart illustrating a Zookeeper-based configuration file writing method according to an embodiment of the present application. As shown in fig. 2, the method includes:
step 201, creating a configuration item root node corresponding to a configuration file to be written; and storing a first message digest in the configuration item root node, wherein the first message digest is calculated based on the storage area of the configuration file to be written.
Step 202, slicing a configuration file to be written according to a preset standard length to obtain slice data;
step 203, creating a configuration item child node according to the slice data, wherein the configuration item child node is used for storing the corresponding slice data;
and step 204, writing the slice data into the configuration item child node.
In the above step, the configuration file to be written refers to the configuration information received from the configuration management client. The configuration information may be stored in a database.
The configuration item root node refers to a storage position used for storing relevant information of the configuration file in a ZooKeeper data storage structure. The related information may be, for example, a message digest used for checking the configuration file, or a storage path of sliced data obtained by slicing the configuration file, or a combination of the two.
As shown in fig. 3, fig. 3 illustrates a data storage structure used by the ZooKeeper storage configuration file proposed in the embodiment of the present application.
In fig. 3, the configuration item root node refers to a storage location corresponding to "/config/producer/producer _ 1".
The configuration item child node refers to a storage location for storing slice data related to a configuration file. In FIG. 3, the configuration item child node may be, for example
A storage location corresponding to "/config/producer/producer _ 1/1";
a storage location corresponding to "/config/producer/producer _ 1/2";
"/config/producer/producer _ 1/3".
The standard length refers to the size of the configuration file that conforms to the ZooKeeper specification. For example, the ZooKeeper specified profile supports a 1MB size. The standard length may be 1 MB. The standard length may also be a size of a profile set according to a user requirement, and may be, for example, a size smaller than a profile supported by Zookeeper, such as 800 Kb.
The slicing processing of the configuration file to be written according to the preset standard length may include the following steps: reading the current file length of the configuration file to be written; and according to the comparison result of the current file length and the standard length, carrying out slicing processing on the configuration file to be written.
The current file length refers to the size of the corresponding configuration file before the configuration file to be written is written into the storage area. For example, before writing into the storage area for the first time, the current file length refers to the total size of the configuration file; before writing the storage area for the second time, the current file length is the size of the configuration file obtained by subtracting the standard length from the original file length after writing the storage area for the first time. For example, taking the size of the configuration file to be written as 5MB and the standard length as 1MB as an example, the current file length is 5MB before the configuration file is written into the storage area for the first time. Before writing to the storage area for the second time, the current file length is 4 MB.
And then, slicing the configuration file to be written according to the current file length and the standard length. The slicing processing refers to dividing the configuration file to be written according to a standard length. For example, the standard length is 1MB and the profile to be written is 5 MB. If the configuration file is stored continuously, the configuration file to be written is divided, the starting physical address of the configuration file to the storage area and the ending physical address corresponding to 1MB in the configuration file can be read first, and a data block, namely the file content corresponding to the standard length, is read between the starting physical address and the ending physical address. Each time the file content corresponding to the standard length is obtained, it may be referred to as a slice data.
By analogy, after 1MB of file content is read from the 5MB configuration file, the file content is 0-1 MB. And deleting the storage position corresponding to the 1MB file. Then, the 1MB file is read from the rest 4MB configuration file as the second slice data, the second slice data corresponds to the storage location with the new start physical address of 1025Kb of the 5MB configuration file, and the end physical address of the second slice data corresponds to the storage location with the end physical address of 2048Kb of the 5MB configuration file. Up to 5MB of the profile is sliced into 5 slices of 1MB of data.
The slicing the configuration file to be written based on the comparison result between the current file length and the standard length may include: determining whether the length of the current file is greater than or equal to the standard length;
when the length of the current file is larger than or equal to the standard length, reading the file content corresponding to the standard length from the current initial position of the configuration file to be written as slice data; cutting the read file content corresponding to the standard length from the configuration file to be written; updating the current initial position of the configuration file to be written; returning and reading the current file length of the configuration file until the current initial position of the configuration file to be written is zero;
and when the length of the current file is smaller than the standard length, taking the configuration file to be written as slice data.
In the above step, after obtaining a slice data, creating a configuration item child node corresponding to the slice data, and writing the slice data into a storage location corresponding to the configuration item child node. And repeating the slicing processing step, creating configuration item child nodes corresponding to the slicing data, and writing the slicing data into the configuration item child nodes until all the configuration files to be written are sliced, and writing the configuration item child nodes corresponding to the slicing data into the configuration item child nodes. The current starting position refers to a starting position of the configuration file to be written before the configuration file to be written is divided. For example, at the time of first slicing, the start position of the profile to be written in the storage area is the current start position. In the second slicing process, the storage position of the configuration file to be written after the content with the standard length is cut off is the current starting position.
On the basis of the above embodiment, the configuration item child node is created from slice data, and can be created by the following steps: after the slice data are obtained, creating a configuration item child node corresponding to the slice data under the configuration item root node; a number corresponding to the configuration item child node is assigned.
As shown in FIG. 3, under the configuration item root node "/config/producer/producer _ 1", 3 configuration item child nodes "/config/producer/producer _ 1/1", "/config/producer/producer _ 1/2", "/config/producer/producer _ 1/3" are created. Wherein the ID numbers are/1,/2,/3.
According to the method and the device, the problem of instability of the Zookeeper in the related technology can be solved by creating the configuration item child node without changing the logic structure of the Zookeeper or modifying any operation parameter of the Zookeeper, the configuration item child node is created in a self-adaptive mode according to the configuration file, and the writing efficiency of the configuration file is greatly improved.
In the above embodiment, after creating the root node of the configuration item corresponding to the configuration file to be written, the method further includes: calculating the message abstract of the configuration file to be written according to the storage area of the configuration file to be written; and storing the message digest to the configuration item root node.
The message digests are stored in the root nodes of the configuration items, and then the completeness and effectiveness of data are guaranteed based on the checksum of the message digests, so that the efficiency of storing the configuration files based on the Zookeeper is effectively improved.
Optionally, in the above embodiment, the configuration item child node is created according to slice data, and may also be created by: after the slice data is obtained, creating a root node for a storage item, wherein the storage item root node has the same level as the root node of the configuration item; creating a configuration item child node corresponding to the slice data under the storage item root node; and allocating the index path corresponding to the configuration item child node.
As shown in fig. 5, fig. 5 is a schematic diagram illustrating another data storage structure provided in the embodiment of the present application. In fig. 5, the same-level storage item root node "/config _ concent" of the configuration item root node is created, and under the storage item root node, 3 configuration item child nodes "/config _ concent/1", "/config _ concent/2", "/config _ concent/3" are created.
The above-mentioned storage item root node refers to a newly created storage location for storing and slicing data. After creating the storage item root node, a storage location corresponding to the slice data is further created.
Calculating the message abstract of the configuration file to be written according to the storage area of the configuration file to be written; storing the message abstract to a configuration item root node; and after the index path corresponding to the configuration item child node is distributed, storing the index path to the configuration item root node.
As shown in fig. 5, on the configuration item root node/config/producer/producer _1, the message digest MD5 and storage paths part _1, part _2, part _3 corresponding to 3 pieces of slice data corresponding to the configuration file are stored, and these storage paths are used to read the slice data.
For example, part _1=/config _ content/1 corresponding to the first slice data; part _1=/config _ content/2 corresponding to the second slice data; part _1=/config _ content/3 corresponding to the third slice data.
The configuration file writing method can support configuration files with any size, does not need to modify any operation parameter, does not need the Zookeeper client to modify the size of a network read-write buffer area and the size of a read-write request coding buffer area, and also has the problems of process running caused by buffer overflow of the client and the like.
In order to more clearly understand the above Zookeeper-based profile writing method, the following description is further developed in conjunction with fig. 3 and 4. The configuration file to be written includes the following:
{ "name": producer 1 ",
“input_tuple”:[
{
“name”:“a”，
“type”：“uint8”,
“len”:1}],
“output_tuple”:[
{
“name”:“a”，
“type”：“uint8”,
“len”:1}]
}。
after obtaining the configuration file, as shown in fig. 4, the method includes the steps of:
step S41, calculates the 32-bit message digest MD5 of the configuration file, and writes the calculated message digest MD5 into the pre-created configuration item root node.
This step may include:
and reading the configuration file to be written, and storing the configuration file to be written into the memory by using the byte array conf. For example, the flag byte array conf has a length Len.
Then, a 32-bit message digest of byte array conf is computed, labeled MD 5.
Pre-creating/config/producer/producer _1 as a root node of the configuration item, and after calculating the message digest, writing the message digest MD5 in the root node of the configuration item.
Step 42, reading 1MB of file content from the configuration file; the number of the configuration item child node to be created is initialized, i.e. ID = 1.
Step 43, writing the read file content into the configuration item sub-node corresponding to the number of the configuration item sub-node; and updates the number, i.e. ID = ID + 1.
The file content that has been read is cut out of the configuration file, step 44.
Step 45, determine whether the length Len of the byte array conf is 0.
The above steps 42 to 45 may obtain the length Len of the byte data conf, and determine whether Len is greater than or equal to 1 MB.
When the length Len is equal to or greater than 1MB, 1MB of file content is cut out from the start position of the byte array conf as one piece of slice data.
When the length Len is less than 1MB, the entire contents of the byte array conf are truncated as one slice data.
The intercepted file content is marked as slice data cur _ slice, and the length of the slice data cur _ slice is marked as len _ cur _ slice. After the slice data is obtained, a configuration item child node/config/producer/producer _1/{ ID } is created, and then the slice data cur _ slice is written in the configuration item child node.
Further, the number of the child node of the update configuration item is ID = ID +1;
the slice data cur _ slice is cut out from the byte array conf to obtain cut byte data conf, and the corresponding length of the cut byte data conf is Len = Len-Len _ cur _ slice.
Returning to the step of reading 1MB of file content from the configuration file, the step of reading 1MB of slice data continues until the length Len of the byte data conf is equal to 0, and the whole writing process is ended.
After the configuration file is processed according to the method shown in fig. 4, the configuration file is stored in ZooKeeper according to the data storage format of fig. 3.
The configuration file writing method can support configuration files with any size, does not need to modify any operation parameter, does not need the Zookeeper client to modify the size of a network read-write buffer area and the size of a read-write request coding buffer area, and does not have the problems of process running and the like caused by buffer overflow of the client.
Referring to fig. 6, fig. 6 is a schematic flowchart illustrating a Zookeeper-based configuration file reading method according to an embodiment of the present application. As shown in fig. 6, the method includes:
step 601, reading slice data stored in a configuration item child node created in advance.
The slice data is obtained by slicing the configuration file to be read according to the standard length when the configuration file to be read is written into the storage area;
step 602, reading a first message digest stored in a pre-created configuration item root node, wherein the first message digest is calculated based on a storage area of a configuration file to be read;
step 603, determining whether the configuration file to be read is successfully read based on the checksum of the first message digest.
According to different storage structures of the configuration files, different reading modes can be adopted, for example, when the configuration item child nodes are created under the configuration item root node, the numbers of all the configuration item child nodes under the configuration item root node are read; reading slice data stored in the configuration item sub-node corresponding to the serial number according to the serial number of the configuration item sub-node;
or when the configuration item child node is created under the storage item root node with the same hierarchy as the configuration item root node, reading an index path of the configuration item child node stored in the configuration item root node; and reading the slice data stored in the configuration item child node corresponding to the index path according to the index path of the configuration item child node.
The index path refers to a storage location for storing slice data created under the same storage item root node as the hierarchy of the configuration item root node. Also referred to as memory paths.
Since the configuration file is stored in a storage mode of slice data, in order to ensure the integrity of the read data, the integrity of the read data is verified by carrying out checksum on the first message digest.
The step 603 may include the following steps: storing the slice data read from the configuration item child nodes into a new storage area; after all configuration item child nodes under the configuration item root node are read, calculating a second message digest based on the new storage area; and determining whether the reading operation of the configuration file to be read is successful or not based on the comparison result of the first message digest and the second message digest. If the first message abstract is the same as the second message abstract, the configuration file to be read is successfully read; and if the first message abstract is different from the second message abstract, the configuration file to be read fails to be read.
The following describes an implementation process of the Zookeeper-based configuration file reading processing method with reference to fig. 3 and 7. Take the example of a configuration file stored according to the data structure shown in fig. 3. As shown in fig. 7, the method includes:
and step S71, reading the first message digest stored in the configuration item root node/config/producer/producer _ 1. To distinguish the new message digest generated during the checksum process, it is denoted herein as a first message digest MD 5.
Obtaining the number N of configuration item child nodes under the root node of the configuration item
Initializing the serial number ID of the configuration item child node to be read, namely ID =1;
and creating a new blank byte array for storing the slice data read from the configuration item child node. The length corresponding to the byte array is CONF.
Step S72, reading the file content stored in the configuration item sub node corresponding to the number of the configuration item sub node. Then, the read slice data is stored into a new byte array.
The configuration item child node corresponding to the number is the file content of/config/producer/producer _1/{ ID }, i.e., the slice data. The length of the slice data may be labeled PART CONT.
And storing the file contents read from the configuration item child node into a new blank byte array, namely CONT = CONT + PART _ CONT.
In step S73, the current number is updated, i.e., ID = ID + 1.
After the reading of the file contents from the configuration item child node is completed, the current number is updated, so that the reading of the slice data stored in all the configuration item child nodes under the configuration item root node is completed.
Step S74, determine whether the current number is greater than the number N of all configuration item child nodes under the configuration item root node.
Step S75, if yes, calculating a second message digest CONT _ MD5 corresponding to the byte array CONF;
step S76, if not, returning to step 72, and continuing to read the content corresponding to the configuration item child node.
At step S77, it is determined whether the first message digest MD5 is equal to the second message digest CONT _ MD 5.
In step S78, if the first message digest MD5 is different from the second message digest CONT _ MD5, it indicates a read failure.
In step S79, if the first message digest MD5 is the same as the second message digest CONT _ MD5, it indicates that the reading is successful.
Based on the above embodiment, the MD5 is verified to ensure that the read configuration file is complete and valid. If MD5 checks fail, the possible reason is that traffic may be retried later during normal generation or deletion of the configuration.
After the configuration file is stored according to the above embodiment, the user may delete the storage node of the configuration file according to the requirement. Referring to fig. 8, fig. 8 is a schematic flowchart illustrating a Zookeeper-based profile deletion processing method according to an embodiment of the present application. As shown in fig. 8, the method includes:
step 801, deleting the configuration item child node according to the number of the configuration item child node created in advance or the index path of the configuration item child node.
The configuration item child node is used for storing slice data corresponding to the configuration file to be deleted;
the slicing data is obtained by slicing the configuration file to be deleted according to the standard length when the configuration file to be deleted is written into the storage area.
Step 802, after all the configuration item child nodes corresponding to the configuration file to be deleted are deleted, the configuration item root node is deleted.
On the basis of the above embodiment, deleting the configuration item child node according to the number of the configuration item child node created in advance may further include: firstly, acquiring the number of configuration item child nodes under a configuration item root node, and then determining the number of the configuration item child nodes to be deleted; deleting the configuration item child nodes corresponding to the numbers; updating the serial number; and then, returning to the step of deleting the configuration item child nodes corresponding to the numbers, and continuing to execute the step of deleting the configuration item child nodes until the number of the deleted configuration item child nodes reaches the number of the configuration item child nodes contained in the pre-created configuration item root node.
On the basis of the above embodiment, deleting the configuration item child node according to the index path of the configuration item child node created in advance, may further include: firstly, reading an index path which is stored in a configuration item root node and corresponds to a configuration item child node; deleting the configuration item child nodes according to the index path; deleting the root node of the storage item after all the child nodes of the configuration item corresponding to the index path stored in the root node of the configuration item are deleted; after deleting the storage item root node, deleting the configuration item root node.
In order to more clearly understand the process of deleting the node storing the configuration file proposed by the present application, a configuration file deletion processing method based on ZooKeeper is described below with reference to fig. 3 and 9.
As shown in fig. 3, a first message digest of the configuration file is stored at the configuration item root node, and 3 configuration item child nodes are stored under the configuration item root node. As shown in fig. 9, the method for deleting a configuration file according to the present application may include the following steps:
step S91, acquiring the number N of configuration item child nodes under the configuration item root node/config/producer/producer _1, and initializing the number of the configuration item child nodes to be deleted, namely ID =1;
in step S92, the configuration item child node corresponding to the number/ID is deleted.
For example, configuration item child/config/producer/producer _1/{ ID }.
In step S93, after deleting one configuration item child node, the update number ID = ID + 1.
In step S94, if the number ID of the configuration item child node to be deleted (i.e. the number of deleted configuration item child nodes) is greater than the number N of the corresponding configuration item child nodes under the configuration item root node, go to step S95. Otherwise, the process returns to step S92.
And step S95, deleting the configuration item root node/config/producer/producer _1, wherein the deletion is successful.
And if not, returning to delete the configuration item child node/config/producer/producer _1/{ ID }, and continuing to execute until the number ID of the deleted configuration item child node is greater than the number N of the configuration item child nodes under the configuration item root node.
Referring further to fig. 10, fig. 10 is a block diagram illustrating an exemplary structure of a Zookeeper-based profile writing apparatus according to an embodiment of the present application. As shown in fig. 10, the apparatus includes:
a root node creating module 1001 configured to create a root node of a configuration item corresponding to a configuration file to be written; and storing a first message digest in the configuration item root node, wherein the first message digest is calculated based on the storage area of the configuration file to be written.
The slicing processing module 1002 is configured to perform slicing processing on the configuration file to be written according to the standard length to obtain slice data;
a child node creating module 1003, configured to create a configuration item child node according to the slice data, where the configuration item child node is configured to store the slice data corresponding to the configuration item child node;
a data writing module 1004, configured to write the slice data into the configuration item child node.
The slicing processing module further includes:
the file length reading submodule is used for reading the current file length of the configuration file to be written;
and the slicing processing submodule is used for slicing the configuration file to be written according to the comparison result of the length of the current file and the standard length.
Wherein the slice processing sub-module is further configured to:
when the length of the current file is larger than or equal to the standard length, reading the file content corresponding to the standard length from the current initial position of the configuration file to be written as slice data;
cutting the read file content corresponding to the standard length from the configuration file to be written;
updating the current initial position of the configuration file to be written;
returning the current file length of the read configuration file until the current initial position of the configuration file to be written is zero;
and when the length of the current file is smaller than the standard length, taking the configuration file to be written as slice data.
The child node creation module is further configured to:
after the slice data are obtained, creating a configuration item child node corresponding to the slice data under the configuration item root node;
a number corresponding to the configuration item child node is assigned.
The child node creation module is further configured to:
after the slice data is obtained, creating a root node for a storage item, wherein the storage item root node has the same level as the root node of the configuration item;
creating a configuration item child node corresponding to the slice data under the storage item root node;
and allocating the index path corresponding to the configuration item child node.
The configuration file writing method can support configuration files with any size, does not need to modify any operation parameter, does not need the Zookeeper client to modify the size of a network read-write buffer area and the size of a read-write request coding buffer area, and also has the problems of process running caused by buffer overflow of the client and the like.
Referring further to fig. 11, fig. 11 is a block diagram illustrating an exemplary structure of a Zookeeper-based profile reading processing apparatus according to an embodiment of the present application. As shown in fig. 11, the apparatus includes:
the slice reading module 1101 is configured to read slice data stored in a pre-created configuration item child node, where the slice data is obtained by slicing a configuration file to be read according to a standard length when the configuration file to be read is written in a storage area;
a digest reading module 1102, configured to read a first message digest stored in a pre-created configuration item root node, where the first message digest is calculated based on a storage area of a configuration file to be read;
a reading determination module 1103, configured to determine whether the configuration file to be read is successfully read based on the checksum of the first message digest.
The slice reading module further comprises:
the number reading sub-module is used for reading the numbers of all the configuration item sub-nodes under the configuration item root node when the configuration item sub-nodes are established under the configuration item root node;
the first slice reading sub-module is used for reading slice data stored in the configuration item sub-node corresponding to the serial number according to the serial number of the configuration item sub-node;
the slice reading module further comprises:
the path reading sub-module is used for reading the index path of the configuration item sub-node stored in the configuration item root node when the configuration item sub-node is created under the storage item root node with the same hierarchy as the configuration item root node;
and the second slice reading sub-module is used for reading slice data stored in the configuration item sub-node corresponding to the index path according to the index path of the configuration item sub-node.
A read determination module, further comprising:
the message abstract calculation sub-module is used for calculating a second message abstract based on a new storage area, and the new storage area is used for storing the slice data read from the configuration item sub-node;
the reading result determining submodule is used for determining that the configuration file to be read is successfully read if the first message abstract is the same as the second message abstract; and if the first message abstract is different from the second message abstract, determining that the configuration file to be read fails to be read.
Referring further to fig. 12, fig. 12 is a block diagram illustrating an exemplary structure of a Zookeeper-based profile deletion processing apparatus according to an embodiment of the present application. As shown in fig. 12, the apparatus includes:
a child node deleting module 1201, configured to delete a configuration item child node according to a pre-created number of the configuration item child node or an index path of the configuration item child node, where the configuration item child node is configured to store slice data corresponding to a configuration file to be deleted, and the slice data is obtained by slicing the configuration file to be deleted according to a standard length when the configuration file to be deleted is written in a storage area;
a root node deleting module 1202, configured to delete the root node of the configuration item after all the child nodes of the configuration item corresponding to the configuration file to be deleted are deleted.
It should be understood that the units or modules described in the apparatus correspond to the individual steps of the method described above. Thus, the operation instructions and features described above for the method are also applicable to the apparatus and the units included therein, and are not described herein again. The device can be implemented in a browser or other security applications of the electronic equipment in advance, and can also be loaded into the browser or other security applications of the electronic equipment in a downloading mode or the like. Corresponding elements in the apparatus may cooperate with elements in the electronic device to implement aspects of embodiments of the present application.
The division into several modules or units mentioned in the above detailed description is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Referring now to FIG. 13, FIG. 13 illustrates a block diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
As shown in fig. 13, the computer system includes a Central Processing Unit (CPU)1301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1302 or a program loaded from a storage portion 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation instructions of the system 1300 are also stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.
The following components are connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.
In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart fig. 1 may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a machine-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program executes the above-described functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 1301.
It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operational instructions of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, and may be described as: a processor includes a root node creation module, a slice processing module, a child node creation module, and a data write module. The names of these units or modules do not in some cases form a limitation on the units or modules themselves, for example, the root node creation module may also be described as "root node for creating configuration items corresponding to configuration files to be written".
As another aspect, the present application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may be separate and not incorporated into the electronic device. The computer-readable storage medium stores one or more programs that, when executed by one or more processors, perform the ZooKeeper-based profile storage processing method described herein.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the disclosure. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.

Claims (13)

1. A ZooKeeper-based configuration file storage processing method is characterized by comprising the following steps:
creating a configuration item root node corresponding to a configuration file to be written, and storing a first message digest in the configuration item root node, wherein the first message digest is obtained by calculation based on a storage area of the configuration file to be written, and the configuration file to be written is configuration information received from a configuration management client;
slicing the configuration file to be written according to a preset standard length to obtain slice data;
creating a configuration item sub-node according to the slice data, wherein the configuration item sub-node is used for storing the corresponding slice data;
writing the slice data to the configuration item child node;
wherein the creating a configuration item child node according to the slice data comprises:
after the slice data is obtained, creating a storage item root node, wherein the storage item root node has the same level as the configuration item root node;
creating a configuration item child node corresponding to the slice data under the storage item root node;
and allocating the index path corresponding to the configuration item child node.
2. The method according to claim 1, wherein the slicing the configuration file to be written according to a preset standard length comprises:
reading the current file length of the configuration file to be written;
and slicing the configuration file to be written according to the comparison result of the length of the current file and the standard length.
3. The method of claim 2, wherein the slicing the configuration file to be written based on the comparison of the current file length and the standard length comprises:
when the length of the current file is larger than or equal to the standard length, reading the file content corresponding to the standard length from the current initial position of the configuration file to be written as slice data;
cutting the read file content corresponding to the standard length from the configuration file to be written;
updating the current initial position of the configuration file to be written;
returning to the step of reading the current file length of the configuration file and continuing to execute slicing processing until the current initial position of the configuration file to be written is zero;
and when the length of the current file is smaller than the standard length, taking the configuration file to be written as slice data.
4. The method of claim 1, wherein creating a configuration item child node from the slice data comprises:
after the slice data are obtained, creating a configuration item child node corresponding to the slice data under the configuration item root node;
assigning a number corresponding to the configuration item child node.
5. A ZooKeeper-based configuration file storage processing method is characterized by comprising the following steps:
reading slice data stored in a pre-created configuration item child node, wherein the slice data is obtained by slicing a configuration file to be read according to a standard length when the configuration file to be read is written into a storage area;
reading a first message digest stored in a pre-created configuration item root node, wherein the first message digest is obtained by calculation based on a storage area of the configuration file to be read;
determining whether the configuration file to be read is successfully read or not based on the checksum of the first message digest;
wherein, the reading the slice data stored in the configuration item child node created in advance includes:
when the configuration item child node is created under the storage item root node with the same hierarchy as the configuration item root node, reading an index path of the configuration item child node stored in the configuration item root node;
and reading the slice data stored in the configuration item child node corresponding to the index path according to the index path of the configuration item child node.
6. The method of claim 5, wherein reading slice data stored in a pre-created configuration item child node comprises:
reading the number of the configuration item child node under the configuration item root node when the configuration item child node is created under the configuration item root node;
and reading the slice data stored in the configuration item sub-node corresponding to the serial number according to the serial number of the configuration item sub-node.
7. The method of claim 5, wherein the determining whether the configuration file to be read is successfully read based on the checksum of the first message digest comprises:
calculating a second message digest based on a new storage area, wherein the new storage area is used for storing slice data read from the configuration item child node;
if the first message abstract is the same as the second message abstract, determining that the configuration file to be read is read successfully;
and if the first message abstract is different from the second message abstract, determining that the configuration file to be read fails to be read.
8. A ZooKeeper-based configuration file storage processing method is characterized by comprising the following steps:
deleting the configuration item child nodes according to the number of the configuration item child nodes or the index paths of the configuration item child nodes, wherein the configuration item child nodes are used for storing slice data corresponding to the configuration files to be deleted, and the slice data are obtained by slicing the configuration files to be deleted according to the standard length when the configuration files to be deleted are written into a storage area;
deleting the root node of the configuration item after all the child nodes of the configuration item corresponding to the configuration file to be deleted are deleted;
wherein, deleting the configuration item child node according to the pre-created index path of the configuration item child node includes:
reading an index path which is stored in a configuration item root node and corresponds to the configuration item child node;
and deleting the configuration item child nodes according to the index path.
9. A ZooKeeper-based profile storage processing apparatus, comprising:
a root node creating module, configured to create a configuration item root node corresponding to a configuration file to be written, and store a first message digest in the configuration item root node, where the first message digest is calculated based on a storage area of the configuration file to be written, and the configuration file to be written is configuration information received from a configuration management client;
the slicing processing module is used for slicing the configuration file to be written according to the standard length to obtain slice data;
a child node creating module, configured to create a configuration item child node according to the slice data, where the configuration item child node is configured to store slice data corresponding to the configuration item child node;
a data writing module, configured to write the slice data into the configuration item child node;
the child node creating module is configured to create a storage item root node after the slice data is obtained, where the storage item root node has the same level as the configuration item root node;
creating a configuration item child node corresponding to the slice data under the storage item root node;
and allocating the index path corresponding to the configuration item child node.
10. A Zookeeper-based configuration file storage processing device is characterized by comprising:
the slice reading module is used for reading slice data stored in a pre-created configuration item child node, wherein the slice data is obtained by performing slice processing according to a standard length when a configuration file to be read is written into a storage area;
the abstract reading module is used for reading a first message abstract stored in a pre-created configuration item root node, wherein the first message abstract is obtained by calculation based on a storage area of the configuration file to be read;
a reading determination module, configured to determine whether the configuration file to be read is successfully read based on a checksum of the first message digest;
the slice reading module is configured to, when the configuration item child node is created under a storage item root node having the same hierarchy as the configuration item root node, read an index path of the configuration item child node stored in the configuration item root node;
and reading the slice data stored in the configuration item child node corresponding to the index path according to the index path of the configuration item child node.
11. A ZooKeeper-based profile storage processing apparatus, comprising:
a child node deleting module, configured to delete a configuration item child node according to a pre-created number of the configuration item child node or an index path of the configuration item child node, where the configuration item child node is configured to store slice data corresponding to a configuration file to be deleted, and the slice data is obtained by slicing the configuration file to be deleted according to a standard length when the configuration file to be deleted is written in a storage area;
a root node deleting module, configured to delete the configuration item root node after all configuration item child nodes corresponding to the configuration file to be deleted are deleted;
wherein the child node deletion module: the index path corresponding to the configuration item child node and stored in the configuration item root node is read;
and deleting the configuration item child nodes according to the index path.
12. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-4, or of any of claims 5-7, or of claim 8 when executing the program.
13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-4, or claims 5-7, or claim 8.
CN202010867152.7A 2020-08-26 2020-08-26 ZooKeeper configuration file storage processing method, device, equipment and medium thereof Active CN111737018B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010867152.7A CN111737018B (en) 2020-08-26 2020-08-26 ZooKeeper configuration file storage processing method, device, equipment and medium thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010867152.7A CN111737018B (en) 2020-08-26 2020-08-26 ZooKeeper configuration file storage processing method, device, equipment and medium thereof

Publications (2)

Publication Number Publication Date
CN111737018A CN111737018A (en) 2020-10-02
CN111737018B true CN111737018B (en) 2020-12-22

Family

ID=72658887

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010867152.7A Active CN111737018B (en) 2020-08-26 2020-08-26 ZooKeeper configuration file storage processing method, device, equipment and medium thereof

Country Status (1)

Country Link
CN (1) CN111737018B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114020346B (en) * 2021-09-29 2023-07-18 苏州浪潮智能科技有限公司 Configuration file processing method and device, electronic equipment and storage medium
CN115277735B (en) * 2022-07-20 2023-11-28 北京达佳互联信息技术有限公司 Data processing method and device, electronic equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1766875A (en) * 2004-10-29 2006-05-03 株式会社东芝 System and method for retrieving structured document
CN111241064A (en) * 2020-01-10 2020-06-05 深圳震有科技股份有限公司 Database configuration file processing method and device and storage medium

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8719580B2 (en) * 2009-06-26 2014-05-06 Trusted Logic Data verification method
CN102710554B (en) * 2012-06-25 2015-09-02 深圳中兴网信科技有限公司 The service state detection method of distributed information system and distributed information system
CN102779185B (en) * 2012-06-29 2014-11-12 浙江大学 High-availability distribution type full-text index method
CN103473287A (en) * 2013-08-30 2013-12-25 中国科学院信息工程研究所 Method and system for automatically distributing, running and updating executable programs
US9690671B2 (en) * 2013-11-01 2017-06-27 Cloudera, Inc. Manifest-based snapshots in distributed computing environments
CN103905537A (en) * 2014-03-20 2014-07-02 冶金自动化研究设计院 System for managing industry real-time data storage in distributed environment
CN105320527A (en) * 2014-06-12 2016-02-10 中兴通讯股份有限公司 Configuration file renewing method, device and system based on zookeeper distributed type search engine
CN105208078A (en) * 2015-08-13 2015-12-30 飞狐信息技术（天津）有限公司 File storage system and method
CN106547859B (en) * 2016-10-21 2021-02-09 杭州朗和科技有限公司 Data file storage method and device under multi-tenant data storage system
CN106936899B (en) * 2017-02-25 2021-02-05 九次方大数据信息集团有限公司 Configuration method of distributed statistical analysis system and distributed statistical analysis system
CN108389129B (en) * 2018-02-27 2020-12-04 创新先进技术有限公司 Transaction execution method and device based on block chain and electronic equipment
CN110730478B (en) * 2019-10-18 2021-12-21 腾讯科技（深圳）有限公司 Slice association method, device, end-to-end slice organizer and storage medium
CN110825420B (en) * 2019-11-26 2023-09-22 中国银行股份有限公司 Method, device, equipment and storage medium for updating configuration parameters of distributed cluster
CN111666256B (en) * 2020-05-27 2024-03-22 南京通用电器有限公司 Video file disk management method and device based on index file

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1766875A (en) * 2004-10-29 2006-05-03 株式会社东芝 System and method for retrieving structured document
CN111241064A (en) * 2020-01-10 2020-06-05 深圳震有科技股份有限公司 Database configuration file processing method and device and storage medium

Also Published As

Publication number Publication date
CN111737018A (en) 2020-10-02

Similar Documents

Publication Publication Date Title
US11782949B2 (en) Violation resolution in client synchronization
US10725976B2 (en) Fast recovery using self-describing replica files in a distributed storage system
CN111737018B (en) ZooKeeper configuration file storage processing method, device, equipment and medium thereof
US10747643B2 (en) System for debugging a client synchronization service
CN110765187A (en) Data source route management method and device
CN109522043B (en) Method and device for managing configuration data and storage medium
US10970193B2 (en) Debugging a client synchronization service
CN113032356A (en) Cabin distributed file storage system and implementation method
CN111444148A (en) Data transmission method and device based on MapReduce
CN114065724A (en) Method, apparatus and computer program product for metadata comparison
CN109992447B (en) Data copying method, device and storage medium
CN112711572B (en) Online capacity expansion method and device suitable for database and table division
CN114969206A (en) Data processing method, device, equipment and storage medium
CN113541987A (en) Method and device for updating configuration data
CN114928604B (en) File distribution method and device
CN115827563A (en) Metadata management method and device
CN117389475A (en) Data processing method and device
CN115167769A (en) Method, device and system for writing data
CN114756173A (en) Method, system, device and computer readable medium for file merging
CN114090524A (en) Excel file distributed exporting method and device
CN115437848A (en) Data backup method and device, electronic equipment and storage medium
CN114500485A (en) Data processing method and device
CN117170884A (en) Chart rendering method, apparatus, electronic device and storage medium
CN117389735A (en) Distributed data management method and device
CN117082046A (en) Data uploading method, device, equipment and storage 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
GR01 Patent grant
GR01 Patent grant
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40030087

Country of ref document: HK