Menu

#2239 log: no housekeeping for cfg files

5.2.FC
fixed
None
enhancement
log
-
major
2017-02-24
2016-12-21
No

At the moment, LOGsv takes care of the housekeeping of the log files, but not for cfg files.

So, if we play with log streams in a long time, or we encounter an cyclic reboots of SCs,
a large numbers of cfg files are generated even log files that go along with them have been removed due to rotation.

Related

Tickets: #2239
Wiki: NEWS-5.2.0

Discussion

  • A V Mahesh (AVM)

    • status: unassigned --> accepted
    • assigned_to: A V Mahesh (AVM)
     
  • A V Mahesh (AVM)

    On 1/9/2017 6:43 PM, Lennart Lund wrote:

    Hi

    A .cfg file is created when a stream is created and it belongs to the log files owned by that stream. If the stream (application runtime) is closed by all the clients the stream is deleted an all its files are closed including the current log file. The files are not deleted and can be seen as a package of log records that includes the .cfg file and all log files that belonged to the stream. The .cfg file is still valid and contains information about how to read the log files. In this case the .cfg file cannot be removed.

    If a configuration of a stream is changed (configuration stream) a new .cfg file is created. Also the current log file is closed and a new current log file is created. Logging is now based on the new settings. The old log files however is not deleted and the old .cfg file is still needed since it contains information about how to read the old log files (file before the change). In this case the old log files will eventually be replaced by log files with the new setting since they are still part of the file rotation. This means that when the last old log file has been rotated out also the old .cfg file can be removed (but not before that).

    Regards
    Lennart

    On 1/10/2017 9:31 AM, A V Mahesh wrote:

    Hi Lennart,

    Thanks for the inputs.

    I did also went through SAI-AIS-LOG-A.02.01 specification to finalized/decided approach on .cfg ROTATE,
    I did find cfg File Naming Rules are defined in the specification but not the ROTATE /polices/for .cfg.

    So it is now up to implementation to define , as you suggested the .cfg file
    can also be ROTATED concurrently whenever the log files with the same <closetime> suffix
    is being ROTATED and it looks idle implementation and better approach.

    -AVM

     
  • A V Mahesh (AVM)

    • status: accepted --> review
     
  • A V Mahesh (AVM)

    • status: review --> fixed
     
  • A V Mahesh (AVM)

    changeset: 8614:0623f817f002
    tag: tip
    user: A V Mahesh mahesh.valla@oracle.com
    date: Fri Feb 24 09:41:04 2017 +0530
    summary: logd: implement cfg files rotation [#2239]

     

    Related

    Tickets: #2239


Log in to post a comment.