CN111046009B - Log storage method and device - Google Patents
Log storage method and device Download PDFInfo
- Publication number
- CN111046009B CN111046009B CN201911094101.9A CN201911094101A CN111046009B CN 111046009 B CN111046009 B CN 111046009B CN 201911094101 A CN201911094101 A CN 201911094101A CN 111046009 B CN111046009 B CN 111046009B
- Authority
- CN
- China
- Prior art keywords
- log
- platform
- storage
- module
- logs
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- 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
-
- 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/185—Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a log storage method and a log storage device, wherein the method is applied to a management level platform in a distributed log management system, the distributed log management system also comprises at least one subordinate platform, and the method comprises the following steps: receiving a log sent by the connected network equipment; determining whether to store the received logs in a grading manner according to the set log storage mode; if yes, distributing a lower platform for each log, and sending the log to the distributed lower platform for storage; if not, the log is stored locally. By the method, the phenomenon that the management level platform and the subordinate platform are overfilled with the magnetic disk can be effectively avoided, and various performances of the management level platform and the subordinate platform are improved.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a log storage method and device.
Background
The log is information of problems and events generated in the network equipment when hardware, software, a system and the like run, and a user can effectively grasp the running condition of the network equipment, locate the cause of error occurrence or search traces and the like left by an attacker when the attacker is attacked by counting and analyzing the log.
The traditional log storage system adopts a centralized storage server to store logs generated by all network devices, and the logs are continuously generated along with the operation of the network devices, so that the storage space of a disk on the storage server is continuously consumed, and indexes such as performance, reliability, safety and the like of the storage server are also tested.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for storing logs, so as to solve the problem in the prior art that the centralized storage server is used to store logs generated by all network devices, so that the storage space of a disk on the storage server is continuously consumed, and all performance indexes of the storage server are affected.
Specifically, the application is realized by the following technical scheme:
according to a first aspect of an embodiment of the present application, there is provided a log storage method, the method being applied to a management level platform in a distributed log management system, the distributed log management system further including at least one subordinate platform, the method including:
receiving a log sent by the connected network equipment;
determining whether to store the received logs in a grading manner according to the set log storage mode;
if yes, distributing a lower platform for each log, and sending the log to the distributed lower platform for storage; if not, the log is stored locally.
Optionally, the allocating a lower platform to each log includes:
traversing a local log storage path when the set log distribution condition is met;
distributing a lower platform for the traversed log;
after the log is sent to the assigned lower platform for storage, the method further comprises:
and deleting the sent log from the local log storage path.
Optionally, the method further comprises:
receiving a log query request sent by a client;
determining whether to perform hierarchical inquiry according to the log storage mode;
if yes, the log inquiry request is issued to at least one subordinate platform, so that the subordinate platform inquires logs matched with the log inquiry request in a local way; if not, locally inquiring the log matched with the log inquiry request.
Optionally, the method further comprises:
receiving a log query result sent by the lower platform, wherein the log query result comprises log information of logs which are queried by the lower platform and are matched with the log query request;
and reporting the log query result to the client for display.
Optionally, the log storage mode includes:
load sharing distribution mode, or load sharing non-distribution mode.
According to a second aspect of embodiments of the present application, there is provided a log storage device applied to a management level platform in a distributed log management system, the distributed log management system further including at least one subordinate platform, the device comprising:
the log receiving module is used for receiving logs sent by the connected network equipment;
the first determining module is used for determining whether the received logs are stored in a grading manner according to the set log storage mode;
the log distribution module is used for distributing a lower stage platform for each log if the received logs are determined to be stored in a grading manner, and sending the logs to the distributed lower stage platforms for storage;
and the log storage module is used for locally storing the received logs if the received logs are determined not to be stored in a grading manner.
Optionally, the log distribution module includes:
the traversal submodule is used for traversing the local log storage path when the set log distribution condition is met;
the distribution sub-module is used for distributing a lower platform for the traversed log;
the apparatus further comprises:
and the log deleting module is used for deleting the sent log from the local log storage path.
Optionally, the apparatus further includes:
the request receiving module is used for receiving a log query request sent by the client;
the second determining module is used for determining whether to perform hierarchical inquiry according to the log storage mode;
the request issuing module is used for issuing the log query request to at least one lower platform if the hierarchical query is determined, so that the lower platform locally queries the log matched with the log query request;
and the query module is used for querying the logs matched with the log query request locally if the fact that the hierarchical query is not performed is determined.
Optionally, the apparatus further includes:
the result receiving module is used for receiving a log query result sent by the lower-level platform, wherein the log query result comprises log information of a log which is queried by the lower-level platform and is matched with the log query request;
and the result reporting module is used for reporting the log query result to the client for display.
Optionally, the log storage mode includes:
load sharing distribution mode, or load sharing non-distribution mode.
According to the method, after receiving the logs sent by the connected network equipment, the management stage platform can send the logs to the lower stage platform for storage, and can also store the logs locally, so that the distributed storage of the logs can be realized, the phenomenon that the management stage platform and the lower stage platform are overfilled with magnetic disks is effectively avoided, and various performances of the management stage platform and the lower stage platform are improved.
Drawings
FIG. 1 is a schematic diagram of a distributed log management system implementing a log storage method according to an embodiment of the present application;
FIG. 2 is a flowchart of an embodiment of a log storage method according to an exemplary embodiment of the present application;
FIG. 3 is a flow chart illustrating an implementation of step 203 according to an exemplary embodiment of the present application;
FIG. 4 is a flowchart illustrating an implementation of a log query process according to an exemplary embodiment of the present application;
FIG. 5 is a hardware configuration diagram of a server where the log storage device of the present application is located.
FIG. 6 is a block diagram of an embodiment of a log storage device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
Referring to fig. 1, an architecture diagram of a distributed log management system implementing a log storage method according to an embodiment of the present application is shown.
As shown in fig. 1, the distributed log management system 100 includes log management platforms 101 to 104 and a network 105. Network 105 is used to provide a communication link between log management platforms 101-104 and may include a wireless link, a wired link, or a fiber optic cable, as the application is not limited in this regard. The log management platforms 101-104 may be hardware supporting log storage, analysis, management, etc. services including, but not limited to, desktop computers, servers, server clusters, etc.
In practical application, a user may set one of the log management platforms 101 to 104 as a management level platform according to factors such as performance, service type, and the number of connected network devices, and the other platforms are lower platforms of the management level platform. For example, the log management platform 101 is set as a management level platform, and the log management platforms 102 to 104 are set as subordinate platforms.
It will be appreciated that the number of networks and devices in fig. 1 is merely illustrative. The distributed log management system architecture 100 may include any number of networks and devices, as desired, and the application is not limited in this regard.
Thus, the description of the system architecture shown in fig. 1 is completed.
For ease of understanding, two log storage modes involved in the embodiment of the present application will be described with reference to the system architecture illustrated in fig. 1, where the following two log storage modes are set for the management level platform as an example:
(1) Load sharing distribution mode
In the load sharing distribution mode, all network devices (e.g., firewalls, terminal devices, routers, etc.) connect to the management level platform, that is, all network devices send the generated logs to the management level platform in unison. And the management level platform can distribute the received log to the lower level platform for storage in the load sharing distribution mode, and the log is not stored on the management level platform.
In addition, in the load sharing distribution mode, the management level platform may synchronize device information (e.g., IP address, serial number, etc.) of the connected network device to each lower level platform.
(2) Load sharing non-distribution mode
In the load sharing non-distribution mode, the management stage platform and each lower stage platform are respectively connected with network equipment, that is, in the load sharing non-distribution mode, the management stage platform and each lower stage platform are respectively independent log storage platforms, and the network equipment sends generated logs to the connected platform and stores the generated logs by the connected platform.
In addition, in the load sharing non-distribution mode, each lower stage platform can report the device information of the connected network device to the management stage platform, and the management can be facilitated through the processing.
So far, the description of two log storage modes involved in the embodiment of the present application is completed.
The log storage method proposed by the application is described below by way of examples:
referring to fig. 2, a flowchart of an embodiment of a log storage method according to an exemplary embodiment of the present application may be applied to a management level platform, such as platform 101, in the distributed log management system 100 illustrated in fig. 1, as an example.
As shown in fig. 2, the process may include the steps of:
step 201: and receiving the log sent by the connected network equipment.
In the application, the network device sends the log generated by the running time to the log management platform connected with the network device, so that the log management platform can receive the log sent by the network device connected with the network device.
In the present application, as is known from the above description, the management stage platform is connected to the network device in either the load sharing distribution mode or the load sharing non-distribution mode, so that in this step 201, the management stage platform can receive the log sent by the network device to which it is connected.
Step 202: determining whether to store the received logs in a grading manner according to the set log storage mode; if yes, go to step 203, if no, go to step 204.
As can be seen from the above description, in the load sharing distribution mode, the management stage platform may distribute the received log to the lower stage platform for storage, and the management stage platform does not store the log, while in the load sharing non-distribution mode, the manager platform is an independent log storage platform, and may directly store the log sent by the network device connected with the manager platform.
Based on this, in this step 202, the management stage platform may determine to hierarchically store the received log when it is set in the load sharing distribution mode, perform step 203, and may determine not to hierarchically store the received log when it is set in the load sharing non-distribution mode, perform step 204.
Step 203: and allocating a lower platform for each log, and sending the log to the allocated lower platform for storage.
The management level platform determines that the received logs are stored in a hierarchical manner through the step 202, and in this step 203, the management level platform may allocate a lower level platform to each log, and send the log to the allocated lower level platform for storing.
As to how the management level platform allocates the lower level platform to each log, it is shown by way of example hereinafter, and will not be described in detail here.
Step 204: the log is stored locally.
The management level platform has determined through step 202 described above that the received log is not to be hierarchically stored, then in this step 204 the management level platform can store the received log directly locally.
According to the embodiment, after the log sent by the connected network equipment is received, the management stage platform can send the log to the lower stage platform for storage and can also store the log locally, so that the distributed storage of the log can be realized, the phenomenon that the management stage platform and the lower stage platform are overfilled with magnetic disks is effectively avoided, and various performances of the management stage platform and the lower stage platform are improved.
The following describes how the management level platform assigns the lower level platform to each log separately:
referring to fig. 3, a flow of one implementation of step 203 is shown for an exemplary embodiment of the present application. As shown in fig. 3, the process may include the steps of:
step 301: and traversing the local log storage path when the set log distribution condition is met.
As an example, the management level platform may first register the log locally when receiving the log sent by the network device. In the application, when the set log distribution condition is satisfied, the process of distributing the log to the lower platform is executed again.
As an example, the log distribution condition set above may be: the set timer reaches the timeout time. That is, the management level platform may execute a flow of distributing logs to the lower level platform at regular intervals.
As an example, the log distribution condition set above may be: the number of the logs stored by the management level platform reaches a set number threshold, or the storage space occupied by the logs reaches a set space threshold.
As one example, the management level platform may traverse the local log storage path when the set log distribution condition is satisfied.
Step 302: and distributing a lower platform for the traversed log, and sending the log to the distributed lower platform for storage.
As an example, the management level platform may traverse to one log at a time, i.e., assign a lower level platform to the traversed log, and send the log to the assigned lower level platform for storage.
As one example, the management level platform may employ an average random allocation algorithm to allocate a lower level platform to the traversed log.
As an example, the management level platform may obtain storage related information of each lower level platform, such as storage amount, size of remaining storage space, and the like, and allocate one lower level platform to the traversed log. As to how the management level platform obtains the storage related information of each lower level platform, the description thereof will be omitted.
As an example, the management level platform may send the log to the allocated lower level platform for storage by way of FTP (File Transfer Protocol ).
Step 303: the transmitted log is deleted from the local log storage path.
As is clear from the above description, the management level platform does not store the log in the load sharing distribution mode, and thus, in this step 303, the management level platform may delete the transmitted log from the local log storage path.
Thus, the flow shown in fig. 3 is completed.
Through the flow shown in fig. 3, the management stage platform is finally realized to respectively allocate the lower stage platform for each received log in the load sharing distribution mode, and the log is sent to the allocated lower stage platform for storage.
It should be noted that, the flow illustrated in fig. 3 is merely an exemplary illustration of how the management level platform allocates a lower level platform to each log, and in practical application, the management level platform may also allocate a lower level platform to a log in other manners, for example, the management level platform may allocate a lower level platform to a log after receiving one log, which is not limited in this aspect of the present application.
In addition, in the application, there is a requirement for log query, and the following description is given by way of example to the process of log query:
referring to fig. 4, an implementation flow of the log query procedure according to an exemplary embodiment of the present application is provided.
As shown in fig. 4, the process may include the steps of:
step 401: and receiving a log query request sent by the client.
In the application, a user can send a log query request to the management level platform through the client, so that the management level platform can receive the log query request sent by the client.
As one example, the log query request may include, but is not limited to: log generation time, event type, network device identification, etc.
Step 402: determining whether to perform hierarchical inquiry according to the log storage mode; if yes, go to step 403, if no, go to step 404.
As can be seen from the above description, in the load sharing distribution mode, the management stage platform may distribute the received log to the lower stage platform for storage, and the management stage platform does not store the log, while in the load sharing non-distribution mode, the manager platform is an independent log storage platform, and may directly store the log sent by the network device connected with the manager platform.
Based on this, in this step 402, the management level platform may determine to perform a hierarchical query when it is set in the load sharing distribution mode, perform step 403, and may determine not to perform a hierarchical query when it is set in the load sharing non-distribution mode, perform step 404.
Step 403: the log query request is issued to at least one subordinate platform, so that the subordinate platform locally queries the log matching the log query request, and step 405 is performed.
The management stage platform determines to perform the hierarchical query through the above step 402, and then in step 403, the management stage platform may issue the log query request received in step 401 to at least one lower stage platform, so that the lower stage locally queries the log matched with the log query request.
As one example, the management level platform may issue a log query request to each of the subordinate platforms.
As one example, the management level platform may issue log query requests to a portion of the subordinate platforms. For example, the lower level platform may be specified in advance by the user, so that in this step 403, the management level platform may issue a log query request to the lower level platform specified by the user.
As to how the lower platform locally queries the log matched with the log query request, the present application is not repeated.
Step 404: the logs that match the log query request are queried locally.
The management level platform has determined that no hierarchical queries have been made via step 402 described above, then in this step 404 the management level platform may query locally for logs that match the log query request. As to how the management level platform locally queries the log matched with the log query request, the present application will not be described in detail.
Step 405: receiving a log query result sent by a lower platform, wherein the log query result comprises log information of logs which are queried by the lower platform and are matched with the log query request.
In the application, if the lower platform locally inquires the log matched with the log inquiry request, the log information of the matched log can be used as a log inquiry result to be sent to the management platform, so that the management platform can receive the log inquiry result sent by the lower platform.
As one example, the log information may include, but is not limited to: log generation time, event type, network device identification, log keywords, such as internet traffic, access web sites, etc.
Step 406: and reporting the log query result to the client for display.
In the present application, after receiving the log query result sent by the lower platform through executing step 405, the management stage platform may report the log query result to the client for display.
By the embodiment shown in fig. 4, the log query is finally implemented on the basis of the distributed storage log.
The application also provides an embodiment of the log storage device corresponding to the embodiment of the log storage method.
Embodiments of the log storage device of the present application may be applied to a server. The apparatus embodiments may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking software implementation as an example, the device in a logic sense is formed by reading corresponding computer program instructions in a nonvolatile memory into a memory by a processor of a server where the device is located. In terms of hardware, as shown in fig. 5, a hardware structure diagram of a server where the log storage device of the present application is located is shown in fig. 5, and the server where the device is located in the embodiment generally includes other hardware according to the actual function of the server, except for the processor 51, the memory 52, the network interface 53, the nonvolatile memory 54 and the internal bus 55 shown in fig. 5, which will not be described again.
Referring to fig. 6, a block diagram of an embodiment of a log storage device according to an exemplary embodiment of the present application is provided, where the device may be applied to a management level platform in a distributed log management system, and the distributed log management system further includes at least one lower level platform, and the device may include: a log receiving module 61, a first determining module 62, a log distributing module 63, and a log storing module 64.
The log receiving module 61 is configured to receive a log sent by a connected network device;
a first determining module 62, configured to determine whether to hierarchically store the received log according to the set log storage mode;
the log distribution module 63 is configured to, if it is determined that the received logs are stored in a hierarchical manner, allocate a lower stage platform to each log, and send the log to the allocated lower stage platform for storage;
the log storage module 64 is configured to store the received log locally if it is determined that the received log is not stored in a hierarchical manner.
In one embodiment, the log distribution module 63 includes (not shown in fig. 6):
the traversal submodule is used for traversing the local log storage path when the set log distribution condition is met;
the distribution sub-module is used for distributing a lower platform for the traversed log;
the device further comprises (not shown in fig. 6):
and the log deleting module is used for deleting the sent log from the local log storage path.
In an embodiment, the apparatus further comprises (not shown in fig. 6):
the request receiving module is used for receiving a log query request sent by the client;
the second determining module is used for determining whether to perform hierarchical inquiry according to the log storage mode;
the request issuing module is used for issuing the log query request to at least one lower platform if the hierarchical query is determined, so that the lower platform locally queries the log matched with the log query request;
and the query module is used for querying the logs matched with the log query request locally if the fact that the hierarchical query is not performed is determined.
In an embodiment, the apparatus further comprises (not shown in fig. 6):
the result receiving module is used for receiving a log query result sent by the lower-level platform, wherein the log query result comprises log information of a log which is queried by the lower-level platform and is matched with the log query request;
and the result reporting module is used for reporting the log query result to the client for display.
In an embodiment, the log storage mode includes: load sharing distribution mode, or load sharing non-distribution mode.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.
Claims (8)
1. A log storage method, wherein the method is applied to a management level platform in a distributed log management system, the distributed log management system further comprising at least one subordinate platform, the method comprising:
receiving a log sent by the connected network equipment;
determining whether to store the received logs in a grading manner according to the set log storage mode;
if yes, distributing a lower platform for each log, and sending the log to the distributed lower platform for storage; if not, the log is stored locally;
the method further comprises the steps of:
receiving a log query request sent by a client;
determining whether to perform hierarchical inquiry according to the log storage mode;
if yes, the log inquiry request is issued to at least one subordinate platform, so that the subordinate platform inquires logs matched with the log inquiry request in a local way; if not, locally inquiring the log matched with the log inquiry request.
2. The method of claim 1, wherein assigning a lower level platform to each log comprises:
traversing a local log storage path when the set log distribution condition is met;
distributing a lower platform for the traversed log;
after the log is sent to the assigned lower platform for storage, the method further comprises:
and deleting the sent log from the local log storage path.
3. The method according to claim 1, wherein the method further comprises:
receiving a log query result sent by the lower platform, wherein the log query result comprises log information of logs which are queried by the lower platform and are matched with the log query request;
and reporting the log query result to the client for display.
4. A method according to any one of claims 1 to 3, wherein the log storage mode comprises:
load sharing distribution mode, or load sharing non-distribution mode.
5. A log storage device for use in a management level platform in a distributed log management system, the distributed log management system further comprising at least one subordinate platform, the device comprising:
the log receiving module is used for receiving logs sent by the connected network equipment;
the first determining module is used for determining whether the received logs are stored in a grading manner according to the set log storage mode;
the log distribution module is used for distributing a lower stage platform for each log if the received logs are determined to be stored in a grading manner, and sending the logs to the distributed lower stage platforms for storage;
the log storage module is used for locally storing the received logs if the received logs are determined not to be stored in a grading manner;
the apparatus further comprises:
the request receiving module is used for receiving a log query request sent by the client;
the second determining module is used for determining whether to perform hierarchical inquiry according to the log storage mode;
the request issuing module is used for issuing the log query request to at least one lower platform if the hierarchical query is determined, so that the lower platform locally queries the log matched with the log query request;
and the query module is used for querying the logs matched with the log query request locally if the fact that the hierarchical query is not performed is determined.
6. The apparatus of claim 5, wherein the log distribution module comprises:
the traversal submodule is used for traversing the local log storage path when the set log distribution condition is met;
the distribution sub-module is used for distributing a lower platform for the traversed log;
the apparatus further comprises:
and the log deleting module is used for deleting the sent log from the local log storage path.
7. The apparatus of claim 5, wherein the apparatus further comprises:
the result receiving module is used for receiving a log query result sent by the lower-level platform, wherein the log query result comprises log information of a log which is queried by the lower-level platform and is matched with the log query request;
and the result reporting module is used for reporting the log query result to the client for display.
8. The apparatus according to any one of claims 5 to 7, wherein the log storage mode includes:
load sharing distribution mode, or load sharing non-distribution mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911094101.9A CN111046009B (en) | 2019-11-11 | 2019-11-11 | Log storage method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911094101.9A CN111046009B (en) | 2019-11-11 | 2019-11-11 | Log storage method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111046009A CN111046009A (en) | 2020-04-21 |
| CN111046009B true CN111046009B (en) | 2023-11-21 |
Family
ID=70232352
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911094101.9A Active CN111046009B (en) | 2019-11-11 | 2019-11-11 | Log storage method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111046009B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571845A (en) * | 2010-12-20 | 2012-07-11 | 南京中兴新软件有限责任公司 | Data storage method and device of distributed storage system |
| CN103051681A (en) * | 2012-12-06 | 2013-04-17 | 华中科技大学 | Collaborative type log system facing to distribution-type file system |
| US9104745B1 (en) * | 2012-09-28 | 2015-08-11 | Palo Alto Networks, Inc. | Distributed log collector and report generation |
| CN105516367A (en) * | 2016-02-02 | 2016-04-20 | 北京百度网讯科技有限公司 | Distributed data storage system, method and device |
| CN106777371A (en) * | 2017-01-23 | 2017-05-31 | 北京齐尔布莱特科技有限公司 | Result collection system and method |
| CN106843750A (en) * | 2016-12-20 | 2017-06-13 | 中国科学院苏州生物医学工程技术研究所 | Distributed memory system |
| CN107835095A (en) * | 2017-11-20 | 2018-03-23 | 杭州迪普科技股份有限公司 | A kind of processing method and processing device of daily record |
| CN107947954A (en) * | 2016-10-12 | 2018-04-20 | 腾讯科技（深圳）有限公司 | Dynamic adjustment journal stage other system, method and server |
| CN108712296A (en) * | 2018-06-07 | 2018-10-26 | 郑州云海信息技术有限公司 | One kind being based on distributed daily record monitoring device and method |
| CN108846070A (en) * | 2018-06-07 | 2018-11-20 | 北京京东尚科信息技术有限公司 | Log processing method, system, electronic equipment and the storage medium of distributed system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110040788A1 (en) * | 2009-08-14 | 2011-02-17 | Ic Manage, Inc. | Coherent File State System Distributed Among Workspace Clients |
| EP2635980A1 (en) * | 2010-09-27 | 2013-09-11 | Telefonaktiebolaget L M Ericsson (PUBL) | Distributed database |
| JP2014182653A (en) * | 2013-03-19 | 2014-09-29 | Canon Inc | Log management system, log management method, image forming apparatus and control method thereof, and program |
-
2019
- 2019-11-11 CN CN201911094101.9A patent/CN111046009B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571845A (en) * | 2010-12-20 | 2012-07-11 | 南京中兴新软件有限责任公司 | Data storage method and device of distributed storage system |
| US9104745B1 (en) * | 2012-09-28 | 2015-08-11 | Palo Alto Networks, Inc. | Distributed log collector and report generation |
| CN103051681A (en) * | 2012-12-06 | 2013-04-17 | 华中科技大学 | Collaborative type log system facing to distribution-type file system |
| CN105516367A (en) * | 2016-02-02 | 2016-04-20 | 北京百度网讯科技有限公司 | Distributed data storage system, method and device |
| CN107947954A (en) * | 2016-10-12 | 2018-04-20 | 腾讯科技（深圳）有限公司 | Dynamic adjustment journal stage other system, method and server |
| CN106843750A (en) * | 2016-12-20 | 2017-06-13 | 中国科学院苏州生物医学工程技术研究所 | Distributed memory system |
| CN106777371A (en) * | 2017-01-23 | 2017-05-31 | 北京齐尔布莱特科技有限公司 | Result collection system and method |
| CN107835095A (en) * | 2017-11-20 | 2018-03-23 | 杭州迪普科技股份有限公司 | A kind of processing method and processing device of daily record |
| CN108712296A (en) * | 2018-06-07 | 2018-10-26 | 郑州云海信息技术有限公司 | One kind being based on distributed daily record monitoring device and method |
| CN108846070A (en) * | 2018-06-07 | 2018-11-20 | 北京京东尚科信息技术有限公司 | Log processing method, system, electronic equipment and the storage medium of distributed system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111046009A (en) | 2020-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3418877B1 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| US7962635B2 (en) | Systems and methods for single session management in load balanced application server clusters | |
| US9298732B2 (en) | Searching cloud-based distributed storage resources using a set of expendable probes | |
| US6928459B1 (en) | Plurality of file systems using weighted allocation to allocate space on one or more storage devices | |
| US20200364608A1 (en) | Communicating in a federated learning environment | |
| US7392261B2 (en) | Method, system, and program for maintaining a namespace of filesets accessible to clients over a network | |
| CN103975571B (en) | High Availabitity network file manager with automatic Load balance and property regulation | |
| US7523454B2 (en) | Apparatus and method for routing a transaction to a partitioned server | |
| CN107241319B (en) | Distributed network crawler system based on VPN and scheduling method | |
| JP2007133586A (en) | Resource allocation arbitration device and resource allocation arbitration method | |
| US20100057935A1 (en) | Record medium with a load distribution program recorded thereon, load distribution method, and load distribution apparatus | |
| US9411648B2 (en) | Flexible resource configuration management for computing clusters | |
| US20060224731A1 (en) | Method for measuring server performance, system for measuring server performance and computer programs therefor | |
| WO2020042427A1 (en) | Reconciliation method and apparatus based on data fragments, computer device, and storage medium | |
| CN108124020A (en) | Domain name analytic method, system and equipment | |
| US20220318071A1 (en) | Load balancing method and related device | |
| CN110798507B (en) | Method and system for DHCP address allocation memory | |
| CN105978744B (en) | A kind of resource allocation methods, apparatus and system | |
| CN111163186A (en) | ID generation method, device, equipment and storage medium | |
| CN111046009B (en) | Log storage method and device | |
| CN109005071B (en) | Decision deployment method and scheduling equipment | |
| CN109451090B (en) | Domain name resolution method and device | |
| US9537748B1 (en) | Finding shortest path in multi-access nodes in cloud service | |
| Liu Sheng et al. | Data allocation design in computer networks: LAN versus MAN versus WAN | |
| US20060168108A1 (en) | Methods and systems for defragmenting subnet space within an adaptive infrastructure |
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 |