Point-to-point database synchronization over a transport protocol
A mechanism includes receiving, at a local node, a Hello message including an application identifier (AppId) and a target link between a target port for a local node and target port for a neighbor node. The local node determines the AppId is associated with an application for performing database synchronization. The local node sets up a local database in memory at the local node as part of a database pair for use by the application, the database pair including a neighbor database at the neighbor node. The local node associates the database pair with the target link. The local node controls synchronization of the local database with the neighbor database via the target link.
1 . A method implemented in a local node, comprising:
generating a disconnected code for an application, the disconnected code indicating that an exchange of Hello Link-Local Registration Protocol Data Unit (LRPDU) messages has failed;
processing an applicant database at the local node according to the application's response to the disconnected code;
receiving a Complete List LRPDU message from a registrar database at a peer node, the Complete List LRPDU message including record headers for all records at the registrar database; and
comparing the record headers from the Complete List LRPDU message with record headers in the applicant database.
2 . The method of claim 1 , further comprising: resetting notify timers for the applicant database.
3 . The method of claim 1 , further comprising:
determining if there is a mismatch between one or more record headers in the applicant database and one or more record headers from the Complete List LRPDU message; and
transmitting a Record LRPDU message toward the registrar database, the Record LRPDU message containing updated record headers if there is a mismatch.
4 . The method of claim 1 , further comprising:
determining no mismatch between record headers in the applicant database and record headers from the registrar database; and
based on the determination of no mismatch, notifying the application that the applicant database is synchronized with the registrar database.
5 . The method of claim 1 , where the applicant database is associated with the registrar database.
6 . The method of claim 1 , where the Complete List LRPDU message comprises an application identifier (AppId) identifying the application.
7 . The method of claim 1 , wherein the Complete List LRPDU message comprises a My Chassis identifier (ID) identifying the local node, a My Port ID identifying a target port on the local node, a Neighbor Chassis ID identifying the peer node, and a Neighbor Port ID identifying a target port on the peer node.
8 . The method of claim 1 , further comprising:
transmitting one or more Record LRPDU messages toward the registrar database, the Record LRPDU messages indicating updates to records stored in the applicant database;
receiving one or more LRPDU messages acknowledging the Record LRPDU messages;
marking at least one updated record in the applicant database as acknowledged by the registrar database; and
notifying the application that the applicant database is synchronized with the registrar database.
9 . The method of claim 8 , further comprising:
determining that all updated records in the applicant database are acknowledged by the registrar database via LRPDU messages, wherein the notifying the application that the applicant database is synchronized with the registrar database is initiated based on the determination that all updated records in the applicant database are acknowledged by the registrar database via LRPDU messages.
10 . The method of claim 8 , wherein the LRPDU messages acknowledging the Record LRPDU messages include a Partial List LRPDU message.
11 . The method of claim 10 , where the Partial List LRPDU message comprises at least one record header acknowledging the at least one updated record.
12 . The method of claim 11 , wherein the record header includes a record number indicating the updated record and a sequence number identifying an update included in the updated record.
13 . The method of claim 8 , wherein the LRPDU messages acknowledging the Record LRPDU messages include a Complete List LRPDU message, the Complete List LRPDU message including record headers for all records at the registrar database.
14 . The method of claim 8 , wherein the Record LRPDU messages comprise one or more record numbers indicating records updated at the applicant database and one or more sequence numbers identifying updates included in the records updated at the applicant database.
15 . The method of claim 1 , further comprising:
generating a failure notification to the application when a Record LRPDU message timer expires without receiving a corresponding Partial List LRPDU message.
16 . The method of claim 15 , wherein the Complete List LRPDU message includes a first record number field indicating the first record stored at the registrar database and a last record number field indicating the last record stored at the registrar database, and wherein the record headers include record numbers indicating the records stored at the registrar database and sequence numbers identifying updates included in the records stored at the registrar database.
17 . The method of claim 1 , further comprising:
transmitting a Request Complete List LRPDU message toward the registrar database; and
receiving a Complete List LRPDU message from the registrar database in response to the Request Complete List LRPDU message.
18 . A local node comprising:
a transmitter and a processor coupled to the transmitter, the local node configured to:
generate a disconnected code for an application, the disconnected code indicating that an exchange of Hello Link-Local Registration Protocol Data Unit (LRPDU) messages has failed;
process an applicant database at the local node according to the application's response to the disconnected code
receive a Complete List LRPDU message from a registrar database at a peer node, the Complete List LRPDU message including record headers for all records at the registrar database; and
compare the record headers from the Complete List LRPDU message with record headers in the applicant database.
19 . The local node of claim 18 , wherein the local node is further configured to reset notify timers for the applicant database.
20 . The local node of claim 18 , wherein the local node is further configured to:
determine a mismatch between one or more record headers in the applicant database and one or more record headers from the Complete List LRPDU message; and
transmit a Record LRPDU message toward the registrar database, the Record LRPDU message containing updated record headers addressing the mismatch.
21 . The local node of claim 18 , wherein the local node is further configured to:
determine no mismatch between record headers in the applicant database and record headers from the registrar database; and
based on the determination of no mismatch, notify the application that the applicant database is synchronized with the registrar database.
22 . The local node of claim 18 , where the applicant database is associated with the registrar database.
23 . The local node of claim 18 , where the Complete List LRPDU message comprises an application identifier (AppId) identifying the application.
24 . A system comprising:
a local first node;
a peer node communicating with the first node; and
wherein the first node is configured to:
generate a disconnected code for an application, the disconnected code indicating that an exchange of Hello Link-Local Registration Protocol Data Unit (LRPDU) messages has failed;
process an applicant database at the local node according to the application's response to the disconnected code;
receive a Complete List LRPDU message from a registrar database at the peer node, the Complete List LRPDU message including record headers for all records at the registrar database; and
compare the record headers from the Complete List LRPDU message with record headers in the applicant database.