CN108134702B - Data acquisition unit fault solving method - Google Patents

Data acquisition unit fault solving method Download PDF

Info

Publication number
CN108134702B
CN108134702B CN201711428544.8A CN201711428544A CN108134702B CN 108134702 B CN108134702 B CN 108134702B CN 201711428544 A CN201711428544 A CN 201711428544A CN 108134702 B CN108134702 B CN 108134702B
Authority
CN
China
Prior art keywords
data
data acquisition
control center
acquisition unit
fault
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
CN201711428544.8A
Other languages
Chinese (zh)
Other versions
CN108134702A (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.)
Beijing Kelai Data Analysis Co ltd
Original Assignee
Beijing Kelai Data Analysis 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 Beijing Kelai Data Analysis Co ltd filed Critical Beijing Kelai Data Analysis Co ltd
Priority to CN201711428544.8A priority Critical patent/CN108134702B/en
Publication of CN108134702A publication Critical patent/CN108134702A/en
Application granted granted Critical
Publication of CN108134702B publication Critical patent/CN108134702B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0677Localisation of faults
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/069Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/28Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources

Abstract

The invention provides a method for solving the fault of a data acquisition unit, which comprises the following steps that after the data acquisition unit is started, if the data acquisition unit has a fault; the control center elects another data acquisition unit in an online state to carry out fault treatment; the control center issues a fault processing notice to the fault processing data acquisition unit for fault processing, and the fault processing data acquisition unit processes the fault after receiving the fault processing notice: the fault processing data acquisition unit inquires data sources linked with the fault data acquisition unit and distributes the data sources to the data acquisition unit in a normal working state for data acquisition; after the distribution is finished, the distribution mode of the data source is sent to a control center; and the data acquisition unit regularly detects whether a data source is newly distributed in the database, and if so, a data acquisition thread is started to acquire data. The invention solves the problem that the data acquisition is seriously lagged and even the data is lost after the single point of failure of the data acquisition device.

Description

