Enhancement #13381
Data Offload huge log file causing CPU high
| Status: | Closed - End of life cycle | Start date: | January 05, 2023 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% | ||
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Problem:
The offload program will grows the log file fast because every minutes contain huge number of transaction come in. Therefore, huge log file size will causing the I/O become slow and CPU will getting high.
Solution:
Change the log file to roll by file size with 1 file size maximum 100MB and max file size is 10 file per day. Also remove all the debug log, only left the error log to show in the log file.
Action:
Update log4j2 setting to roll by file size.
Last status:
Already provided patch to PTAP and deployed to NFT
History
#1
Updated by Bramantyo Pujo Wiyono over 1 year ago
After several testing, the rolling file for the new setting is still not work as we expected. so will hold the Release [20221223_01] - Update Log4j2 settings. and replace it with only update log level to error for Data Offloading
#2
Updated by Tan Lee Yong about 1 year ago
- Assignee changed from Ngoh Chee Ping to Rayvandy Gabbytian
Reassign to Gabby to follow up
#3
Updated by Rayvandy Gabbytian about 1 year ago
- Status changed from Pending Prod Deployment to Closed - End of life cycle
deployed to production 28/05/2023