Troubleshooting Backlogs at CHN Collectors Due to Full Utilization on the Pri Viewer For Tataplay

Overview

The issue pertains to backlogs being created at CHN collectors due to full utilization on the Pri viewer. This can prevent the normal operation of the system and cause significant operational issues. The customer may experience a slowdown in system performance and an inability to process files as expected.

Recording: Explaining the issue

Ticket: 4141959

Solution

To resolve the issue, the following steps were taken:

1. A new parallel instance was created to clear the backlog.
2. A new directory, Processing-output-bkp parallel, was created at path /u01/NATDATA/SYSLOG/JUNIPER/.
3. 
4. The current configuration was copied with the command: cp -r 000/ 001/.
5. The backlog path in the distribution-service.xml was updated.
6. The service running on port 5504 was restarted.
7. 
8. The backlog processing status was validated and it was found that the files were processing fine.
9. 

The team continued to monitor the situation until the backlog was fully cleared.

Summary

The issue of backlogs being created at CHN collectors due to full utilization on the Pri viewer was resolved by creating a new parallel instance, updating the backlog path in the distribution-service.xml file, and restarting the service running on port 5504. The backlog processing status was then validated and monitored until the backlog was fully cleared.

FAQ

1. What causes backlogs at CHN collectors?
   Backlogs at CHN collectors can be caused by full utilization on the Pri viewer, which can prevent the normal operation of the system.
2. How can the backlog be cleared?
   The backlog can be cleared by creating a new parallel instance, updating the backlog path in the distribution-service.xml file, and restarting the service running on a specific port.
3. What happens after the service is restarted?
   After the service is restarted, the backlog processing status is validated and monitored until the backlog is fully cleared.