Data acquisition unit fault solving method
Technical Field
The invention relates to a data collector fault solving method, in particular to a collector fault solving method suitable for a pull-type data collector.
Background
At present, a pull-type data acquisition unit (a pull-type data acquisition unit refers to a data acquisition unit actively pulling data to a data source, and the pull-type data acquisition unit can access a database of the data source or pull the data through other communication modes.) most of failures cannot be automatically recovered or the data source cannot be replaced by other data acquisition units, so that serious delay of data acquisition and even data loss and other consequences are caused.
Disclosure of Invention
The invention aims to solve the technical problem of providing a method for solving the problems of serious delay of data acquisition, even data loss and the like after single-point failure of a data acquisition device;
the second technical problem to be solved by the invention is an automatic balancing method for automatically balancing the collection work of the data source of the data collector to other collectors on the basis of ensuring the single-point fault problem of the data collector;
the third technical problem to be solved by the invention is to provide a method for conveniently checking the fault problem cause.
The technical scheme adopted by the invention is as follows: a method for solving the fault of a data collector comprises the following specific steps: after the data acquisition device is started, linking the corresponding data source for data acquisition, updating the heartbeat time linked with the data source to the database at intervals of a set time threshold T1, and indicating that the data acquisition device normally works as long as the heartbeat time does not exceed the set time distance threshold T2;
meanwhile, the data collector and the control center establish long TCP connection in a socket communication mode, after the connection is established, the data collector logs in the control center, the ID of the data collector is uploaded during logging in, all data source IDs linked with the data collector are reported to the control center, after the logging is successful, the data collector reports the heartbeat time of the operation of the data collector to the control center every set time threshold T3, and as long as the heartbeat time does not exceed the set time distance threshold T4, the data collector works normally and the network of the control center and the data collector is smooth;
if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link with the control center is disconnected, the data collector is possibly in fault; the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for carrying out fault processing;
the control center issues a fault processing notice to the fault processing data acquisition unit for fault processing, and the fault processing data acquisition unit performs fault processing after receiving the fault processing notice: the fault processing data acquisition unit inquires data sources linked with the fault data acquisition unit with faults from a corresponding database, and distributes the data sources to the data acquisition units in normal working state for data acquisition; after the distribution is completed, the fault processing data acquisition unit reports that the fault is processed to the control center and sends the distribution mode of the data source to the control center;
and the data acquisition unit which is allocated with the data source detects whether a data source which needs to be acquired is newly allocated in the database at regular time, and if the newly allocated data source is found, a data acquisition thread is started to acquire the data.
When the fault processing data collector is elected, only one data collector can be elected from the data collectors in the online normal working state according to the set election rule to be used as the fault processing data collector.
The distribution work of the data source to be distributed is only to update the corresponding relation between the data acquisition units and the data source in the corresponding database, so that after the distribution is completed, each online data acquisition unit inquires the data source to be acquired, starts a data acquisition thread corresponding to the data source to be acquired, and completes the data source acquisition work.
The scheme of the invention solves the problems of serious delay of data acquisition, even data loss and the like after single-point failure of the data acquisition device.
The method further comprises the following steps: and establishing a data acquisition unit group, and uploading the group ID of the data acquisition unit when the data acquisition unit logs in the control center. And establishing a data collector group to realize the grouping management of the data collectors.
The method further comprises the following steps: when the data collector group is established, for data sources of the same service type, the data collectors are established in the same group, so that the grouping responsibility is clear.
The method further comprises the following steps: each data collector group corresponds to one database, and grouping management is facilitated.
The method further comprises the following steps: and the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for fault processing, and the elected fault processing data acquisition unit and the data acquisition unit with the fault are in the same group.
The method further comprises the following steps: and the control center elects another data acquisition device in an online state as a fault processing data acquisition device for fault processing, and the elected fault processing data acquisition device is the data acquisition device with the largest or smallest ID number in the data acquisition devices in the online state.
The method further comprises the following steps: the control center sends a fault processing notice to the fault processing data collector for fault processing, and the fault processing data collector carries out fault processing after receiving the fault processing notice; at the moment, if the fault data collector logs in the control center, a locking mechanism is adopted for processing, and the logging of the logged data collector is refused; and after receiving the distribution mode of the data source, the control center releases the login lock, and at the moment, the data acquisition device needing to login can log in the control center.
The control center informs the logged data collector that the data collector can not log in at present, the data collector elected at present carries out fault processing, and the data collector can log in until the fault processing is finished, so that the consistency of the state is ensured.
The method further comprises the following steps: the control center records logs to a corresponding database, and the content of the logs comprises failure occurrence time, ID of a failed data collector and whether to confirm processing; and after receiving the distribution mode of the data source, the control center records the distribution log to a corresponding database, so that the fault problem cause is conveniently checked.
The method further comprises the following steps: if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link is disconnected with the control center, before the control center elects other data collectors to process the fault, fault confirmation is carried out, and the specific confirmation method comprises the following steps: selecting a data acquisition unit in an online state and working normally, inquiring whether a heartbeat time linked with a data source exists in a certain data acquisition unit in a database within T2 time, if so, indicating that the certain data acquisition unit is still in the normal working state, waiting for the certain data acquisition unit to automatically reconnect a control center so as to recover the communication with the control center, and simultaneously reporting that the certain data acquisition unit is still in the working state to the control center by the selected data acquisition unit; if not, it indicates that the certain data collector actually fails.
The method further comprises the following steps: when the fault processing data acquisition device processes the fault, all the data acquisition devices in the working state are inquired at the same time, and the data sources to be allocated are averagely allocated to the inquired data acquisition devices in the working state according to the average allocation principle, so that the balanced allocation of the resources is realized.
Compared with the prior art, the invention has the beneficial effects that:
1. the problem of single-point failure of the pull-type data acquisition unit is solved;
2. the scheme is well solved for the automatic balanced distribution of the acquired data sources after a certain data acquisition device fails;
3. a locking mechanism is introduced, so that the condition that the fault data acquisition unit cannot be reconnected when fault processing is carried out is ensured, and the consistency of the state is ensured;
4. the heartbeat mechanism of the data acquisition device and the data source ensures that only one acquisition device can be linked with one data source at the same time;
5. a group mechanism is introduced, namely, the data acquisition devices in the same group can be ensured to carry out resource balance and fault processing;
6. the control center is used as a core component of the data acquisition unit, uniformly discovers faults and newly adds acquisition units, introduces an election mechanism, and selects the only acquisition unit for fault processing and resource balancing;
7. the heartbeat mechanisms of the control center and the data acquisition unit can ensure that faults can be found in time;
8. the control center records the log of fault occurrence and processing, and can provide reference for a system administrator to perform fault troubleshooting.
Drawings
Fig. 1 is a schematic diagram of an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Any feature disclosed in this specification (including any accompanying drawings) may be replaced by alternative features serving equivalent or similar purposes, unless expressly stated otherwise. That is, unless expressly stated otherwise, each feature is only an example of a generic series of equivalent or similar features.
Detailed description of the preferred embodiment 1
As shown in fig. 1, a method for solving a failure of a data collector specifically includes: after the data acquisition device is started, linking the corresponding data source for data acquisition, updating the heartbeat time linked with the data source to the database at intervals of a set time threshold T1, and indicating that the data acquisition device normally works as long as the heartbeat time does not exceed the set time distance threshold T2;
meanwhile, the data collector and the control center establish long TCP connection in a socket communication mode, after the connection is established, the data collector logs in the control center, the ID of the data collector is uploaded during logging in, all data source IDs linked with the data collector are reported to the control center, after the logging is successful, the data collector reports the heartbeat time of the operation of the data collector to the control center every set time threshold T3, and as long as the heartbeat time does not exceed the set time distance threshold T4, the data collector works normally and the network of the control center and the data collector is smooth;
if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link with the control center is disconnected, the data collector is possibly in fault; the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for carrying out fault processing;
the control center issues a fault processing notice to the fault processing data acquisition unit for fault processing, and the fault processing data acquisition unit performs fault processing after receiving the fault processing notice: the fault processing data acquisition unit inquires data sources linked with the fault data acquisition unit with faults from a corresponding database, and distributes the data sources to the data acquisition units in normal working state for data acquisition; after the distribution is completed, the fault processing data acquisition unit reports that the fault is processed to the control center and sends the distribution mode of the data source to the control center;
and the data acquisition unit which is allocated with the data source detects whether a data source which needs to be acquired is newly allocated in the database at regular time, and if the newly allocated data source is found, a data acquisition thread is started to acquire the data.
The T1 and T3 can be set to a time of 1 second to 3 seconds, and the T2 and T4 can be set to a time of 3 seconds to 5 seconds, and the specific setting is set according to the actual demand and actual situation of the user.
Specific example 2
On the basis of the specific embodiment 1, the method further includes: and establishing a data acquisition unit group, and uploading the group ID of the data acquisition unit when the data acquisition unit logs in the control center. And establishing a data collector group to realize the grouping management of the data collectors. As shown in fig. 1, in this embodiment, the data collectors are divided into g1 group and g2 group, where g1 group includes data collectors c1, c2 and c3, and data collection is performed on data sources s1 to s 6; the group g2 includes data collectors c4, c5 and c6, which collect data from data sources s7 to s 9.
Specific example 3
On the basis of the specific embodiment 2, the method further includes: when the data collector group is established, for data sources of the same service type, the data collectors are established in the same group, so that the grouping responsibility is clear. As shown in fig. 1, in this embodiment, the data sources collected by the data collector of group g1 and the data collector of group g2 are data sources of two different traffic types. The data collector of the group g1 can only be linked with the data sources s1 to s6 corresponding to the group g 1; the data collector of group g2 can only link with the data sources s7 to s9 corresponding to group g 2.
Specific example 4
On the basis of the specific embodiment 2 or 3, the method further includes: each data collector group corresponds to one database, and grouping management is facilitated. As shown in FIG. 1, in this particular embodiment, the group g1 corresponds to database db1, and the group g2 corresponds to database db 2.
Specific example 5
On the basis of one of specific embodiments 2 to 4, the method further includes: and the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for fault processing, and the elected fault processing data acquisition unit and the data acquisition unit with the fault are in the same group. As shown in fig. 1, if the data collector in group g1 fails, the failure handling data collector can only be selected from group g 1; if the data collector in the group g2 fails, the failure processing data collector can be selected from the group g 2.
Specific example 6
On the basis of one of specific embodiments 1 to 5, the method further includes: the control center elects other data collectors in an online state as fault processing data collectors for fault processing, the elected fault processing data collectors are the data collectors with the largest or smallest ID numbers in the data collectors in the online state, and the elected fault processing data collectors are used as election rules, and the only one data collector is elected from the data collectors in the online normal working state as the fault processing data collector. Taking c2 data collectors in the group g1 as fault data collectors as an example, if the election rule is the data collector with the largest ID number in the data collectors in the online state, electing c3 as a fault processing data collector; and if the election rule is the data collector with the smallest ID number in the data collectors in the online state, the election c1 is the fault handling data collector.
Specific example 7
On the basis of one of specific embodiments 1 to 6, the method further includes: the control center sends a fault processing notice to the fault processing data collector for fault processing, and the fault processing data collector carries out fault processing after receiving the fault processing notice; at the moment, if the fault data collector logs in the control center, a locking mechanism is adopted for processing, and the logging of the logged data collector is refused; and after receiving the distribution mode of the data source, the control center releases the login lock, and at the moment, the data acquisition device needing to login can log in the control center.
As shown in fig. 1, taking the c2 data collector in the group g1 as a failure data collector and taking the data collector with the smallest ID number in the data collectors with the online election rule as an example, the c1 is taken as a failure handling data collector. If the control center issues a fault processing notice to the data collector c1 for fault processing, the data collector c1 carries out fault processing after receiving the fault processing notice; at the moment, if the c2 fault recovery needs to log in the control center, a locking mechanism is adopted for processing, and the log-in of the data collector c2 is refused; after the control center receives the allocation mode of the data source, the login lock is released, and at the moment, the data collector c2 can log in the control center, so that the consistency of the state is ensured.
Specific example 8
On the basis of one of specific embodiments 1 to 7, the method further includes: the control center records logs to a corresponding database, and the content of the logs comprises failure occurrence time, ID of a failed data collector and whether to confirm processing; and after receiving the distribution mode of the data source, the control center records the distribution log to a corresponding database. As shown in fig. 1, in the present embodiment, the control center logs to the logging database db 3.
Specific example 9
On the basis of one of specific embodiments 1 to 8, the method further includes: if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link is disconnected with the control center, before the control center elects other data collectors to process the fault, fault confirmation is carried out, and the specific confirmation method comprises the following steps: selecting a data acquisition unit in an online state and working normally, inquiring whether a heartbeat time linked with a data source exists in a certain data acquisition unit in a database within T2 time, if so, indicating that the certain data acquisition unit is still in the normal working state, waiting for the certain data acquisition unit to automatically reconnect a control center so as to recover the communication with the control center, and simultaneously reporting that the certain data acquisition unit is still in the working state to the control center by the selected data acquisition unit; if not, it indicates that the certain data collector actually fails.
Detailed description of example 10
On the basis of one of specific embodiments 1 to 9, the method further includes: when the fault processing data acquisition device processes the fault, all the data acquisition devices in the working state are inquired at the same time, and the data sources to be allocated are averagely allocated to the inquired data acquisition devices in the working state according to the average allocation principle, so that the balanced allocation of the resources is realized. Taking c2 data collector in the group g1 as a fault data collector, and taking the data collector with the smallest ID number in the data collectors with the online selection rule as an example, c1 is taken as a fault processing data collector. If the control center issues a fault processing notice to the data collector c1 for fault processing, the data collector c1 carries out fault processing after receiving the fault processing notice. If data collector c2 does fail, data collector c1 queries data sources s3 and s4 linked with data collector c2 from database db1, and simultaneously queries data collectors c1 and c3 currently in a normal working state, and data collectors c1 and c3 can each allocate one more data source according to an average allocation principle (the maximum number of data sources that can be allocated to each data collector: cail (6/2) =3, the cail function is an upward integer function, 6 refers to the number of all data sources, and 2 refers to the number of data collectors in normal working state), so that data sources s3 and s4 are allocated to data collectors c1 and c3, respectively. The distribution work is only to update the corresponding relation between the data collector and the data source in the database db1, the data collector c1 and the data collector c3 regularly monitor whether the data source needing to be collected is newly distributed in the database db1, and if the newly distributed data source is found, the data collection thread is started to collect the data.

