[jira] [Updated] (RANGER-3603) HDFS audit files rollover improvement to trigger rollover in monitoring thread

["Ramesh Mani (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RANGER-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Mani updated RANGER-3603:
--------------------------------
    Affects Version/s: 2.3.0
                           (was: 2.2.0)

> HDFS audit files rollover improvement to trigger rollover in monitoring thread
> ------------------------------------------------------------------------------
>
>                 Key: RANGER-3603
>                 URL: https://issues.apache.org/jira/browse/RANGER-3603
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: RANGER-3603.rtf
>
>
> HDFS audit files rollover improvement to trigger rollover in monitoring thread. Currently file rollover happens based on the audit event occurrence. If there are no event happening, then the created hdfs or any cloud location audit file will be kept opened until an auditing event occurs. This result in files that are opened beyond the configured rollover time. e.g if the file rollover time is 1 day, some files are kept opened beyond 1 day. This may cause some inconvenience when audit files are read by an external tools for analysis on a daily basis.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)