CN105159796A - Data processing method and server end - Google Patents
Data processing method and server end Download PDFInfo
- Publication number
- CN105159796A CN105159796A CN201510524312.7A CN201510524312A CN105159796A CN 105159796 A CN105159796 A CN 105159796A CN 201510524312 A CN201510524312 A CN 201510524312A CN 105159796 A CN105159796 A CN 105159796A
- Authority
- CN
- China
- Prior art keywords
- server
- data
- master server
- client
- master
- 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
Landscapes
- Hardware Redundancy (AREA)
Abstract
The present invention discloses a data processing method and a server end. The method comprises: a slave server receiving data sent by a client, backing up the data into a memory database, and returning confirmation information of the data to the client, wherein the data is identical to data sent by the client to a master server, and the slave server and the master server are respectively arranged in different computer rooms. By means of the scheme provided by the present invention, the problem that when conventional hot-standby dual computers are located in the same computer room, the whole service system breaks down once a problem occurs to the computer room, thereby causing serious influence on user application, can be avoided.
Description
Technical field
The present invention relates to the double-machine standby technology of server data, particularly relate to a kind of data processing method and server end.
Background technology
Along with internet (mobile Internet) high speed development, user is the data, services that provides of reliance server more and more, strengthens the usability requirements of data, needs the service (data) that access services device more anywhere or anytime provides; Traditional two-node cluster hot backup is the hot reserve scheme in same machine room, and on May 27th, 2015, Hangzhou Xiaoshan somewhere optical fiber is dug disconnected, causes some local Alipays to use; On May 28th, 2015, ctrip.com can not normally access, so the service that user cannot normally use ctrip.com to provide; Based on the generation of above-mentioned accident, knownly to go wrong once this machine room when hot standby two-shipper is in same machine room, whole service system can be made to paralyse, have a strong impact on user's application.
Summary of the invention
In order to solve the problem, the present invention proposes a kind of data processing method and server end, when conventional hot standby two-shipper can be avoided to be in same machine room, go wrong once this machine room, whole service system is paralysed, having a strong impact on the problem of user's application.
In order to achieve the above object, the present invention proposes a kind of data processing method, the method comprises:
From the data that server receives client sends, these data are stored in memory database, and return the confirmation receiving these data to client.
Wherein, these data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.
Preferably, the method also comprises:
When master server breaks down, be that master server carries out work from Server switching, and before handover by receive from client and untreated data process.
Preferably, the method also comprises:
When master server breaks down, from the first notification message that this master server of server reception master server transmission breaks down, and after master server recovers normally, receive normal second notification message of this master server recovery that master server sends, and receive and the data processed from server during the master server that master server sends breaks down.
When from server fail, this third notice message from server fail is sent from server to master server, and send should recover normal 4th notification message from server to master server afterwards recovering normal from server, and receiving and the data processed from master server during server fail of receiving that master server sends.
Preferably, the method also comprises:
When not breaking down from server, when the quantity of the data backed up in memory database reaches default storage threshold, the data backed up from server process memory database, and by the data conversion storage after process in non-memory database.
In order to achieve the above object, the invention allows for a kind of data processing server end, this server end comprises master server and one or more from server.
From the data that server sends for receiving client, these data being stored in memory database, and returning the confirmation receiving these data to client.
Wherein, these data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.
Preferably,
From server also for, when master server breaks down, switch to master server to carry out work, and before handover by receive from client and untreated data process.
Preferably, from server also for,
When described master server breaks down, the first notification message that this master server receiving the transmission of described master server breaks down, and after described master server recovers normally, receive normal second notification message of this master server recovery that described master server sends, and receive and the data processed from server described in during breaking down to the described master server that described master server sends.
When described from server fail time, this third notice message from server fail is sent to described master server, and recover normal from server described send should recover normal 4th notification message from server to described master server afterwards, and describedly receiving and the data processed from described master server during server fail of receiving that described master server sends.
Preferably,
From server also for, when not breaking down from server, when the quantity of the data backed up in memory database reaches default storage threshold, the data that back up in process memory database, and by the data conversion storage after process in non-memory database.
Compared with prior art, the present invention includes: these data are backuped in memory database, and return the confirmation receiving these data to client by the data sent from server receives client.Wherein, these data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.By the solution of the present invention, when conventional hot standby two-shipper can be avoided to be in same machine room, go wrong once this machine room, whole service system is paralysed, have a strong impact on the problem of user's application.
Accompanying drawing explanation
Be described the accompanying drawing in the embodiment of the present invention below, the accompanying drawing in embodiment is for a further understanding of the present invention, is used from explanation the present invention, does not form limiting the scope of the invention with instructions one.
Fig. 1 is data processing method process flow diagram of the present invention;
Fig. 2 is traditional two-node cluster hot backup scheme topology and two-node cluster hot backup scheme topology comparison diagram of the present invention;
Fig. 3 is data processing structure figure of the present invention;
Fig. 4 is data processing server end composition frame chart of the present invention.
Embodiment
For the ease of the understanding of those skilled in the art, below in conjunction with accompanying drawing, the invention will be further described, can not be used for limiting the scope of the invention.
The present invention proposes a kind of offsite active standby hot reserve scheme according to problems of the prior art, and when somewhere goes wrong, another place can provide service in time, and user can not be subject to obvious impact.
Particularly, in order to achieve the above object, the present invention proposes a kind of data processing method, as shown in Figure 1, Figure 3, the method comprises:
S101, master server receive the data that client sends, and process these data, and the data after process are returned described client.
Preferably, the method also comprises:
When master server breaks down, be that master server carries out work from Server switching, and before handover by receive from client and untreated data process, to receive new data.
Preferably, the method also comprises:
When master server breaks down, master server sends the first notification message to from server, the message informing broken down is from server, and recover normal at master server and send the second notification message to from server afterwards, master server is recovered normal message informing from server, and reception receives and the data processed from server during the master server that server sends breaks down.
These data are backuped in memory database, and return the confirmation receiving these data to client by S102, the data sent from server receives client.
Wherein, data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.
Preferably, the method also comprises:
When from server fail, master server continues the data receiving client transmission, processes these data, and the data after process are returned client.That is, master server receives and to process the mode of client data constant.
Preferably, the method also comprises:
When master server breaks down, from the first notification message that this master server of server reception master server transmission breaks down, and after master server recovers normally, receive normal second notification message of this master server recovery that master server sends, and receive and the data processed from server during the master server that master server sends breaks down.
When from server fail, this third notice message from server fail is sent from server to master server, and send should recover normal 4th notification message from server to master server afterwards recovering normal from server, and receiving and the data processed from master server during server fail of receiving that master server sends.
Preferably, the method also comprises:
When not breaking down from server, when the quantity of the data backed up in memory database reaches default storage threshold, the data backed up from server process memory database, and by the data conversion storage after process in non-memory database.In embodiments of the present invention, master server and being placed in respectively in different machine rooms from server.As shown in Figure 2, wherein, (a) is traditional two-node cluster hot backup scheme topological diagram, and (b) is two-node cluster hot backup scheme topological diagram of the present invention.Further, can be one or more from server, all be positioned in different machine rooms from master server.
In addition, in embodiments of the present invention, a control end can also be there is, this control end can be client, master server, or an access point etc., this control end is responsible for confirming master server and is all received from server the data that client sends, and when receiving master server and from the returning results of server, is only a complete data upload and to the process returning results confirmation.
Here it should be noted that, above-mentioned step S101 and S102 does not have dividing of sequencing, master server and from server can simultaneously by control end receive client send data and return results, also can not simultaneously receive, master server and from server by control end receive client send data be separate.
Compared with traditional scheme: the present invention program to be different from traditional two-node cluster hot backup scheme principal and subordinate's server in the situation of a machine room, master server and dividing from server is placed in different machine rooms.Like this, when link fails, also can switch in time and service is provided; Master server and from the probability that server breaks down simultaneously be Single-Server probability of happening square, more stable service can be provided.
In order to achieve the above object, the invention allows for a kind of data processing server end 01, as shown in Figure 4, this server end comprises master server 011 and one or more from server 012.
The data that master server 011 sends for receiving client, process these data, and the data after process are returned described client.
From the data that server 012 sends for receiving client, these data being backuped in memory database, and returns the confirmation receiving these data to client.
Wherein, these data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.
Preferably,
From server 012 also for, when master server 011 breaks down, switch to master server 011 to carry out work, and before handover by receive from client and untreated data process.
Master server 011 also for, when breaking down from server 012, continue receive client send data, these data are processed, and by process after data return client.
Preferably,
Master server 011 also for, when master server 011 breaks down, the first notification message is sent to from server 012, the message informing broken down by master server 011 is from server 012, and recover normal at master server 011 and send the second notification message to from server 012 afterwards, master server 011 is recovered normal message informing from server 012, and reception receives and the data processed from server 012 during the master server 011 that server 012 sends breaks down.
From server 012 also for:
When master server 011 breaks down, the first notification message that this master server 011 receiving master server 012 transmission breaks down, and this master server 011 receiving master server 011 transmission after master server 011 recovers normally recovers normal second notification message, and receive and the data processed from server 012 during the master server 011 that master server 011 sends breaks down.
When breaking down from server 012, this third notice message broken down from server 012 is sent to master server 011, and send should recover normal 4th notification message from server 012 to master server 011 afterwards recovering normal from server 012, and receiving and the data processed from break down period master server 011 of server 012 of receiving that master server 011 sends.
Preferably,
From server 012 also for, when not breaking down from server 012, when the quantity of the data backed up in memory database reaches default storage threshold, the data backed up in process memory database, and by the data conversion storage after process in non-memory database.
Compared with prior art, the present invention includes: these data are backuped in memory database, and return the confirmation receiving these data to client by the data sent from server receives client.Wherein, these data are identical with the data that client sends to master server; Be placed in respectively in different machine rooms from server and master server.By the solution of the present invention, when conventional hot standby two-shipper can be avoided to be in same machine room, go wrong once this machine room, whole service system is paralysed, have a strong impact on the problem of user's application.
It should be noted that; above-described embodiment is only understand for the ease of those skilled in the art; be not limited to protection scope of the present invention; under the prerequisite not departing from inventive concept of the present invention, any apparent replacement and improvement etc. that those skilled in the art make the present invention are all within protection scope of the present invention.
Claims (8)
1. a data processing method, is characterized in that, described method comprises:
Receive the described data of described client transmission from server, described data are stored in memory database, and return the confirmation receiving described data to described client;
Wherein, described data are identical with the data that described client sends to master server; Describedly to be placed in respectively in different machine rooms from server and master server.
2. data processing method as claimed in claim 1, it is characterized in that, described method also comprises:
When described master server breaks down, described is that described master server carries out work from Server switching, and before handover by receive from described client and untreated described data process.
3. data processing method as claimed in claim 2, it is characterized in that, described method also comprises:
When described master server breaks down, the first notification message that described this master server receiving the transmission of described master server from server breaks down, and after described master server recovers normally, receive normal second notification message of this master server recovery that described master server sends, and receive and the data processed from server described in during breaking down to the described master server that described master server sends;
When described from server fail time, describedly send this third notice message from server fail from server to described master server, and recover normal from server described send should recover normal 4th notification message from server to described master server afterwards, and describedly receiving and the data processed from described master server during server fail of receiving that described master server sends.
4. data processing method as claimed in claim 2, it is characterized in that, described method also comprises:
Described do not break down from server time, when the quantity of the described data backed up in described memory database reaches default storage threshold, the described described data backed up from memory database described in server process, and by the described data conversion storage after process in non-memory database.
5. a data processing server end, is characterized in that, described server end comprises master server and one or more from server;
Described data are stored in memory database, and return the confirmation receiving described data to described client by the described described data sent for receiving described client from server;
Wherein, described data are identical with the data that described client sends to master server; Describedly to be placed in respectively in different machine rooms from server and described master server.
6. server end as claimed in claim 5, is characterized in that,
Described from server also for, when described master server breaks down, switch to described master server to carry out work, and before handover by receive from described client and untreated described data process.
7. server end as claimed in claim 6, is characterized in that, described from server also for,
When described master server breaks down, the first notification message that this master server receiving the transmission of described master server breaks down, and after described master server recovers normally, receive normal second notification message of this master server recovery that described master server sends, and receive and the data processed from server described in during breaking down to the described master server that described master server sends;
When described from server fail time, this third notice message from server fail is sent to described master server, and recover normal from server described send should recover normal 4th notification message from server to described master server afterwards, and describedly receiving and the data processed from described master server during server fail of receiving that described master server sends.
8. server end as claimed in claim 6, is characterized in that,
Described from server also for, described do not break down from server time, when the quantity of the described data backed up in described memory database reaches default storage threshold, process in described memory database the described data backed up, and by the described data conversion storage after process in non-memory database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510524312.7A CN105159796A (en) | 2015-08-24 | 2015-08-24 | Data processing method and server end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510524312.7A CN105159796A (en) | 2015-08-24 | 2015-08-24 | Data processing method and server end |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105159796A true CN105159796A (en) | 2015-12-16 |
Family
ID=54800658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510524312.7A Pending CN105159796A (en) | 2015-08-24 | 2015-08-24 | Data processing method and server end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105159796A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108243209A (en) * | 2016-12-23 | 2018-07-03 | 深圳市优朋普乐传媒发展有限公司 | A kind of method of data synchronization and device |
| CN109213631A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | A kind of transaction methods, device, equipment and readable storage medium storing program for executing |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060294207A1 (en) * | 2005-06-09 | 2006-12-28 | International Business Machines Corporation | Apparatus and method for autonomically adjusting configuration parameters for a server when a different server fails |
| CN101414917A (en) * | 2007-10-19 | 2009-04-22 | 华为技术有限公司 | Method for saving internal memory space, data management network element and network system |
| CN103067206A (en) * | 2012-12-28 | 2013-04-24 | 无锡博欧节能科技有限公司 | Internet of things across-machine room distributed type full automatic hot standby server switching system |
-
2015
- 2015-08-24 CN CN201510524312.7A patent/CN105159796A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060294207A1 (en) * | 2005-06-09 | 2006-12-28 | International Business Machines Corporation | Apparatus and method for autonomically adjusting configuration parameters for a server when a different server fails |
| CN101176073A (en) * | 2005-06-09 | 2008-05-07 | 国际商业机器公司 | Adjusting configuration parameters for a server when a different server fails |
| CN101414917A (en) * | 2007-10-19 | 2009-04-22 | 华为技术有限公司 | Method for saving internal memory space, data management network element and network system |
| CN103067206A (en) * | 2012-12-28 | 2013-04-24 | 无锡博欧节能科技有限公司 | Internet of things across-machine room distributed type full automatic hot standby server switching system |
Non-Patent Citations (1)
| Title |
|---|
| ZHANG 988119: "XXXX数据库***双机双柜解决方案", 《百度文库》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108243209A (en) * | 2016-12-23 | 2018-07-03 | 深圳市优朋普乐传媒发展有限公司 | A kind of method of data synchronization and device |
| CN109213631A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | A kind of transaction methods, device, equipment and readable storage medium storing program for executing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106331098B (en) | Server cluster system | |
| EP3493471B1 (en) | Data disaster recovery method, apparatus and system | |
| EP2648114A1 (en) | Method, system, token conreoller and memory database for implementing distribute-type main memory database system | |
| CN104158693A (en) | A method and a system for disaster recovery backup of data service | |
| CN103441863B (en) | The hot standby system of two server and control method in a kind of air traffic control automation system | |
| EP2902922B1 (en) | Distributed file system and data backup method for distributed file system | |
| CN102752093B (en) | Based on the data processing method of distributed file system, equipment and system | |
| CN113051110A (en) | Cluster switching method, device and equipment | |
| CN106656589A (en) | Server dual hot backup system | |
| CN104901983B (en) | A kind of information synchronization method, apparatus and system | |
| CN106407045B (en) | A kind of data disaster restoration methods, system and server virtualization system | |
| CN105095008A (en) | Distributed task fault redundancy method suitable for cluster system | |
| CN105007193A (en) | Multi-layer information processing method, system thereof and cluster management node | |
| CN105049263A (en) | Data processing method and data processing system | |
| CN104967691A (en) | Distributed storage control method and system | |
| CN105049264A (en) | Data processing method and server side | |
| CN110351313B (en) | Data caching method, device, equipment and storage medium | |
| CN103916226A (en) | Redundant backup method based on embedded equipment | |
| CN105162560A (en) | Data processing method and system | |
| CN105159796A (en) | Data processing method and server end | |
| CN106201772A (en) | The backup of a kind of operating system based on data center, restoration methods and device | |
| CN106712997B (en) | Method, equipment and system for recovering table entry | |
| CN103605616A (en) | Multi-controller cache data consistency guarantee method | |
| CN112052127B (en) | Data synchronization method and device for dual-computer hot standby environment | |
| CN204406385U (en) | The management devices of computer system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20151216 |