Claims (10)

1. A method for solving the fault of a data collector comprises the following specific steps: after the data acquisition device is started, linking the corresponding data source for data acquisition, updating the heartbeat time linked with the data source to the database at intervals of a set time threshold T1, and indicating that the data acquisition device normally works as long as the heartbeat time does not exceed the set time distance threshold T2;
meanwhile, the data collector and the control center establish long TCP connection in a socket communication mode, after the connection is established, the data collector logs in the control center, the ID of the data collector is uploaded during logging in, all data source IDs linked with the data collector are reported to the control center, after the logging is successful, the data collector reports the heartbeat time of the operation of the data collector to the control center every set time threshold T3, and as long as the heartbeat time does not exceed the set time distance threshold T4, the data collector works normally and the network of the control center and the data collector is smooth;
if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link with the control center is disconnected, the data collector is possibly in fault; the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for carrying out fault processing;
the control center issues a fault processing notice to the fault processing data acquisition unit for fault processing, and the fault processing data acquisition unit performs fault processing after receiving the fault processing notice: the fault processing data acquisition unit inquires data sources linked with the fault data acquisition unit with faults from a corresponding database, and distributes the data sources to the data acquisition units in normal working state for data acquisition; after the distribution is completed, the fault processing data acquisition unit reports that the fault is processed to the control center and sends the distribution mode of the data source to the control center;
and the data acquisition unit which is allocated with the data source detects whether a data source which needs to be acquired is newly allocated in the database at regular time, and if the newly allocated data source is found, a data acquisition thread is started to acquire the data.
2. The data collector failure resolution method of claim 1, further comprising: and establishing a data acquisition unit group, and uploading the group ID of the data acquisition unit when the data acquisition unit logs in the control center.
3. The data collector failure resolution method of claim 2, further comprising: when the data collector group is established, the data collectors of the data sources with the same service type are established in the same group.
4. The data collector failure resolution method of claim 2 or 3, the method further comprising: each data collector group corresponds to a database.
5. The data collector failure resolution method of claim 4, further comprising: and the control center elects another data acquisition unit in an online state as a fault processing data acquisition unit for fault processing, and the elected fault processing data acquisition unit and the fault data acquisition unit with the fault are in the same group.
6. The data collector failure resolution method of claim 5, further comprising: and the control center elects another data acquisition device in an online state as a fault processing data acquisition device for fault processing, and the elected fault processing data acquisition device is the data acquisition device with the largest or smallest ID number in the data acquisition devices in the online state.
7. The data collector failure resolution method of claim 1, further comprising: the control center sends a fault processing notice to the fault processing data collector for fault processing, and the fault processing data collector carries out fault processing after receiving the fault processing notice; at the moment, if the fault data collector logs in the control center, a locking mechanism is adopted for processing, and the logging of the logged data collector is refused; and after receiving the distribution mode of the data source, the control center releases the login lock, and at the moment, the data acquisition device needing to login can log in the control center.
8. The data collector failure resolution method of claim 1, further comprising: the control center records logs to a corresponding database, and the content of the logs comprises failure occurrence time, ID of a failed data collector and whether to confirm processing; and after receiving the distribution mode of the data source, the control center records the distribution log to a corresponding database.
9. The data collector failure resolution method of claim 8, further comprising: if the control center finds that a certain data collector does not report the heartbeat time of the operation of the data collector within the time T4 or the long link is disconnected with the control center, before the control center elects other data collectors to process the fault, fault confirmation is carried out, and the specific confirmation method comprises the following steps: electing a normally working data collector in an online state, inquiring whether a heartbeat time linked with a data source exists in a certain data collector in a database within T2 time, if so, waiting for the certain data collector to automatically reconnect a control center so as to recover the communication with the control center, and simultaneously reporting that the certain data collector is still in a working state to the control center by the elected data collector; if not, it indicates that the certain data collector actually fails.
10. The data collector failure resolution method of claim 8 or 9, the method further comprising: when the fault processing data acquisition device processes fault processing, all the data acquisition devices in the current working state are inquired at the same time, and the data sources needing to be distributed are averagely distributed to the inquired data acquisition devices in the current working state according to an average distribution principle.
CN201711428544.8A 2017-12-26 2017-12-26 Data acquisition unit fault solving method Active CN108134702B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711428544.8A CN108134702B (en) 2017-12-26 2017-12-26 Data acquisition unit fault solving method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711428544.8A CN108134702B (en) 2017-12-26 2017-12-26 Data acquisition unit fault solving method

