CN111752757A - Same-city double-center system - Google Patents
Same-city double-center system Download PDFInfo
- Publication number
- CN111752757A CN111752757A CN202010614232.1A CN202010614232A CN111752757A CN 111752757 A CN111752757 A CN 111752757A CN 202010614232 A CN202010614232 A CN 202010614232A CN 111752757 A CN111752757 A CN 111752757A
- Authority
- CN
- China
- Prior art keywords
- node
- application
- database
- cluster
- service
- 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.)
- Pending
Links
- 238000011084 recovery Methods 0.000 claims description 28
- 238000012546 transfer Methods 0.000 claims description 12
- 230000009977 dual effect Effects 0.000 claims description 6
- 230000005012 migration Effects 0.000 claims description 6
- 238000013508 migration Methods 0.000 claims description 6
- 238000000034 method Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1461—Backup scheduling policy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1456—Hardware arrangements for backup
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Abstract
The application discloses with two central systems in city, main central system and with city disaster preparation central system, main central system includes the first storage cluster that first application cluster, the first database cluster that a plurality of first database nodes constitute and a plurality of first storage node constitute that a plurality of first application nodes constitute, with city disaster preparation central system including the second application cluster that a plurality of second application nodes constitute, the second database cluster that a plurality of second database nodes constitute and the second storage cluster that a plurality of first storage node constitute. When the main central system is normal, the city-like disaster preparation central system also provides query service, so that the service load of the main central system is reduced, and the utilization rate of the city-like disaster preparation central system is improved; and other files except the file to be shared in the file to be stored are stored locally, and the external service of the double-center system in the same city is not influenced when the shared storage fails.
Description
Technical Field
The application relates to the technical field of computers, in particular to a same-city double-center system.
Background
At present, a banking core business system adopts a deployment mode combining a master-standby deployment mode and a cluster deployment mode, and with the development and analysis of banking core business and the summary of the operation condition of the banking core business system, higher requirements are put forward on the performance and the function of the banking core business system.
Under the condition that the bank core business system comprises a main system and a city-sharing disaster recovery system which adopt a cluster deployment mode, the city-sharing disaster recovery system is utilized only when the main system fails, the utilization rate of the city-sharing disaster recovery system is low, and system resources are wasted; in addition, the bank core business system generally adopts a shared storage technology, and the external service of the bank core business system is seriously influenced under the condition that the shared storage is invalid.
Disclosure of Invention
In view of this, the embodiment of the present application provides a city double-center system, which reduces the service load of the main center system and improves the utilization rate of the city disaster recovery center system; and the external service of the double-center system in the same city is not influenced when the shared storage fails.
In a first aspect, an embodiment of the present application provides a city-based dual-center system, including:
the disaster recovery system comprises a main central system and a city-sharing disaster preparation central system, wherein the main central system comprises a first application cluster, a first database cluster and a first storage cluster, the first application cluster comprises a plurality of first application nodes, the first database cluster comprises a plurality of first database nodes, and the first storage cluster comprises a plurality of first storage nodes; the same-city disaster preparation center system comprises a second application cluster, a second database cluster and a second storage cluster, wherein the second application cluster comprises a plurality of second application nodes, the second database cluster comprises a plurality of second database nodes, and the second storage cluster comprises a plurality of first storage nodes;
the first application node is used for accessing the corresponding first database node if the read-write transaction service or the query transaction service is allocated when the main center system is normal;
the first database node is used for providing read-write service and query service when the main center system is normal;
the second application node is used for accessing the corresponding first database node if the read-write transaction service is allocated to the main central system and the same-city disaster recovery central system when the main central system and the same-city disaster recovery central system are both normal; if the second database node is distributed to the query transaction service, accessing the corresponding second database node;
the second database node is used for providing the query service when the main central system and the disaster preparation central system in the same city are normal;
the first storage node is used for locally storing other files except the files to be shared in the files to be stored.
Optionally, each of the first application nodes and each of the first database nodes are deployed independently; each of the second application nodes and each of the second database nodes are deployed independently.
Optionally, when a single first application node fails, the first application node supports service transfer; when a single second application node fails, the second application node supports service transfer; when a single first database node fails, the first database node supports service transfer; when a single said second database node fails, said second database node supports service transfer; the first storage node supports storage migration when a single of the first storage nodes fails.
Optionally, the city bicenter system further includes a transaction route;
and the transaction route is used for carrying out route distribution on the transaction service according to the system state and the service type of the transaction service, and the transaction service comprises the read-write transaction service and the query transaction service.
Optionally, the transaction routing is specifically configured to:
when the main center system and the disaster recovery center system in the same city are normal, the read-write transaction service is processed according to a first preset proportion a: b, distributing the query type transaction service to the first application node and the second application node, and performing the query type transaction service according to a second preset proportion c: d to the first application node and the second application node; a + b is 1, a > b, c + d is 1, c < d.
Optionally, the transaction routing is specifically configured to:
and when the same-city disaster recovery center system fails, distributing each read-write transaction service and each query transaction service to the first application node.
Optionally, the transaction routing is specifically configured to:
and when the main central system fails, distributing each read-write transaction service and each query transaction service to the second application node.
Optionally, the other files include a system execution code file and a system log file.
Optionally, the first application cluster supports dynamic node expansion, and the second application cluster supports dynamic node expansion.
Optionally, when the first application cluster dynamic node is expanded, the dynamic node expansion specifically clones the existing first application node as the newly added first application node; when the second application cluster dynamic node is expanded, the dynamic node expansion specifically clones the existing second application node as the newly added second application node.
Compared with the prior art, the method has the advantages that:
by adopting the technical scheme of the embodiment of the application, the same-city double-center system comprises a main center system and a same-city disaster preparation center system, the main center system comprises a first application cluster consisting of a plurality of first application nodes, a first database cluster consisting of a plurality of first database nodes and a first storage cluster consisting of a plurality of first storage nodes, and the same-city disaster preparation center system comprises a second application cluster consisting of a plurality of second application nodes, a second database cluster consisting of a plurality of second database nodes and a second storage cluster consisting of a plurality of first storage nodes. The first application node is used for accessing a corresponding first database node if the first application node is distributed to read-write transaction service or query transaction service when the first application node is in the main central system; the first database node is used for providing read-write service and query service when the main central system is normal; the second application node is used for accessing the corresponding first database node if the read-write transaction service is distributed when the main central system and the same-city disaster preparation central system are normal; if the query type transaction service is distributed, accessing a corresponding second database node; the second database node is used for providing query service when the main central system is normal and when the main central system is in the same city as the disaster recovery central system; the first storage node is used for locally storing other files except the files to be shared in the files to be stored. Therefore, when the main central system is normal, the disaster recovery central system in the same city also provides query service, the service load of the main central system is reduced, and the utilization rate of the disaster recovery central system in the same city is improved; and other files except the file to be shared in the file to be stored are stored locally, and the external service of the double-center system in the same city is not influenced when the shared storage fails.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a same city dual-center system according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of another city-level dual-center system according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
At the present stage, the bank core business system comprises a main system and a city-sharing disaster recovery system, the main system and the city-sharing disaster recovery system adopt a framework of a cluster deployment mode, and the framework cannot meet higher requirements for the performance and the function of the bank core business system along with the development analysis of the bank core business and the summary of the operation condition of the bank core business system. The inventor finds that the disaster recovery system in the same city in the bank core business system is used only when the main system fails, the utilization rate of the disaster recovery system in the same city is low, and system resources are wasted; in addition, the bank core business system generally adopts a shared storage technology, and the external service of the bank core business system is seriously influenced under the condition that the shared storage is invalid.
In order to solve the problem, in the embodiment of the present application, the city-sharing dual-center system includes a main center system and a city-sharing disaster recovery center system, where the main center system includes a first application cluster formed by a plurality of first application nodes, a first database cluster formed by a plurality of first database nodes, and a first storage cluster formed by a plurality of first storage nodes, and the city-sharing disaster recovery center system includes a second application cluster formed by a plurality of second application nodes, a second database cluster formed by a plurality of second database nodes, and a second storage cluster formed by a plurality of first storage nodes. The first application node is used for accessing a corresponding first database node if the first application node is distributed to read-write transaction service or query transaction service when the first application node is in the main central system; the first database node is used for providing read-write service and query service when the main central system is normal; the second application node is used for accessing the corresponding first database node if the read-write transaction service is distributed when the main central system and the same-city disaster preparation central system are normal; if the query type transaction service is distributed, accessing a corresponding second database node; the second database node is used for providing query service when the main central system is normal and when the main central system is in the same city as the disaster recovery central system; the first storage node is used for locally storing other files except the files to be shared in the files to be stored. Therefore, when the main central system is normal, the disaster recovery central system in the same city also provides query service, the service load of the main central system is reduced, and the utilization rate of the disaster recovery central system in the same city is improved; and other files except the file to be shared in the file to be stored are stored locally, and the external service of the double-center system in the same city is not influenced when the shared storage fails.
The following describes in detail a specific implementation manner of the same city dual-center system in the embodiment of the present application by way of an embodiment with reference to the drawings.
Exemplary System
Referring to fig. 1, a schematic structural diagram of a city-level double-center system in an embodiment of the present application is shown. In this embodiment, the city bicenter system may specifically include:
the disaster recovery system comprises a main center system 100 and a city disaster preparation center system 200, wherein the main center system 100 comprises a first application cluster 101, a first database cluster 102 and a first storage cluster 103, the first application cluster 101 comprises a plurality of first application nodes 104, the first database cluster 102 comprises a plurality of first database nodes 105, and the first storage cluster 103 comprises a plurality of first storage nodes 106; the city disaster preparation center system 200 comprises a second application cluster 201, a second database cluster 202 and a second storage cluster 203, wherein the second application cluster 201 comprises a plurality of second application nodes 204, the second database cluster 202 comprises a plurality of second database nodes 205, and the second storage cluster 203 comprises a plurality of first storage nodes 106;
the first application node 104 is configured to, when the main central system 100 is normal, access the corresponding first database node 105 if the read-write transaction service or the query transaction service is allocated;
the first database node 105 is configured to provide a read-write service and an inquiry service when the main center system 100 is normal;
the second application node 204 is configured to, when both the main central system 100 and the disaster recovery central system 200 in the same city are normal, access the corresponding first database node 105 if the read-write transaction service is allocated; if the query type transaction service is allocated, accessing the corresponding second database node 205;
the second database node 205 is configured to provide the query service when both the main central system 100 and the disaster preparation central system 200 in the same city are normal;
the first storage node 106 is configured to locally store other files except the file to be shared in the file to be stored.
It can be understood that in the prior art, the disaster recovery system in the same city is utilized only when the main system fails, the utilization rate of the disaster recovery system in the same city is low, and system resources are wasted; in this embodiment of the present application, in order to improve the utilization rate of the same-city disaster recovery center system, even if the main center system 100 in the same-city dual center system is normal, the read-write transaction service or the query transaction service is allocated to the first application node 104, the first application node 104 may be allocated to the read-write transaction service to the second application node 204 on the basis of accessing the corresponding first database node 105 through the corresponding read-write transaction service component or the query transaction service component, and the second application node 204 accesses the corresponding first database node 105 through the read-write transaction service component; and may also be distributed to the second application node 204, and the second application node 204 accesses the corresponding second database node 205 through the query transaction service component. In this way, the same city disaster recovery center system 200 also provides query service when the main center system 100 is normal, and the transaction service load of the main center system 100 is reduced, thereby improving the utilization rate of the same city disaster recovery center system 200.
It should be noted that, in this embodiment, when the main center system 100 is normal, the second application node 204 in the second application cluster 201 may be allocated to a read-write transaction service, and may also be allocated to an inquiry transaction service, where the read-write transaction service and the inquiry transaction service are transaction services of two different service types. In order to realize intelligent distribution of transaction services to the second application node 104 in the first application cluster 101 or the second application node 204 in the second application cluster 201, reasonably reduce transaction service load of the main central system 100, improve the utilization rate of the same-city disaster recovery central system 200, a transaction route needs to be set in the same-city double-central system, and the transaction route performs route distribution on the transaction services according to the system state and the service type of the transaction services. Therefore, in an optional implementation manner of the embodiment of the present application, the city bicenter system further includes a transaction route; and the transaction route is used for carrying out route distribution on the transaction service according to the system state and the service type of the transaction service, and the transaction service comprises the read-write transaction service and the query transaction service. For example, as shown in fig. 2, another city bicenter system is shown, in which a transaction route 300 is added on the basis of fig. 1.
The following describes in detail an embodiment of transaction routing assignment of transaction services according to system status and service type of transaction services.
When the main central system 100 and the city-owned disaster recovery central system 200 are normal, the read-write transaction services can be allocated to the first application node 104 or the second application node 204, and considering that the main central system 100 mainly processes the read-write transaction services under the condition, the number of the read-write transaction services allocated to the first application node 104 needs to be larger than the number of the read-write transaction services allocated to the second application node 204. The query-type transaction services may be distributed to either the first application node 104 or the second application node 204, and considering that the query-type transaction services are mainly or completely processed by the city disaster recovery center system 200 under this situation, the number of the query-type transaction services distributed to the first application node 104 needs to be smaller than the number of the query-type transaction services distributed to the second application node 204. Therefore, in an optional implementation manner of this embodiment of the present application, the transaction routing is specifically configured to: when the main center system 100 and the city-sharing disaster preparation center system 200 are normal, the read-write transaction service is performed according to a first preset proportion a: b is distributed to the first application node 104 and the second application node 204, and the query transaction service is processed according to a second preset proportion c: d to the first application node 104 and the second application node 204; a + b is 1, a > b, c + d is 1, c < d. For example, the first preset ratio a: b may be 80%: 20 percent; the first preset proportion a: b may be 0%: 100 percent.
Of course, when the disaster recovery center system 200 in the same city fails, both the read-write transaction service and the query transaction service cannot be allocated to the second application node 204, but only to the first application node 104. Therefore, in an optional implementation manner of this embodiment of the present application, the transaction routing is specifically configured to: when the disaster recovery center system 200 in the same city fails, each of the read-write transaction services and each of the query transaction services are distributed to the first application node 104.
Similarly, when the main central system 100 fails, both the read-write transaction service and the query transaction service cannot be allocated to the first application node 104, but only to the second application node 204. Therefore, in an optional implementation manner of this embodiment of the present application, the transaction routing is specifically configured to: when the master center system 100 fails, distributing each read-write transaction service and each query transaction service to the second application node 204.
It can also be understood that, in the prior art, the bank core business system generally adopts a shared storage technology, and the external service of the bank core business system is seriously influenced under the condition that the shared storage is invalid; in the embodiment of the application, in order to avoid influencing the external service of the same-city dual-center system when the shared storage fails, for other files except the file to be shared in the file to be stored, the shared storage is not required, the storage node does not store the files in a shared storage mode, but stores the files in a local storage mode, and the mode does not influence the external service of the same-city dual-center system when the shared storage fails.
The files to be stored, except the files to be shared, represent files that do not need to be shared in the files to be stored, and generally refer to system execution code files and system log files that only need to be stored locally. Therefore, in an optional implementation manner of the embodiment of the present application, the other files include a system execution code file and a system log file.
It should be noted that, in the prior art, when an application node and a database node are deployed, independence between the application node and the database node is not considered, and the application node and the database node are deployed on the same cluster machine, so that a large risk of putting a single point of failure exists; that is, a cluster machine that deploys both application nodes and database nodes fails, resulting in both application services and database services being abnormal. Therefore, in the embodiment of the application, each application node in the application cluster and the database node in the database cluster are independently deployed, and the symmetric deployment and transformation of the application node and the database node are realized. The deployment mode effectively reduces the risk of single-point faults, improves the high availability and the concurrent processing capacity of the system, and does not influence the normal external service provision of the system when single-point faults occur in a single application node and a single database node. That is, in an optional implementation manner of the embodiment of the present application, each of the first application nodes 104 and each of the first database nodes 105 are deployed independently; each of the second application nodes 204 and each of the second database nodes 205 are deployed independently.
Moreover, when a single application node, a single database node or a single storage node fails, the single node can be automatically and quickly transferred to avoid the system external service exception caused by the single node failure. Specifically, the application node supports service migration, the database node supports service migration, and the storage node supports storage migration. Therefore, in an optional implementation manner of this embodiment of the present application, when a single first application node 104 fails, the first application node 104 supports service transfer; when a single said second application node 204 fails, said second application node 204 supports service transfer; said first database node 105 supports service transfer when a single said first database node 105 fails; when a single said second database node 205 fails, said second database node 205 supports service transfer; the first storage node 106 supports storage migration when a single one of the first storage nodes 106 fails.
It should be further noted that, in order to meet the requirement of flexible expansion of application nodes in an application cluster, the application nodes in the application cluster need to be flexibly deployed, that is, the application nodes in the application cluster can be dynamically expanded, for example, when a same-city dual-center system is in a transaction processing peak, new application nodes can be dynamically added to the application cluster in a menu manner so as to cope with the transaction processing peak. Therefore, in an optional implementation manner of this embodiment of the present application, the first application cluster 101 supports dynamic node expansion, and both the second application clusters 201 support dynamic node expansion.
Specifically, the dynamic node expansion of the application cluster actually clones the existing application node as the newly added application node, and when the load balancing switch is turned on, the read-write transaction service and the query transaction service can be distributed to the existing application node and the newly added application node in a balanced manner. Therefore, in an optional implementation manner of this embodiment of the present application, when a dynamic node of the first application cluster 101 is expanded, the dynamic node expansion specifically clones the existing first application node 104 as the newly added first application node 104; when the second application cluster 201 is dynamically expanded, the dynamic node expansion specifically clones the existing second application node 204 as the newly added second application node 204.
Through various implementation manners provided by this embodiment, the city-sharing dual-center system includes a main center system and a city-sharing disaster preparation center system, the main center system includes a first application cluster composed of a plurality of first application nodes, a first database cluster composed of a plurality of first database nodes, and a first storage cluster composed of a plurality of first storage nodes, and the city-sharing disaster preparation center system includes a second application cluster composed of a plurality of second application nodes, a second database cluster composed of a plurality of second database nodes, and a second storage cluster composed of a plurality of first storage nodes. The first application node is used for accessing a corresponding first database node if the first application node is distributed to read-write transaction service or query transaction service when the first application node is in the main central system; the first database node is used for providing read-write service and query service when the main central system is normal; the second application node is used for accessing the corresponding first database node if the read-write transaction service is distributed when the main central system and the same-city disaster preparation central system are normal; if the query type transaction service is distributed, accessing a corresponding second database node; the second database node is used for providing query service when the main central system is normal and when the main central system is in the same city as the disaster recovery central system; the first storage node is used for locally storing other files except the files to be shared in the files to be stored. Therefore, when the main central system is normal, the disaster recovery central system in the same city also provides query service, the service load of the main central system is reduced, and the utilization rate of the disaster recovery central system in the same city is improved; and other files except the file to be shared in the file to be stored are stored locally, and the external service of the double-center system in the same city is not influenced when the shared storage fails.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing is merely a preferred embodiment of the present application and is not intended to limit the present application in any way. Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application. Those skilled in the art can now make numerous possible variations and modifications to the disclosed embodiments, or modify equivalent embodiments, using the methods and techniques disclosed above, without departing from the scope of the claimed embodiments. Therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present application still fall within the protection scope of the technical solution of the present application without departing from the content of the technical solution of the present application.
Claims (10)
1. A same city dual center system, comprising: the disaster recovery system comprises a main central system and a city-sharing disaster preparation central system, wherein the main central system comprises a first application cluster, a first database cluster and a first storage cluster, the first application cluster comprises a plurality of first application nodes, the first database cluster comprises a plurality of first database nodes, and the first storage cluster comprises a plurality of first storage nodes; the same-city disaster preparation center system comprises a second application cluster, a second database cluster and a second storage cluster, wherein the second application cluster comprises a plurality of second application nodes, the second database cluster comprises a plurality of second database nodes, and the second storage cluster comprises a plurality of first storage nodes;
the first application node is used for accessing the corresponding first database node if the read-write transaction service or the query transaction service is allocated when the main center system is normal;
the first database node is used for providing read-write service and query service when the main center system is normal;
the second application node is used for accessing the corresponding first database node if the read-write transaction service is allocated to the main central system and the same-city disaster recovery central system when the main central system and the same-city disaster recovery central system are both normal; if the second database node is distributed to the query transaction service, accessing the corresponding second database node;
the second database node is used for providing the query service when the main central system and the disaster preparation central system in the same city are normal;
the first storage node is used for locally storing other files except the files to be shared in the files to be stored.
2. The co-urban dual-hub system according to claim 1, wherein each of said first application nodes and each of said first database nodes are deployed independently; each of the second application nodes and each of the second database nodes are deployed independently.
3. The metro dual-hub system of claim 1, wherein when a single said first application node fails, said first application node supports service transfer; when a single second application node fails, the second application node supports service transfer; when a single first database node fails, the first database node supports service transfer; when a single said second database node fails, said second database node supports service transfer; the first storage node supports storage migration when a single of the first storage nodes fails.
4. The city bicenter system of claim 1, further comprising a transaction route;
and the transaction route is used for carrying out route distribution on the transaction service according to the system state and the service type of the transaction service, and the transaction service comprises the read-write transaction service and the query transaction service.
5. The same city dual hub system as in claim 4, wherein the transaction routing is specifically configured to:
when the main center system and the disaster recovery center system in the same city are normal, the read-write transaction service is processed according to a first preset proportion a: b, distributing the query type transaction service to the first application node and the second application node, and performing the query type transaction service according to a second preset proportion c: d to the first application node and the second application node; a + b is 1, a > b, c + d is 1, c < d.
6. The same city dual hub system as in claim 4, wherein the transaction routing is specifically configured to:
and when the same-city disaster recovery center system fails, distributing each read-write transaction service and each query transaction service to the first application node.
7. The same city dual hub system as in claim 4, wherein the transaction routing is specifically configured to:
and when the main central system fails, distributing each read-write transaction service and each query transaction service to the second application node.
8. The metro dual hub system of claim 1, wherein said other files comprise system execution code files and system log files.
9. The metro dual-hub system of claim 1, wherein the first application cluster supports dynamic node expansion and the second application cluster supports dynamic node expansion.
10. The co-urban dual-hub system according to claim 9, wherein when a dynamic node of the first application cluster is expanded, the dynamic node expansion specifically clones the existing first application node as the newly added first application node; when the second application cluster dynamic node is expanded, the dynamic node expansion specifically clones the existing second application node as the newly added second application node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010614232.1A CN111752757A (en) | 2020-06-30 | 2020-06-30 | Same-city double-center system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010614232.1A CN111752757A (en) | 2020-06-30 | 2020-06-30 | Same-city double-center system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111752757A true CN111752757A (en) | 2020-10-09 |
Family
ID=72676782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010614232.1A Pending CN111752757A (en) | 2020-06-30 | 2020-06-30 | Same-city double-center system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111752757A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
| CN103365979A (en) * | 2013-07-03 | 2013-10-23 | 交通银行股份有限公司 | Long-distance double-center online processing method and system based on open database |
| CN105577761A (en) * | 2015-12-16 | 2016-05-11 | 北京神州新桥科技有限公司 | Trade processing system and trade processing method based on double sites |
| CN108512693A (en) * | 2018-02-24 | 2018-09-07 | 国家计算机网络与信息安全管理中心 | A kind of trans-regional disaster recovery method and device |
-
2020
- 2020-06-30 CN CN202010614232.1A patent/CN111752757A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
| CN103365979A (en) * | 2013-07-03 | 2013-10-23 | 交通银行股份有限公司 | Long-distance double-center online processing method and system based on open database |
| CN105577761A (en) * | 2015-12-16 | 2016-05-11 | 北京神州新桥科技有限公司 | Trade processing system and trade processing method based on double sites |
| CN108512693A (en) * | 2018-02-24 | 2018-09-07 | 国家计算机网络与信息安全管理中心 | A kind of trans-regional disaster recovery method and device |
Non-Patent Citations (1)
| Title |
|---|
| 郑仕辉: "打破技术瓶颈 同城双活中心一体化运行", 金融电子化, 30 November 2013 (2013-11-30), pages 50 - 51 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3433759B1 (en) | Method and apparatus for expanding high-availability server cluster | |
| EP1159681B1 (en) | System and method for determining cluster membership in a heterogeneous distributed system | |
| CN112671882B (en) | Same-city double-activity system and method based on micro-service | |
| CN102938001B (en) | Data loading device and data load method | |
| JP4405511B2 (en) | Dynamically configurable fault tolerance in autonomous computing with multiple service points | |
| CN106302702A (en) | Burst storage method, the Apparatus and system of data | |
| US20140108358A1 (en) | System and method for supporting transient partition consistency in a distributed data grid | |
| CN103365979A (en) | Long-distance double-center online processing method and system based on open database | |
| CN105930498A (en) | Distributed database management method and system | |
| CN105337780B (en) | A kind of server node configuration method and physical node | |
| CN107430603A (en) | The system and method for MPP database | |
| CN107124469B (en) | Cluster node communication method and system | |
| WO2012069091A1 (en) | Real time database system | |
| EP3786802B1 (en) | Method and device for failover in hbase system | |
| CN104054076A (en) | Data storage method, database storage node failure processing method and apparatus | |
| CN111158949A (en) | Configuration method, switching method and device of disaster recovery architecture, equipment and storage medium | |
| US20070239736A1 (en) | Commit tree optimization based on recovery topology information | |
| CN109245915B (en) | Method and system for realizing server set balanced allocation | |
| CN110519354A (en) | A kind of distributed objects storage system and its method for processing business and storage medium | |
| CN114422331A (en) | Disaster tolerance switching method, device and system | |
| KR19990043986A (en) | Business take over system | |
| CN111752757A (en) | Same-city double-center system | |
| US20080250421A1 (en) | Data Processing System And Method | |
| US11061719B2 (en) | High availability cluster management of computing nodes | |
| CN116954863A (en) | Database scheduling method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |