KBI 312174 Issue Addressed: Primary Generator Runs Out Of Disk Space When Secondary Generators Are Deployed
Version
Argent Omega 2.2A-2401-A and earlier
Date
Thursday, 13 June 2024
Summary
When deployed, Secondary Generators periodically uploads runtime data including Relator trace log, connectivity status, network scan results, etc. to the Primary Generator
The Primary Generator then updates SQL database
The runtime data is compressed before uploading. The compressed files can be found in RUNTIME folder on Secondary Generator side, and WO\{Secondary Generator Name} on Primary Generator side.
It has been identified that Secondary Generator has resource leak during the process. The obvious symptoms include:
- There are more and more compressed files (*.Z) accumulated in WO\{Secondary Generator Name} on Primary Generator side.
- The size of compressed file (*.Z) grows over time.
- Memory usage of process ‘ArgentOmegaMain.exe’ grows on both Primary Generator and Secondary Generator sides.
- CPU usage might be affected as well.
In the extreme scenario, Primary Generator can run out of disk space because of too many *.Z files not processed
The issue has been addressed in Argent Omega 2.2A-2404-A
Technical Background
The issue is caused by coding error
Resolution
Upgrade to Argent Omega 2.2A-2404-A or later