CN110971872B - Video image information acquisition method based on distributed cluster - Google Patents
Video image information acquisition method based on distributed cluster Download PDFInfo
- Publication number
- CN110971872B CN110971872B CN201911114002.2A CN201911114002A CN110971872B CN 110971872 B CN110971872 B CN 110971872B CN 201911114002 A CN201911114002 A CN 201911114002A CN 110971872 B CN110971872 B CN 110971872B
- Authority
- CN
- China
- Prior art keywords
- node
- cluster
- interface
- nodes
- management
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N5/00—Details of television systems
- H04N5/76—Television signal recording
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a video image information acquisition method based on a distributed cluster, which comprises the following steps: step 1, data in an acquisition device/system are interconnected with a private network, the data are interconnected and stored in a cluster area through the private network, and the data stored in the cluster area are provided to a service information system through the private network again; step 2, the cluster area is composed of a cluster management layer and an interface service layer, and the cluster management layer of the cluster area provides a fixed IP port for the private network; step 3, a cluster management layer in the cluster area is provided with a main management node and a standby management node; the main management node and the standby management node in the cluster management layer are connected with the same and independent IP port to provide data transmission service; step 4, the interface service layer takes Nginx as a plurality of independent stateless interface nodes, and the interface nodes are connected with a main management node and a standby management node in the cluster management layer in an HTTP long connection mode; step 5, interface nodes in the interface service layer are respectively interconnected with the information queue/cache and the cloud storage service; and 6, interconnecting the main service clusters by the information queue/cache region, and interconnecting the main service clusters with the cloud storage service. By adopting the video image information acquisition method based on the distributed cluster, the video and picture information processing capacity is improved, and the cost and time are saved.
Description
Technical Field
The invention relates to the field of network security, in particular to a video image information acquisition method based on a distributed cluster.
Background
With the development of deep learning, intelligent video analysis and big data technology, deep mining and analysis of massive video image data have been conditioned, and the data need to be supported by a database for centrally storing video images. The video image database stores video clip files and image files from the intelligent acquisition equipment and objects such as personnel, vehicles, articles, scenes, video image labels and the like contained in the video clip files and the image files, and provides data service interfaces for all business systems to support various application requirements. The video image database can receive tens of millions to hundreds of millions of data each day, and the data are crucial to the business development of each application system.
For example, the Chinese invention patent: 201910134543.5, discloses a big data based information collection method, the big data based information collection system includes: the system comprises a data source module, a data transmission module, a central control module, a retrieval module, an information integration module, an information management module, a big data analysis module, a balance module, a cloud storage module and a display module. According to the method, the analysis result obtained by the big data analysis module is stored in the analysis result table of the distributed database, and the big data does not need to be obtained from massive big data in the distributed database, so that the time consumption is short and the method is easy to realize; meanwhile, the balancing module dynamically adjusts the network bandwidth of data balance according to the data balance strategy and the load and performance data of the big data cluster, and restarts the data balance program, so that the efficiency and the elasticity of cluster data balance can be improved while the normal data production of the cluster is ensured.
For another example, the Chinese invention patent: 201710373026.4, discloses a data acquisition system based on distributed cluster, the system includes a main acquisition node, a data analysis module and a plurality of sub acquisition nodes; the main acquisition node is connected with a plurality of the sub acquisition nodes, the sub acquisition nodes are used for acquiring data, and the main acquisition node is used for receiving the data acquired by each sub acquisition node; the data analysis module is used for respectively calculating the change rate of the data acquired by each sub-acquisition node and adjusting the data acquisition frequency of each sub-acquisition node according to the change rate; the system disclosed by the invention can adjust the data acquisition frequency of each sub-acquisition node through the change rate, so that the acquisition frequency of each sub-acquisition node is adaptive to the change rate of the acquired data.
Based on the above-mentioned shortcomings of the prior art, the data amount of the database, which is continuously and stably received and stored every day, up to several tens of millions of pieces of video image information and structured description information, cannot be solved.
Disclosure of Invention
The data volume of the database, which is continuously and stably received and stored every day, can not be solved by the prior art, and the data volume is up to tens of millions to hundreds of millions of pieces of video image information and structural description information.
The invention aims to provide a video image information acquisition method based on a distributed cluster, which comprises the following steps:
step 1, data in an acquisition device/system are interconnected with a private network, the data are interconnected and stored in a cluster area through the private network, and the data stored in the cluster area are provided to a service information system through the private network again;
step 2, the cluster area is composed of a cluster management layer and an interface service layer, and the cluster management layer of the cluster area provides a fixed IP port for the private network;
step 3, a cluster management layer in the cluster area is provided with a main management node and a standby management node; the main management node and the standby management node in the cluster management layer are connected with the same and independent IP port to provide data transmission service;
step 4, the interface service layer takes Nginx as a plurality of independent stateless interface nodes, and the interface nodes are connected with a main management node and a standby management node in the cluster management layer in an HTTP long connection mode;
step 5, interface nodes in the interface service layer are respectively interconnected with the information queue/cache and the cloud storage service;
and 6, interconnecting the main service clusters through the information queues/caches, and interconnecting the main service clusters with the cloud storage service.
Further, if the main management node in step 3 fails, the standby management node starts switching to continue providing service, and the time for starting and switching the main management node and the standby management node to switch each other is 0.1-2S according to the configured priority.
Further, the cluster management layer in step 3 is used as an entrance for all external private network requests, the cluster management layer needs to provide a fixed IP to the outside, and when the primary management node fails, the standby management node continues to use the same IP to provide services to the outside.
Further, the cluster management layer in step 3 realizes high availability of the management nodes in a manner of master management nodes and standby management nodes, and realizes failover and automatic recovery of the master management nodes and the standby management nodes by using keepalive, and the failover and automatic recovery steps are as follows:
step 3.1, a Virtual Routing Redundancy Protocol (VRRP) used by keepalive shares a virtual IP among a router group, a main node and a plurality of standby nodes are arranged in the router group, the main node binds the external IP to a machine of the main node, a multicast packet is periodically sent, the standby nodes mark the main node as abnormal when the standby nodes cannot receive the multicast packet, and one standby node is selected as the main node according to the configured priority to keep the continuity and reliability of communication and eliminate the single node fault;
step 3.2, the keepalive regularly executes scripts specified by the user, and health check scripts are edited on machines where the main management nodes and the standby management nodes are located in the cluster management layer, so that the migration of faults of the main management nodes and the standby management nodes is realized, and the health check scripts execute the following steps:
step 3.2.1, running a linux command to check the management node;
step 3.2.2, checking the management node in the cluster management layer by the linux command, if the management node is abnormal, automatically restarting the management node, waiting for 15-30 milliseconds, checking whether the restarted management node is normal again, displaying a normal checking result, and finishing the linux command;
step 3.2.3, if the check result of the management node after automatic restart is abnormal, the linux command judges that the management node is in fault, the linux command continues to analyze the state of the fault management node, and when the state of the fault management node is a main management node, an alarm mail is sent to a designated administrator, the automatic priority of the fault management node is reduced by 5, and then a Keepalived process is stopped;
step 3.2.4, synchronously checking other keepalives of the same virtual routing group by the linux command, and if the keepalives cannot receive the multicast packet of the main management node, trying to access a service address provided by the cluster management layer to the private network by the keepalives;
step 3.2.5, trying to access the abnormal IP address provided by the cluster management layer to the private network, and trying to connect the default gateway Ping again;
step 3.2.6, if the default gateway Ping can not be communicated, the linux command judges that the server in which the gateway is located is checked has a network fault, and an alarm mail is sent to an administrator;
and 3.2.7, if the default gateway Ping is communicated, judging that the main management node in the cluster management layer has a fault by the linux command, automatically binding the virtual IP to the server where the virtual IP is located, and taking over the task of the main management node.
Further, the interface service layer in step 3 performs parsing and checking when receiving the image and video segments sent by the cluster management layer, and then decodes the image and video segments.
Further, in step 4, according to the response time of the interface node, the Nginx allocates the image and the video clip sent by the cluster management layer to the interface node with the highest processing speed, so as to ensure that each interface node of the interface service layer processes the same amount of video images.
Further, step 4, the nginnx automatically checks the health status of the managed interface node, and automatically deletes the failed interface node from the list; and after the interface node which detects the fault is recovered to be normal, adding the interface node into the list to continue providing the service.
Further, the Nginx described in step 4 provides dynamically added interface nodes at the same time, and when a new interface node needs to be added to the interface service layer, the capacity expansion without stopping the service is realized by modifying the interface node list managed by the Nginx program and sending a process signal of the USR1 to the Nginx.
Further, in step 4, the interface nodes are interconnected with the information queue/cache, and the real-time information in the interface nodes is stored in the information queue/cache, so that the interface nodes have no task, and when the interface nodes executing the task have a fault, other interface nodes extract the current state of the task from the information queue/cache and continue to execute the task.
Further, after receiving the information sent by the cluster management layer, the interface node in step 4 splits the information, stores the picture and the video file in an information queue/cache, and stores the structured information in a cloud storage service through the NFS network file system, so as to shorten the information processing time.
Further, the interface nodes in step 4 are interconnected with cloud storage nodes in the cloud storage service, and each interface node is independently interconnected with a plurality of cloud storage nodes.
Further, in the cloud storage node in the cloud storage service in step 5, when the interface node writes a file to a plurality of cloud storage nodes, the specified cloud storage node is searched through the following execution steps:
step 5.1, numbering the cloud storage nodes in sequence from 0;
step 5.2, generating a unique ID number for each video clip or picture file, wherein the ID number consists of an equipment number, a timestamp, a category and a serial number;
and 5.3, respectively dividing the generated unique ID numbers by the total number of the cloud storage nodes, taking the remainder to obtain a regular result, and selecting the IP as the final cloud storage node according to the regular result.
Further, the main service cluster automatically judges the requirements of other systems on the data stored in the information queue/cache and cloud storage service and the target information concerned in the data, and forwards the data meeting the conditions to other systems.
Compared with the prior art, the video image information acquisition method based on the distributed cluster has the following remarkable advantages:
1. by adopting a video image information acquisition method based on a distributed cluster, tens of millions to hundreds of millions of pieces of video image information and structural description information thereof are received every day, and the video image information can be continuously and stably received and stored.
2. Under the condition of simultaneously acquiring and forwarding data by adopting a single tera network port, a 600M/s video short film + image file can be continuously and stably received and transmitted, and 7700 related pieces of structural description information are contained.
3. By adopting the video image information acquisition method based on the distributed cluster, the video and picture information processing capacity is improved, and the cost and time are saved.
4. By adopting the video image information acquisition method based on the distributed cluster, the cluster is expanded without stopping service.
Drawings
FIG. 1 is a flow chart of a distributed cluster-based video image information acquisition method;
FIG. 2 is a diagram of a cloud storage console in a distributed cluster-based video image information acquisition method;
Detailed Description
As shown in fig. 1 and fig. 2, the video image information collecting method based on distributed cluster includes the following steps:
step 1, data in an acquisition device/system are interconnected with a private network, the data are interconnected and stored in a cluster area through the private network, and the data stored in the cluster area are provided to a service information system through the private network again;
step 2, the cluster area is composed of a cluster management layer and an interface service layer, and the cluster management layer of the cluster area provides a fixed IP port for the private network;
step 3, a cluster management layer in the cluster area is provided with a main management node and a standby management node; the main management node and the standby management node in the cluster management layer are connected with the same and independent IP port to provide data transmission service;
step 4, the interface service layer takes Nginx as a plurality of independent stateless interface nodes, and the interface nodes are connected with a main management node and a standby management node in the cluster management layer in an HTTP long connection mode;
step 5, interface nodes in the interface service layer are respectively interconnected with the information queue/cache and the cloud storage service;
and 6, interconnecting the main service clusters through the information queues/caches, and interconnecting the main service clusters with the cloud storage service.
Further, if the main management node in step 3 fails, the standby management node starts switching to continue providing service, and the time for starting and switching the main management node and the standby management node to switch each other is 0.1-2S according to the configured priority.
Further, the cluster management layer in step 3 is used as an entrance for all external private network requests, the cluster management layer needs to provide a fixed IP to the outside, and when the primary management node fails, the standby management node continues to use the same IP to provide services to the outside.
Further, the cluster management layer in step 3 realizes high availability of the management nodes in a manner of master management nodes and standby management nodes, and realizes failover and automatic recovery of the master management nodes and the standby management nodes by using keepalive, and the failover and automatic recovery steps are as follows:
step 3.1, a Virtual Routing Redundancy Protocol (VRRP) used by keepalive shares a virtual IP among a router group, a main node and a plurality of standby nodes are arranged in the router group, the main node binds the external IP to a machine of the main node, a multicast packet is periodically sent, the standby nodes mark the main node as abnormal when the standby nodes cannot receive the multicast packet, and one standby node is selected as the main node according to the configured priority to keep the continuity and reliability of communication and eliminate the single node fault;
step 3.2, the keepalive regularly executes scripts specified by the user, and health check scripts are edited on machines where the main management nodes and the standby management nodes are located in the cluster management layer, so that the migration of faults of the main management nodes and the standby management nodes is realized, and the health check scripts execute the following steps:
step 3.2.1, running a linux command to check the management node;
step 3.2.2, checking the management node in the cluster management layer by the linux command, if the management node is abnormal, automatically restarting the management node, waiting for 15-30 milliseconds, checking whether the restarted management node is normal again, displaying a normal checking result, and finishing the linux command;
step 3.2.3, if the check result of the management node after automatic restart is abnormal, the linux command judges that the management node is in fault, the linux command continues to analyze the state of the fault management node, and when the state of the fault management node is a main management node, an alarm mail is sent to a designated administrator, the automatic priority of the fault management node is reduced by 5, and then a Keepalived process is stopped;
step 3.2.4, synchronously checking other keepalives of the same virtual routing group by the linux command, and if the keepalives cannot receive the multicast packet of the main management node, trying to access a service address provided by the cluster management layer to the private network by the keepalives;
step 3.2.5, trying to access the abnormal IP address provided by the cluster management layer to the private network, and trying to connect the default gateway Ping again;
step 3.2.6, if the default gateway Ping can not be communicated, the linux command judges that the server in which the gateway is located is checked has a network fault, and an alarm mail is sent to an administrator;
and 3.2.7, if the default gateway Ping is communicated, judging that the main management node in the cluster management layer has a fault by the linux command, automatically binding the virtual IP to the server where the virtual IP is located, and taking over the task of the main management node.
Further, the interface service layer in step 3 performs parsing and checking when receiving the image and video segments sent by the cluster management layer, and then decodes the image and video segments.
Further, in step 4, according to the response time of the interface node, the Nginx allocates the image and the video clip sent by the cluster management layer to the interface node with the highest processing speed, so as to ensure that each interface node of the interface service layer processes the same amount of video images.
Further, step 4, the nginnx automatically checks the health status of the managed interface node, and automatically deletes the failed interface node from the list; and after the interface node which detects the fault is recovered to be normal, adding the interface node into the list to continue providing the service.
Further, the Nginx described in step 4 provides dynamically added interface nodes at the same time, and when a new interface node needs to be added to the interface service layer, the capacity expansion without stopping the service is realized by modifying the interface node list managed by the Nginx program and sending a process signal of the USR1 to the Nginx.
Further, in step 4, the interface nodes are interconnected with the information queue/cache, and the real-time information in the interface nodes is stored in the information queue/cache, so that the interface nodes have no task, and when the interface nodes executing the task have a fault, other interface nodes extract the current state of the task from the information queue/cache and continue to execute the task.
Further, after receiving the information sent by the cluster management layer, the interface node in step 4 splits the information, stores the picture and the video file in an information queue/cache, and stores the structured information in a cloud storage service through the NFS network file system, so as to shorten the information processing time.
Further, the interface nodes in step 4 are interconnected with cloud storage nodes in the cloud storage service, and each interface node is independently interconnected with a plurality of cloud storage nodes.
Further, in the cloud storage node in the cloud storage service in step 5, when the interface node writes a file to a plurality of cloud storage nodes, the specified cloud storage node is searched through the following execution steps:
step 5.1, numbering the cloud storage nodes in sequence from 0;
step 5.2, generating a unique ID number for each video clip or picture file, wherein the ID number consists of an equipment number, a timestamp, a category and a serial number;
and 5.3, respectively dividing the generated unique ID numbers by the total number of the cloud storage nodes, taking the remainder to obtain a regular result, and selecting the IP as the final cloud storage node according to the regular result.
Further, the main service cluster automatically judges the requirements of other systems on the data stored in the information queue/cache and cloud storage service and the target information concerned in the data, and forwards the data meeting the conditions to other systems.
The above description is only for the preferred embodiment of the present invention and should not be construed as limiting the present invention, and it will be understood by those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the present invention, and any modifications, equivalents, improvements, etc. made therein are intended to be included within the scope of the appended claims.
Claims (10)
1. A video image information acquisition method based on distributed clusters is characterized by comprising the following steps:
step 1, data in an acquisition device/system are interconnected with a private network, the data are interconnected and stored in a cluster area through the private network, and the data stored in the cluster area are provided to a service information system through the private network again;
step 2, the cluster area is composed of a cluster management layer and an interface service layer, and the cluster management layer of the cluster area provides a fixed IP port for the private network;
step 3, a cluster management layer in the cluster area is provided with a main management node and a standby management node; the main management node and the standby management node in the cluster management layer are connected with the same and independent IP port to provide data transmission service;
the cluster management layer realizes high availability of management nodes in a mode of a main management node and a standby management node, and realizes fault transfer and automatic recovery of the main management node and the standby management node by adopting Keeplived, wherein the fault transfer and automatic recovery steps are as follows:
step 3.1, a Virtual Routing Redundancy Protocol (VRRP) used by keepalive shares a virtual IP among a router group, a main node and a plurality of standby nodes are arranged in the router group, the main node binds the external IP to a machine of the main node, a multicast packet is periodically sent, the standby nodes mark the main node as abnormal when the standby nodes cannot receive the multicast packet, and one standby node is selected as the main node according to the configured priority to keep the continuity and reliability of communication and eliminate the single node fault;
step 3.2, the keepalive regularly executes scripts specified by the user, and health check scripts are edited on machines where the main management nodes and the standby management nodes are located in the cluster management layer, so that the migration of faults of the main management nodes and the standby management nodes is realized, and the health check scripts execute the following steps:
step 3.2.1, running a linux command to check the management node;
step 3.2.2, checking the management node in the cluster management layer by the linux command, if the management node is abnormal, automatically restarting the management node, waiting for 15-30 milliseconds, checking whether the restarted management node is normal again, displaying a normal checking result, and finishing the linux command;
step 3.2.3, if the check result of the management node after automatic restart is abnormal, the linux command judges that the management node is in fault, the linux command continues to analyze the state of the fault management node, and when the state of the fault management node is a main management node, an alarm mail is sent to a designated administrator, the automatic priority of the fault management node is reduced by 5, and then a Keepalived process is stopped;
step 3.2.4, synchronously checking other keepalives of the same virtual routing group by the linux command, and if the keepalives cannot receive the multicast packet of the main management node, trying to access a service address provided by the cluster management layer to the private network by the keepalives;
step 3.2.5, trying to access the abnormal IP address provided by the cluster management layer to the private network, and trying to connect the default gateway Ping again;
step 3.2.6, if the default gateway Ping can not be communicated, the linux command judges that the server in which the gateway is located is checked has a network fault, and an alarm mail is sent to an administrator;
step 3.2.7, if the default gateway Ping is communicated, the linux command judges that the main management node in the cluster management layer has a fault, the virtual IP is automatically bound to the server where the virtual IP is located, and the task of the main management node is taken over;
step 4, the interface service layer takes Nginx as a plurality of independent stateless interface nodes for managing, the interface nodes adopt an HTTP long connection mode to connect a main management node and a standby management node in the cluster management layer, the main management node starts switching to continuously provide services if a fault occurs, the main management node and the standby management node are started and switched according to configured priority, and the mutual starting and switching time of the main management node and the standby management node is 0.1-2S;
the cluster management layer is used as an entrance of all external private network requests, the cluster management layer needs to provide a fixed IP for the outside, and when the main management node fails, the standby management node continues to use the same IP to provide services for the outside;
step 5, interface nodes in the interface service layer are respectively interconnected with the information queue/cache and the cloud storage service;
and 6, interconnecting the main service clusters by the information queue/cache region, and interconnecting the main service clusters with the cloud storage service.
2. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 3, when receiving the image and video segments sent by the cluster management layer, the interface service layer performs analysis and verification and then decodes the image and video segments.
3. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 4, the Nginx allocates the image and the video clip sent by the cluster management layer to the interface node with the highest processing speed according to the response time of the interface node so as to ensure that each interface node of the interface service layer processes the same amount of video images.
4. The distributed cluster-based video image information acquisition method according to claim 1, wherein: step 4, the Nginx automatically checks the health state of the managed interface nodes and automatically deletes the fault interface nodes from the list; and after the interface node which detects the fault is recovered to be normal, adding the interface node into the list to continue providing the service.
5. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 4, the Nginx simultaneously provides dynamically increased interface nodes, and when a new interface node needs to be added into an interface service layer, the Nginx modifies an interface node list managed by a Nginx program and sends a process signal of USR1 to the Nginx, so that the capacity expansion is realized without stopping the service.
6. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 4, the interface nodes are interconnected with the information queue/cache, the real-time information in the interface nodes is stored in the information queue/cache so as to realize that the interface nodes have no task, and when the interface nodes executing the task have faults, other interface nodes extract the current state of the task from the information queue/cache and continue to execute the task.
7. The distributed cluster-based video image information acquisition method according to claim 1, wherein: in step 4, after receiving the information sent by the cluster management layer, the interface node splits the information, stores the picture and the video file into an information queue/cache, and stores the structured information into a cloud storage service through the NFS network file system, so as to shorten the information processing time.
8. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 4, the interface nodes are interconnected with the cloud storage nodes in the cloud storage service, and each interface node is independently interconnected with a plurality of cloud storage nodes.
9. The distributed cluster-based video image information acquisition method according to claim 1, wherein: step 5, when the interface node writes a file to a plurality of cloud storage nodes, the cloud storage nodes in the cloud storage service search for the specified cloud storage nodes through the following execution steps:
step 5.1, numbering the cloud storage nodes in sequence from 0;
step 5.2, generating a unique ID number for each video clip or picture file, wherein the ID number consists of an equipment number, a timestamp, a category and a serial number;
and 5.3, respectively dividing the generated unique ID numbers by the total number of the cloud storage nodes, taking the remainder to obtain a regular result, and selecting the IP as the final cloud storage node according to the regular result.
10. The distributed cluster-based video image information acquisition method according to claim 1, wherein: and 6, automatically judging the requirements of other systems on the data stored in the information queue/cache and the cloud storage service and the target information concerned in the data by the main service cluster, and forwarding the data meeting the conditions to other systems.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911114002.2A CN110971872B (en) | 2019-11-14 | 2019-11-14 | Video image information acquisition method based on distributed cluster |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201911114002.2A CN110971872B (en) | 2019-11-14 | 2019-11-14 | Video image information acquisition method based on distributed cluster |
Publications (2)
Publication Number | Publication Date |
---|---|
CN110971872A CN110971872A (en) | 2020-04-07 |
CN110971872B true CN110971872B (en) | 2021-05-18 |
Family
ID=70030711
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201911114002.2A Active CN110971872B (en) | 2019-11-14 | 2019-11-14 | Video image information acquisition method based on distributed cluster |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110971872B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112003721B (en) * | 2020-07-15 | 2022-10-14 | 苏州浪潮智能科技有限公司 | Method and device for realizing high availability of large data platform management node |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9178935B2 (en) * | 2009-03-05 | 2015-11-03 | Paypal, Inc. | Distributed steam processing |
CN102467508A (en) * | 2010-11-04 | 2012-05-23 | 中兴通讯股份有限公司 | Method for providing database service and database system |
CN103955509A (en) * | 2014-04-30 | 2014-07-30 | 广西电网公司电力科学研究院 | Quick search method for massive electric power metering data |
CN105117171B (en) * | 2015-08-28 | 2018-11-30 | 南京国电南自维美德自动化有限公司 | A kind of energy SCADA mass data distributed processing system(DPS) and its method |
CN110225074B (en) * | 2019-01-04 | 2023-04-14 | 国网浙江省电力有限公司 | Communication message distribution system and method based on equipment address domain |
-
2019
- 2019-11-14 CN CN201911114002.2A patent/CN110971872B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN110971872A (en) | 2020-04-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11714726B2 (en) | Failover and recovery for replicated data instances | |
US10601728B2 (en) | Software-defined data center and service cluster scheduling and traffic monitoring method therefor | |
US11477105B2 (en) | Monitoring of replicated data instances | |
CN109361532B (en) | High availability system and method for network data analysis and computer readable storage medium | |
US9641449B2 (en) | Variable configurations for workload distribution across multiple sites | |
CN107547661B (en) | Container load balancing implementation method | |
WO2020147331A1 (en) | Micro-service monitoring method and system | |
US20170279674A1 (en) | Method and apparatus for expanding high-availability server cluster | |
US7518983B2 (en) | Proxy response apparatus | |
US20130159487A1 (en) | Migration of Virtual IP Addresses in a Failover Cluster | |
WO2017050254A1 (en) | Hot backup method, device and system | |
JP5804189B2 (en) | Information processing system, information processing method, program | |
CN106713378B (en) | Method and system for providing service by multiple application servers | |
WO2021004385A1 (en) | Service unit switching method, system and apparatus | |
CN110971872B (en) | Video image information acquisition method based on distributed cluster | |
CN109088830B (en) | Port state synchronization method and device | |
CN113709220B (en) | High-availability implementation method and system of virtual load equalizer and electronic equipment | |
EP3570169A1 (en) | Method and system for processing device failure | |
CN113347038B (en) | Circulation mutual-backup high-availability system for bypass flow processing | |
JP2006100906A (en) | Method for managing operation of network system and storage device | |
CN113055461A (en) | ZooKeeper-based unmanned cluster distributed cooperative command control method | |
CN108847980A (en) | A kind of method and device of CTDB node failure virtual IP address migration | |
CN111490886B (en) | Network data processing method and system | |
CN112019601B (en) | Two-node implementation method and system based on distributed storage Ceph | |
CN114422567A (en) | Data request processing method, device, system, computer equipment and medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |