Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.0 |  CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 

cubrid applyinfo

Description

This utility is used to check the copied and applied status of replication logs by CUBRID HA.

Syntax

cubrid applyinfo [option] <database-name>

  • database-name: Specifies the name of a server to check. A node name is not included.
Options

Option

Default

Description

-r

none

Configures the name of a target node in which transaction logs are copied. Using this option will output the information of active logs (Active Info.) of a target node.

-a

 

Outputs the information of replication reflection of a node executing cubrid applyinfo. The -L option is required to use this option.

-L

none

Configures the location of transaction logs copied from the other node. Using this option will output the information of transaction logs copied (Copied Active Info.) from the other node.

-p

0

Outputs the information of a specific page in the copied logs. This is available only when the -L option is enabled.

-v

 

Outputs detailed information.

-i

 

Periodically  Outputs the copied and applied statuses of transaction logs per specified seconds. To output the information of log status by which the replication is delayed, this option is mandatory.

Example

The following example shows how to check log information (Active Info.) of the master node, the copylogdb information (Copied Active Info.) of the slave node, and the applylogdb info (Applied Info.) of the slave node by executing applyinfo in the slave node.

  • Applied Info.: Shows the status information after the slave node applies the replication log.
  • Copied Active Info.: Shows the status information after the slave node copies the replication log.
  • Active Info.: Shows the status information after the master node records the transaction log.
  • Delay in Copying Active Log: Shows the status information which the transaction logs’ copy is delayed.
  • Delay in Applying Copied Log: Shows the status information which the transaction logs’ application is delayed.

[nodeB] $ cubrid applyinfo -L /home/cubrid/DB/testdb_nodeA -r nodeA -a -i 3 testdb

 

 *** Applied Info. ***

Insert count                   : 289492

Update count                   : 71192

Delete count                   : 280312

Schema count                   : 20

Commit count                   : 124917

Fail count                     : 0

 

 *** Copied Active Info. ***

DB name                        : testdb

DB creation time               : 04:29:00.000 PM 11/04/2012 (1352014140)

EOF LSA                        : 27722 | 10088

Append LSA                     : 27722 | 10088

HA server state                : active

 

 ***  Active Info. ***

DB name                        : testdb

DB creation time               : 04:29:00.000 PM 11/04/2012 (1352014140)

EOF LSA                        : 27726 | 2512

Append LSA                     : 27726 | 2512

HA server state                : active

 

 *** Delay in Copying Active Log ***

Delayed log page count         : 4

Estimated Delay                : 0 second(s)

 

 *** Delay in Applying Copied Log ***

Delayed log page count         : 1459

Estimated Delay                : 22 second(s)

The items shown by each status are as follows:

  • Applied Info.
    • Committed page: The information of committed pageid and offset of a transaction reflected last through replication log reflection process. The difference between this value and the EOF LSA of "Copied Active Info. represents the amount of replication delay.
    • Insert Count: The number of Insert queries reflected through replication log reflection process.
    • Update Count: The number of Update queries reflected through replication log reflection process.
    • Delete Count: The number of Delete queries reflected through replication log reflection process.
    • Schema Count: The number of DDL statements reflected through replication log reflection process.
    • Commit Count: The number of commits reflected through replication log reflection process.
    • Fail Count: The number of DML and DDL statements in which log reflection through replication log reflection process fails.
  • Copied Active Info.
    • DB name: Name of a target database in which the replication log copy process copies logs
    • DB creation time: The creation time of a database copied through replication log copy process
    • EOF LSA: Information of pageid and offset copied at the last time on the target node by the replication log copy process. There will be a delay in copying logs as much as difference with the EOF LSA value of "Active Info." and with the Append LSA value of "Copied Active Info."
    • Append LSA: Information of pageid and offset written at the last time on the disk by the replication log copy process. This value can be less than or equal to EOF LSA. There will be a delay in copying logs as much as difference between the EOF LSA value of "Copied Active Info." and this value.
    • HA server state: Status of a database server process which replication log copy process receives logs from. For details on status, see Server.
  • Active Info.
    • DB name: Name of a database of which node was configured in the -r option.
    • DB creation time: Database creation time of a node that is configured in the -r option.
    • EOF LSA: The last information of pageid and offset of a database transaction log of a node that is configured in the -r option. There will be a delay in copying logs as much as difference between the EOF LSA value of "Copied Active Info." and this value.
    • Append LSA: Information of pageid and offset written at the last time on the disk by the database of which node was configured in the -r option.
    • HA server state: The server status of a database server of which node was configured in the -r option.
  • Delay in Copying Active Log

    • Delayed log page count: the count of transaction log pages which the copy is delayed.

    • Estimated Delay: the expected time which the logs copying is completed.

  • Delay in Applying Copied Log

    • Delayed log page count: the count of transaction log pages which the application is delayed.

    • Estimated Delay: the expected time which the logs applying is completed.