CN108471387A - A kind of daily record flow decentralized control method and system - Google Patents
A kind of daily record flow decentralized control method and system Download PDFInfo
- Publication number
- CN108471387A CN108471387A CN201810257323.7A CN201810257323A CN108471387A CN 108471387 A CN108471387 A CN 108471387A CN 201810257323 A CN201810257323 A CN 201810257323A CN 108471387 A CN108471387 A CN 108471387A
- Authority
- CN
- China
- Prior art keywords
- daily record
- service node
- cluster service
- end applications
- target
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
Abstract
This application provides a kind of daily record flow decentralized control method and systems, in this application, the size for the daily record total amount and the goal-selling daily record flow that target journaling collector cluster service node receives described in；If the daily record total amount received is not more than the goal-selling daily record flow, journal engine is written into the daily record of the target front end applications；If the daily record total amount received is more than the goal-selling daily record flow, then abandon the daily record of the target front end applications, it can be with the log collection flow of control targe log concentrator cluster service node, therefore in log concentrator cluster, in this way, the control of log collection flow may be implemented in log concentrator cluster service node.
Description
Technical field
This application involves daily record flow control technology field, more particularly to a kind of daily record flow decentralized control method and it is
System.
Background technology
Nowadays, internet has become people's daily life inalienable part, shopping, chat, reading etc.
All carry out on the internet.Since people are while using Internet application system, the individuation data of oneself can be stayed in
On internet, therefore Internet application system all generates and needs the valuable daily record data recorded daily, and internet is answered
It is generally required with system and collects these daily record datas, for carrying out correlation analysis.
Currently, generally by the daily record data of the multiple distribution application systems of distributed information log collector centralized collection, but
How to control the collection of log data flow of distributed information log collector becomes problem.
Invention content
In order to solve the above technical problems, a kind of daily record flow decentralized control method of the embodiment of the present application offer and system, with
Achieve the purpose that realize that the more service node decentralised control log collection flows of log concentrator cluster, technical solution are as follows：
A kind of daily record flow decentralized control method, including：
Target journaling collector cluster service node receives the log request that target front end applications are sent；
The target journaling collector cluster service node obtains the target front end applications from the log request
Daily record, and being counted to the daily record of the target front end applications, the result of counting is as the target front end applications described
The daily record total amount received on target journaling collector cluster service node；
The target journaling collector cluster service node obtains the goal-selling daily record flow of the target front end applications；
The relatively more described daily record total amount received of the target journaling collector cluster service node and the goal-selling
The size of daily record flow；
If the daily record total amount received is not more than the goal-selling daily record flow, by the target front end applications
Daily record be written journal engine；
If the daily record total amount received is more than the goal-selling daily record flow, the target front end applications are abandoned
Daily record.
Preferably, the determination process of the target journaling collector cluster service node, including：
The affiliated node of the target front end applications obtains log concentrator cluster service node from decentralized configuration center
The weight of list and each log concentrator cluster service node；
The affiliated node of the target front end applications utilizes load-balancing algorithm, the log concentrator cluster service node
The weight of list and each log concentrator cluster service node determines each log concentrator cluster service node
In for receive the target front end applications daily record node, as the target journaling collector cluster service node.
Preferably, the goal-selling daily record flow is obtained by the decentralized configuration center configuration；
The configuration process of the log concentrator cluster service node listing, including：
Register each log concentrator cluster, each log concentrator group service node in the decentralized configuration center
And the weight of each log concentrator cluster service node；
List is written in the information of each log concentrator cluster service node by the decentralized configuration center, is obtained
The log concentrator cluster service node listing.
Preferably, the target front end applications obtain log concentrator cluster service node listing from decentralized configuration center
And the weight of each log concentrator cluster service node, including：
The target front end applications obtain log concentrator collection in a manner of asynchronous notifications, from the decentralized configuration center
The weight of group's service node list and each log concentrator cluster service node.
Preferably, the target journaling collector cluster service node obtains the goal-selling day of the target front end applications
Will flow, including：
The target journaling collector cluster service node is obtained in a manner of asynchronous notifications from the decentralized configuration center
Take goal-selling daily record total flow, the log concentrator cluster service node listing and each day of each front end applications
The weight of will collector cluster service node；
The target journaling collector cluster service node is according to the goal-selling daily record total flow and each day
The ratio of the weight of will collector cluster service node calculates each front end applications in the target journaling collector collection
Goal-selling daily record flow on group's service node；
The target journaling collector cluster service node deposits the goal-selling daily record flow of each front end applications
Storage is in local cache；
The target journaling collector cluster service node obtains the target front end applications from the local cache
Goal-selling daily record flow.
A kind of daily record flow scattered control system, including：Target journaling collector cluster service node, the target journaling
Collector cluster service node includes：
Receiving module, the log request for receiving the transmission of target front end applications；
Counting module, the daily record for obtaining the target front end applications from the log request, and to the target
The daily record of front end applications is counted, and the result of counting is as the target front end applications in the target journaling collector cluster
The daily record total amount received on service node；
First acquisition module, the goal-selling daily record flow for obtaining the target front end applications；
Comparison module, the size of daily record total amount and the goal-selling daily record flow for being received described in comparison, if
The daily record total amount received is not more than the goal-selling daily record flow, then executes writing module, is received if described
Daily record total amount is more than the goal-selling daily record flow, then executes discard module；
Said write module, for journal engine to be written in the daily record of the target front end applications；
The discard module, the daily record for abandoning the target front end applications.
Preferably, the system also includes：The affiliated node of target front end applications and decentralized configuration center, the target
The affiliated node of front end applications includes：
Second acquisition module, for from the decentralized configuration center obtain log concentrator cluster service node listing and
The weight of each log concentrator cluster service node；
Determining module, for utilizing load-balancing algorithm, the log concentrator cluster service node listing and each institute
The weight for stating log concentrator cluster service node determines in each log concentrator cluster service node for receiving institute
The node for stating the daily record of target front end applications, as the target journaling collector cluster service node.
Preferably, the decentralized configuration center is for configuring the goal-selling daily record flow；
The decentralized configuration center includes：
Registration module, for registering each log concentrator cluster, each log concentrator group service node and each
The weight of a log concentrator cluster service node；
List Generating Module is obtained for list to be written in the information of each log concentrator cluster service node
The log concentrator cluster service node listing.
Preferably, second acquisition module is specifically used in a manner of asynchronous notifications, from the decentralized configuration center
Obtain the weight of log concentrator cluster service node listing and each log concentrator cluster service node.
Preferably, first acquisition module includes：
First acquisition unit, in a manner of asynchronous notifications, obtaining each front end from the decentralized configuration center and answering
Goal-selling daily record total flow, the log concentrator cluster service node listing and each log concentrator cluster
The weight of service node；
Computing unit, for according to the goal-selling daily record total flow and each log concentrator cluster service section
It is default on the target journaling collector cluster service node to calculate each front end applications for the ratio of the weight of point
Target journaling flow；
Storage unit, for the goal-selling daily record flow of each front end applications to be stored in local cache；
Second acquisition unit, the goal-selling log stream for obtaining the target front end applications from the local cache
Amount.
Compared with prior art, the application has the beneficial effect that：
In this application, target journaling collector cluster independently compares the day received by each service node
The size of will total amount and the goal-selling daily record flow；If the daily record total amount received is not more than the goal-selling day
Then journal engine is written in the daily record of the target front end applications by will flow；If the daily record total amount received is more than described
Goal-selling daily record flow then abandons the daily record of the target front end applications, can with the daily record flow of control targe front end applications,
Therefore in log concentrator cluster, each node is all made of this mode, and respective control section daily record flow reaches daily record receipts
The purpose of the more service node decentralised control log collection flows of storage cluster, to realize that the entirety to daily record flow controls.
Description of the drawings
In order to more clearly explain the technical solutions in the embodiments of the present application, make required in being described below to embodiment
Attached drawing is briefly described, it should be apparent that, the accompanying drawings in the following description is only some embodiments of the present application, for
For those of ordinary skill in the art, without having to pay creative labor, it can also be obtained according to these attached drawings
His attached drawing.
Fig. 1 is a kind of flow chart of daily record flow decentralized control method provided by the present application；
Fig. 2 is a kind of flow chart of daily record flow decentralized control method provided by the present application；
Fig. 3 is a kind of sub-process figure of daily record flow decentralized control method provided by the present application；
Fig. 4 is another sub-process figure of daily record flow decentralized control method provided by the present application；
Fig. 5 is a kind of logical construction schematic diagram of daily record flow scattered control system provided by the present application.
Specific implementation mode
Below in conjunction with the attached drawing in the embodiment of the present application, technical solutions in the embodiments of the present application carries out clear, complete
Site preparation describes, it is clear that described embodiments are only a part of embodiments of the present application, instead of all the embodiments.It is based on
Embodiment in the application, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall in the protection scope of this application.
The embodiment of the present application discloses a kind of daily record flow decentralized control method, passes through target journaling collector cluster service
Node receives the log request that target front end applications are sent；The target journaling collector cluster service node is asked from the daily record
It asks middle and obtains the daily record of the target front end applications, and the daily record of the target front end applications is counted, the result of counting
As the daily record total amount received；The target journaling collector cluster service node obtains the default of the target front end applications
Target journaling flow；The relatively more described daily record total amount received of the target journaling collector cluster service node is preset with described
The size of target journaling flow；It, will be described if the daily record total amount received is not more than the goal-selling daily record flow
Journal engine is written in the daily record of target front end applications；If the daily record total amount received is more than the goal-selling log stream
Amount, then abandon the daily record of the target front end applications, the log collection of each log concentrator cluster service node may be implemented
The control of flow.
Next daily record flow decentralized control method disclosed in the embodiment of the present application is introduced, refers to Fig. 1, it can be with
Including：
Step S11, target journaling collector cluster service node receives the log request that target front end applications are sent.
In the present embodiment, target front end applications can be by point-to-point direct-connected with target journaling collector cluster service node
Communication modes are communicated, and avoid the transfer of load-balancing device, and then save the cost of load-balancing device, Yi Jike
Performance bottleneck to break away from load-balancing device is shown.
Step S12, the described target journaling collector cluster service node in the log request before obtaining the target
The daily record of application is held, and the daily record of the target front end applications is counted, the result of counting is answered as the target front end
With the daily record total amount received on the target journaling collector cluster service node.
Step S13, the described target journaling collector cluster service node obtains the goal-selling of the target front end applications
Daily record flow.
Goal-selling daily record flow can be understood as：The daily record that target journaling collector cluster server node can be collected
Quantity upper limit value.
It should be noted that corresponding one of each log concentrator cluster service node is default in log concentrator cluster
Target journaling flow, and the corresponding goal-selling daily record flow of each log concentrator cluster service node is different.
Step S14, the relatively described daily record total amount received of the described target journaling collector cluster service node with it is described
The size of goal-selling daily record flow.
If the daily record total amount received is not more than the goal-selling daily record flow, S15 is thened follow the steps；If described
The daily record total amount received is more than the goal-selling daily record flow, thens follow the steps S16.
Step S15, journal engine is written into the daily record of the target front end applications.
Step S16, the daily record of the target front end applications is abandoned.
In this application, target journaling collector cluster independently compares the day received by each service node
The size of will total amount and the goal-selling daily record flow；If the daily record total amount received is not more than the goal-selling day
Then journal engine is written in the daily record of the target front end applications by will flow；If the daily record total amount received is more than described
Goal-selling daily record flow then abandons the daily record of the target front end applications, can with the daily record flow of control targe front end applications,
Therefore in log concentrator cluster, each node is all made of this mode, and respective control section daily record flow reaches daily record receipts
The purpose of the more service node decentralised control log collection flows of storage cluster, to realize that the entirety to daily record flow controls.
Further, it is default to be based on corresponding one of each log concentrator cluster service node in log concentrator cluster
Target journaling flow, and the corresponding goal-selling daily record flow of each log concentrator cluster service node is different,
Using the daily record flow decentralized control method of the application, target journaling collector cluster service node can be received with independent control daily record
The flow of collection avoids and has used stream between each each node of log concentrator cluster service that centralized control daily record flow is related to
Measure count synchronization, caused performance bottleneck problem.
In another embodiment of the application, to the determination process of the target journaling collector cluster service node into
Row is introduced, and is referred to Fig. 2, be may include：
Step S21, the affiliated node of the described target front end applications obtains log concentrator cluster from decentralized configuration center
The weight of service node list and each log concentrator cluster service node.
It is understood that the resources allocation ability of log concentrator cluster service node is higher, weight is bigger.
Step S22, the affiliated node of the described target front end applications utilizes load-balancing algorithm, the log concentrator cluster
The weight of service node list and each log concentrator cluster service node determines each log concentrator cluster
The node of daily record in service node for receiving the target front end applications, as the target journaling collector cluster service
Node.
It is understood that each node of target front end applications passes through asynchronous acquisition target journaling collector cluster service section
The weight of point list and each log concentrator cluster service node determines target journaling collector collection using load-balancing algorithm
Group's service node, is sent to the target journaling collector cluster service node, before realizing target by daily record point-to-pointly
Apply the soft load balancing of daily record flow in end.
Target journaling collector cluster service node can be understood as：Log collection flow is sufficient for target front end applications
Log collection node.
In another embodiment of the application, the goal-selling daily record flow is introduced, can specifically include：
The goal-selling daily record flow can be obtained by the decentralized configuration center configuration.
It is preset it should be noted that decentralized configuration center configures one for each log concentrator cluster service node
Target journaling flow, and the corresponding goal-selling daily record flow of each log concentrator cluster service node is different.
In the present embodiment, while the configuration process of the log concentrator cluster service node listing is introduced, referred to
Fig. 3 can specifically include：
Step S31, each log concentrator cluster, each log concentrator group are registered in the described decentralized configuration center
The weight of service node and each log concentrator cluster service node.
Step S32, the information of each log concentrator cluster service node is written at the described decentralized configuration center
List obtains the log concentrator cluster service node listing.
In another embodiment of the application, daily record is obtained from decentralized configuration center to the target front end applications and is received
The weight of storage cluster service node listing and each log concentrator cluster service node is introduced, and may include：
The target front end applications obtain log concentrator collection in a manner of asynchronous notifications, from the decentralized configuration center
The weight of group's service node list and each log concentrator cluster service node.
In a manner of asynchronous notifications, from the decentralized configuration center obtain log concentrator cluster service node listing and
The weight of each log concentrator cluster service node, can save Internet resources.
Content based on foregoing individual embodiments collects the target journaling in another embodiment of the application
The goal-selling daily record flow that device cluster service node obtains the target front end applications is introduced, and refers to Fig. 4, can wrap
It includes：
Step S41, the described target journaling collector cluster service node is matched in a manner of asynchronous notifications from the distribution
The center of setting obtains the goal-selling daily record total flow of each front end applications.
The target journaling collector cluster service node is obtained in a manner of asynchronous notifications from the decentralized configuration center
The goal-selling daily record total flow for taking each front end applications, can save Internet resources.
Step S42, the described target journaling collector cluster service node is according to the goal-selling daily record total flow and respectively
The ratio of the weight of a log concentrator cluster service node calculates each front end applications in the target journaling
Goal-selling daily record flow on collector cluster service node.
Step S43, the described target journaling collector cluster service node is by the goal-selling day of each front end applications
Will flow is stored in local cache.
Step S44, the described target journaling collector cluster service node in the local cache before obtaining the target
Hold the goal-selling daily record flow of application.
Next daily record flow scattered control system provided by the present application is introduced, refers to Fig. 5, daily record flow point
Scattered control system includes：Target journaling collector cluster service node 1, target journaling collector cluster service node 1 include：It connects
Receive module 11, counting module 12, the first acquisition module 13, comparison module 14, writing module 15 and discard module 16.
Receiving module 11, the log request for receiving the transmission of target front end applications.
Counting module 12, the daily record for obtaining the target front end applications from the log request, and to the mesh
The daily record of mark front end applications is counted, and the result of counting is as the target front end applications in the target journaling collector collection
The daily record total amount received on group's service node.
First acquisition module 13, the goal-selling daily record flow for obtaining the target front end applications.
Comparison module 14, the size of daily record total amount and the goal-selling daily record flow for being received described in comparison,
If the daily record total amount received is not more than the goal-selling daily record flow, writing module 15 is executed, if the reception
The daily record total amount arrived is more than the goal-selling daily record flow, then executes discard module 16.
Said write module 15, for journal engine to be written in the daily record of the target front end applications.
The discard module 16, the daily record for abandoning the target front end applications.
In the present embodiment, above-mentioned daily record flow scattered control system can also include：The affiliated node of target front end applications
With decentralized configuration center.
Correspondingly, the affiliated node of the target front end applications may include：
Second acquisition module, for from the decentralized configuration center obtain log concentrator cluster service node listing and
The weight of each log concentrator cluster service node；
Determining module, for utilizing load-balancing algorithm, the log concentrator cluster service node listing and each institute
The weight for stating log concentrator cluster service node determines in each log concentrator cluster service node for receiving institute
The node for stating the daily record of target front end applications, as the target journaling collector cluster service node 1.
In the present embodiment, the decentralized configuration center can be used for configuring the goal-selling daily record flow；
The decentralized configuration center may include：
Registration module, for registering each log concentrator cluster, each log concentrator group service node and each
The weight of a log concentrator cluster service node；
List Generating Module is obtained for list to be written in the information of each log concentrator cluster service node
The log concentrator cluster service node listing.
In the present embodiment, second acquisition module specifically can be used in a manner of asynchronous notifications, from the distribution
Configuration center obtains the weight of log concentrator cluster service node listing and each log concentrator cluster service node.
In the present embodiment, first acquisition module may include：
First acquisition unit, in a manner of asynchronous notifications, obtaining each front end from the decentralized configuration center and answering
Goal-selling daily record total flow, the log concentrator cluster service node listing and each log concentrator cluster
The weight of service node；
Computing unit, for according to the goal-selling daily record total flow and each log concentrator cluster service section
It is default on the target journaling collector cluster service node to calculate each front end applications for the ratio of the weight of point
Target journaling flow；
Storage unit, for the goal-selling daily record flow of each front end applications to be stored in local cache；
Second acquisition unit, the goal-selling log stream for obtaining the target front end applications from the local cache
Amount.
It should be noted that each embodiment in this specification is described in a progressive manner, each embodiment weight
Point explanation is all difference from other examples, and the same or similar parts between the embodiments can be referred to each other.
For device class embodiment, since it is basically similar to the method embodiment, so fairly simple, the related place ginseng of description
See the part explanation of embodiment of the method.
Finally, it is to be noted that, herein, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, the terms "include", "comprise" or its any other variant meaning
Covering non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only that
A little elements, but also include other elements that are not explicitly listed, or further include for this process, method, article or
The intrinsic element of equipment.In the absence of more restrictions, the element limited by sentence "including a ...", is not arranged
Except there is also other identical elements in the process, method, article or apparatus that includes the element.
For convenience of description, it is divided into various units when description apparatus above with function to describe respectively.Certainly, implementing this
The function of each unit is realized can in the same or multiple software and or hardware when application.
As seen through the above description of the embodiments, those skilled in the art can be understood that the application can
It is realized by the mode of software plus required general hardware platform.Based on this understanding, the technical solution essence of the application
On in other words the part that contributes to existing technology can be expressed in the form of software products, the computer software product
It can be stored in a storage medium, such as ROM/RAM, magnetic disc, CD, including some instructions are used so that a computer equipment
(can be personal computer, server either network equipment etc.) executes the certain of each embodiment of the application or embodiment
Method described in part.
A kind of daily record flow decentralized control method provided herein and system are described in detail above, herein
In apply specific case the principle and implementation of this application are described, the explanation of above example is only intended to sides
Assistant solves the present processes and its core concept；Meanwhile for those of ordinary skill in the art, the think of according to the application
Think, there will be changes in the specific implementation manner and application range, in conclusion the content of the present specification should not be construed as pair
The limitation of the application.
Claims (10)
1. a kind of daily record flow decentralized control method, which is characterized in that including：
Target journaling collector cluster service node receives the log request that target front end applications are sent；
The target journaling collector cluster service node obtains the daily record of the target front end applications from the log request,
And the daily record of the target front end applications is counted, the result of counting is as the target front end applications in the target day
The daily record total amount received on will collector cluster service node；
The target journaling collector cluster service node obtains the goal-selling daily record flow of the target front end applications；
The relatively more described daily record total amount received of the target journaling collector cluster service node and the goal-selling daily record
The size of flow；
If the daily record total amount received is not more than the goal-selling daily record flow, by the day of the target front end applications
Journal engine is written in will；
If the daily record total amount received is more than the goal-selling daily record flow, the day of the target front end applications is abandoned
Will.
2. according to the method described in claim 1, it is characterized in that, the determination of the target journaling collector cluster service node
Process, including：
The affiliated node of the target front end applications obtains log concentrator cluster service node listing from decentralized configuration center
And the weight of each log concentrator cluster service node；
The affiliated node of the target front end applications utilizes load-balancing algorithm, the log concentrator cluster service node listing
And the weight of each log concentrator cluster service node, it determines and is used in each log concentrator cluster service node
In the node for the daily record for receiving the target front end applications, as the target journaling collector cluster service node.
3. according to the method described in claim 2, it is characterized in that, the goal-selling daily record flow is by the decentralized configuration
Center configuration obtains；
The configuration process of the log concentrator cluster service node listing, including：
The decentralized configuration center register each log concentrator cluster, each log concentrator group service node and each
The weight of a log concentrator cluster service node；
List is written in the information of each log concentrator cluster service node by the decentralized configuration center, is obtained described
Log concentrator cluster service node listing.
4. according to the method described in claim 2, it is characterized in that, the target front end applications are obtained from decentralized configuration center
The weight of log concentrator cluster service node listing and each log concentrator cluster service node, including：
The target front end applications obtain log concentrator cluster clothes in a manner of asynchronous notifications, from the decentralized configuration center
The weight of business node listing and each log concentrator cluster service node.
5. according to the method described in claim 2, it is characterized in that, the target journaling collector cluster service node obtains institute
The goal-selling daily record flow of target front end applications is stated, including：
The target journaling collector cluster service node is obtained each in a manner of asynchronous notifications from the decentralized configuration center
Goal-selling daily record total flow, the log concentrator cluster service node listing and each daily record of a front end applications are received
The weight of storage cluster service node；
The target journaling collector cluster service node is received according to the goal-selling daily record total flow and each daily record
The ratio of the weight of storage cluster service node calculates each front end applications and is taken in the target journaling collector cluster
The goal-selling daily record flow being engaged on node；
The goal-selling daily record flow of each front end applications is stored in by the target journaling collector cluster service node
In local cache；
The target journaling collector cluster service node obtains the default of the target front end applications from the local cache
Target journaling flow.
6. a kind of daily record flow scattered control system, which is characterized in that including：Target journaling collector cluster service node, institute
Stating target journaling collector cluster service node includes：
Receiving module, the log request for receiving the transmission of target front end applications；
Counting module, the daily record for obtaining the target front end applications from the log request, and to the target front end
The daily record of application is counted, and the result of counting is as the target front end applications in the target journaling collector cluster service
The daily record total amount received on node；
First acquisition module, the goal-selling daily record flow for obtaining the target front end applications；
Comparison module, the size of daily record total amount and the goal-selling daily record flow for being received described in comparison, if described
The daily record total amount received is not more than the goal-selling daily record flow, then writing module is executed, if the daily record received
Total amount is more than the goal-selling daily record flow, then executes discard module；
Said write module, for journal engine to be written in the daily record of the target front end applications；
The discard module, the daily record for abandoning the target front end applications.
7. system according to claim 6, which is characterized in that the system also includes：The affiliated section of target front end applications
Point and decentralized configuration center, the affiliated node of the target front end applications include：
Second acquisition module, for obtaining log concentrator cluster service node listing and each from the decentralized configuration center
The weight of log concentrator cluster service node；
Determining module, for utilizing load-balancing algorithm, the log concentrator cluster service node listing and each day
The weight of will collector cluster service node determines in each log concentrator cluster service node for receiving the mesh
The node for marking the daily record of front end applications, as the target journaling collector cluster service node.
8. system according to claim 7, which is characterized in that the decentralized configuration center is for configuring the default mesh
Mark daily record flow；
The decentralized configuration center includes：
Registration module, for registering each log concentrator cluster, each log concentrator group service node and each institute
State the weight of log concentrator cluster service node；
List Generating Module obtains described for list to be written in the information of each log concentrator cluster service node
Log concentrator cluster service node listing.
9. system according to claim 7, which is characterized in that second acquisition module is specifically used for asynchronous notifications
Mode obtains log concentrator cluster service node listing and each log concentrator cluster clothes from the decentralized configuration center
The weight of business node.
10. system according to claim 7, which is characterized in that first acquisition module includes：
First acquisition unit, in a manner of asynchronous notifications, each front end applications to be obtained from the decentralized configuration center
Goal-selling daily record total flow, the log concentrator cluster service node listing and each log concentrator cluster service
The weight of node；
Computing unit, for according to the goal-selling daily record total flow and each log concentrator cluster service node
The ratio of weight calculates goal-selling of each front end applications on the target journaling collector cluster service node
Daily record flow；
Storage unit, for the goal-selling daily record flow of each front end applications to be stored in local cache；
Second acquisition unit, the goal-selling daily record flow for obtaining the target front end applications from the local cache.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810257323.7A CN108471387B (en) | 2018-03-27 | 2018-03-27 | Log flow decentralized control method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810257323.7A CN108471387B (en) | 2018-03-27 | 2018-03-27 | Log flow decentralized control method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108471387A true CN108471387A (en) | 2018-08-31 |
| CN108471387B CN108471387B (en) | 2022-10-21 |
Family
ID=63265896
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810257323.7A Active CN108471387B (en) | 2018-03-27 | 2018-03-27 | Log flow decentralized control method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108471387B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109327353A (en) * | 2018-09-29 | 2019-02-12 | 阿里巴巴集团控股有限公司 | Service traffics determine method, apparatus and electronic equipment |
| CN112231191A (en) * | 2020-10-23 | 2021-01-15 | 新华三信息安全技术有限公司 | Log collection method and device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101849384A (en) * | 2007-11-06 | 2010-09-29 | 朗讯科技公司 | Method for controlling load balance of network system, client, server and network system |
| CN103220354A (en) * | 2013-04-18 | 2013-07-24 | 广东宜通世纪科技股份有限公司 | Method for achieving load balancing of server cluster |
| CN103458013A (en) * | 2013-08-21 | 2013-12-18 | 成都云鹰科技有限公司 | Streaming media server cluster load balancing system and balancing method |
| CN103838659A (en) * | 2014-02-17 | 2014-06-04 | 大唐移动通信设备有限公司 | Method and device for controlling system logs |
| CN104023083A (en) * | 2014-06-23 | 2014-09-03 | 广东睿江科技有限公司 | Method and device for log collection cluster load balance |
| CN104092650A (en) * | 2013-12-04 | 2014-10-08 | 腾讯数码（天津）有限公司 | Service distributing request method and device |
| CN104158911A (en) * | 2014-09-01 | 2014-11-19 | 青岛海信电器股份有限公司 | Server cluster-oriented control method and system |
| CN105915646A (en) * | 2016-06-20 | 2016-08-31 | 飞天诚信科技股份有限公司 | Method and device for dispersing load of servers |
| CN106210120A (en) * | 2016-07-29 | 2016-12-07 | 广州仕邦人力资源有限公司 | A kind of recommendation method of server and device thereof |
| CN107426055A (en) * | 2017-07-31 | 2017-12-01 | 努比亚技术有限公司 | Abnormal flow monitoring method, device and computer-readable recording medium |
-
2018
- 2018-03-27 CN CN201810257323.7A patent/CN108471387B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101849384A (en) * | 2007-11-06 | 2010-09-29 | 朗讯科技公司 | Method for controlling load balance of network system, client, server and network system |
| CN103220354A (en) * | 2013-04-18 | 2013-07-24 | 广东宜通世纪科技股份有限公司 | Method for achieving load balancing of server cluster |
| CN103458013A (en) * | 2013-08-21 | 2013-12-18 | 成都云鹰科技有限公司 | Streaming media server cluster load balancing system and balancing method |
| CN104092650A (en) * | 2013-12-04 | 2014-10-08 | 腾讯数码（天津）有限公司 | Service distributing request method and device |
| CN103838659A (en) * | 2014-02-17 | 2014-06-04 | 大唐移动通信设备有限公司 | Method and device for controlling system logs |
| CN104023083A (en) * | 2014-06-23 | 2014-09-03 | 广东睿江科技有限公司 | Method and device for log collection cluster load balance |
| CN104158911A (en) * | 2014-09-01 | 2014-11-19 | 青岛海信电器股份有限公司 | Server cluster-oriented control method and system |
| CN105915646A (en) * | 2016-06-20 | 2016-08-31 | 飞天诚信科技股份有限公司 | Method and device for dispersing load of servers |
| CN106210120A (en) * | 2016-07-29 | 2016-12-07 | 广州仕邦人力资源有限公司 | A kind of recommendation method of server and device thereof |
| CN107426055A (en) * | 2017-07-31 | 2017-12-01 | 努比亚技术有限公司 | Abnormal flow monitoring method, device and computer-readable recording medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109327353A (en) * | 2018-09-29 | 2019-02-12 | 阿里巴巴集团控股有限公司 | Service traffics determine method, apparatus and electronic equipment |
| CN109327353B (en) * | 2018-09-29 | 2022-01-11 | 创新先进技术有限公司 | Service flow determination method and device and electronic equipment |
| CN112231191A (en) * | 2020-10-23 | 2021-01-15 | 新华三信息安全技术有限公司 | Log collection method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108471387B (en) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109618002A (en) | A kind of micro services gateway optimization method, device and storage medium | |
| JP6126099B2 (en) | Marketplace for timely event data distribution | |
| US7130901B2 (en) | Network service provider platform for supporting usage sensitive billing and operation services | |
| CN109981416A (en) | A kind of block chain method for testing performance and system | |
| CN106790718A (en) | Service call link analysis method and system | |
| KR20170106648A (en) | High-capacity network data processing techniques | |
| US8176200B2 (en) | Distributed aggregation on an overlay network | |
| CN101605092A (en) | A kind of content-based SiteServer LBS | |
| CN108769271A (en) | Method, apparatus, storage medium and the terminal device of load balancing | |
| CN103995807B (en) | Magnanimity data query and the method for after-treatment under a kind of framework based on Web | |
| JP2013168139A (en) | Load balancing device, load balancing method and hierarchized data center system | |
| CN104023083A (en) | Method and device for log collection cluster load balance | |
| CN108471387A (en) | A kind of daily record flow decentralized control method and system | |
| CN103795575B (en) | A kind of system monitoring method towards multiple data centers | |
| CN106341312A (en) | Social contact information display method, system and server | |
| CN109032800A (en) | A kind of load equilibration scheduling method, load balancer, server and system | |
| CN110457337A (en) | Link aggregation method, system and equipment | |
| CN101710412A (en) | Method and system for processing quota data | |
| US20080256079A1 (en) | Load-based technique to balance data sources to data consumers | |
| CN108958939A (en) | Distribution method, device and the server of Service Source | |
| CN101399713B (en) | Method for measuring proximity of network node | |
| CN110012050A (en) | Message Processing, storage method, apparatus and system | |
| CN110769023B (en) | Point-to-point content distribution network system based on intelligent home gateway | |
| CN106878128A (en) | A kind of collocation method and device of identifier receiving filter | |
| CN109981795A (en) | Resource request dispatching method and device |
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 |