Overview

You have noticed that one of the Cloud LGPs (e.g. LGP 2) is not updating and the last log is from a month ago.

Solution

Check the output of tp_walk --tp_lgp lgpStatus from all LGP nodes.

The output should look similar to the example provided below:

[textpass@RMD-SMSC_LGP-01 ~]$ tp_walk --tp_lgp lgpStatus
lgpDbSize.0 = VVV: 722292237
............................................................
[textpass@RMD-SMSC_LGP-02 ~]$ tp_walk --tp_lgp lgpStatus
lgpDbSize.0 = VVV: 14564531330
.......................................................
[textpass@RMD-SMSC_LGP-03 ~]$ tp_walk --tp_lgp lgpStatus
lgpDbSize.0 = VVV: 297462130
.............................................................
[textpass@RMD-SMSC_LGP-04 ~]$ tp_walk --tp_lgp lgpStatus
lgpDbSize.0 = VVV: 421153724

The fact that a certain LGP is not collecting and processing log records might be because the database has the largest size among the other LGPs. The LGP process syncs up and coordinates the data collection with the other LGPs to have databases of equivalent sizes. It will take some time until all LGPs' DBs are equivalent. In the example above, LGP 2 has the largest size as seen in the output which is causing a lag in its updates.

If you find that the database sizes are equivalent among all LGPs, contact support for further assistance.