Publications (2)

Publication Number Publication Date
CN108134702A CN108134702A (en) 2018-06-08
CN108134702B true CN108134702B (en) 2021-01-01

Family

ID=62392961

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711428544.8A Active CN108134702B (en) 2017-12-26 2017-12-26 Data acquisition unit fault solving method

Country Status (1)

Country Link
CN (1) CN108134702B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109660428B (en) * 2018-12-24 2020-08-28 航天信息股份有限公司 High availability cluster system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179432A (en) * 2007-12-13 2008-05-14 浪潮电子信息产业股份有限公司 Method of implementing high availability of system in multi-machine surroundings
CN102739775A (en) * 2012-05-29 2012-10-17 宁波东冠科技有限公司 Method for monitoring and managing Internet of Things data acquisition server cluster
CN103716182A (en) * 2013-12-12 2014-04-09 中国科学院信息工程研究所 Failure detection and fault tolerance method and failure detection and fault tolerance system for real-time cloud platform
CN105791031A (en) * 2016-05-04 2016-07-20 重庆世纪之光科技实业有限公司 Data acquisition and transmitting method
CN106911519A (en) * 2017-04-10 2017-06-30 北京搜狐新媒体信息技术有限公司 A kind of data acquisition monitoring method and device
CN107247729A (en) * 2017-05-03 2017-10-13 中国银联股份有限公司 A kind of document handling method and device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179432A (en) * 2007-12-13 2008-05-14 浪潮电子信息产业股份有限公司 Method of implementing high availability of system in multi-machine surroundings
CN102739775A (en) * 2012-05-29 2012-10-17 宁波东冠科技有限公司 Method for monitoring and managing Internet of Things data acquisition server cluster
CN103716182A (en) * 2013-12-12 2014-04-09 中国科学院信息工程研究所 Failure detection and fault tolerance method and failure detection and fault tolerance system for real-time cloud platform
CN105791031A (en) * 2016-05-04 2016-07-20 重庆世纪之光科技实业有限公司 Data acquisition and transmitting method
CN106911519A (en) * 2017-04-10 2017-06-30 北京搜狐新媒体信息技术有限公司 A kind of data acquisition monitoring method and device
CN107247729A (en) * 2017-05-03 2017-10-13 中国银联股份有限公司 A kind of document handling method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于Storm的实时大数据分析系统的研究与实现;龙少杭;《中国优秀硕士学位论文全文数据库信息科技辑(月刊)》;20160315;I138-4328 *

Also Published As

Publication number Publication date
CN108134702A (en) 2018-06-08

Similar Documents

Publication Publication Date Title
CN102739775B (en) The monitoring of internet of things data acquisition server cluster and management method
CN105915405A (en) Large-scale cluster node performance monitoring system
CN107947960A (en) The method for pushing and system of configuration information, the method for reseptance and system of configuration information
CN104618255B (en) A kind of front-collection service system and data processing method
CN112073265A (en) Internet of things monitoring method and system based on distributed edge computing
CN104717077B (en) A kind of method, apparatus and system for managing data center
CN112637368B (en) Distributed industrial data acquisition system and method
CN109391691B (en) Method and related device for recovering NAS service under single-node fault
CN105554099A (en) Method and device for balancing load of acquisition servers
CN101753451A (en) Network load balance track traffic signal equipment state collection method and device
CN108810853A (en) A kind of system and method based on the upgrading of 4G network wireless sensor automatic remotes
CN104363278A (en) Mass terminal communication access system
CN108134702B (en) Data acquisition unit fault solving method
CN109151082A (en) A kind of multi-connection method for building up, device and system
DE112020000145T5 (en) Redundant network IP intelligent switching method and system based on redundant computer
CN111949404A (en) Method and device for adjusting server load and related equipment
CN106230622A (en) A kind of cluster implementation method and device
CN106452899B (en) A kind of distributed data digging system and method
CN108234623B (en) Automatic balance management method for data acquisition link of distribution network master station
US20160164719A1 (en) Fault tolerance method for distributed stream processing system
CN108667640B (en) Communication method and device, and network access system
CN107942888B (en) Work control method after fault recovery of data acquisition device
CN109067600A (en) A kind of private clound management platform system and its task processing method
CN106254150A (en) Network failure processing method and system
CN101877714A (en) Integrated server

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