You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Haihui Xu (Jira)" <ji...@apache.org> on 2021/06/01 01:59:00 UTC
[jira] [Updated] (RANGER-3302) GetAuthzEvents should check if
auditProvider is null
[ https://issues.apache.org/jira/browse/RANGER-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Haihui Xu updated RANGER-3302:
------------------------------
Description:
Process the auditlog，need to getAuditProvider and getAuthzEvents, when logAuthzAudit, the code is
if (auditProvider == null || !auditProvider.log(auditEvent)) {
MiscUtil.logErrorMessageByInterval(LOG, "fail to log audit event " + auditEvent);
}
so, when getAuthzEvents should check auditProvider value, when auditProvider is null, there is no need to construct auditEvent, which is time-consuming and will result in the performance decline of service(kakfa broker,namenode, hiveserver2...)
> GetAuthzEvents should check if auditProvider is null
> ----------------------------------------------------
>
> Key: RANGER-3302
> URL: https://issues.apache.org/jira/browse/RANGER-3302
> Project: Ranger
> Issue Type: Improvement
> Components: audit
> Affects Versions: 2.1.0
> Reporter: Haihui Xu
> Assignee: Haihui Xu
> Priority: Major
> Fix For: 2.2.0
>
>
> Process the auditlog，need to getAuditProvider and getAuthzEvents, when logAuthzAudit, the code is
> if (auditProvider == null || !auditProvider.log(auditEvent)) {
> MiscUtil.logErrorMessageByInterval(LOG, "fail to log audit event " + auditEvent);
> }
> so, when getAuthzEvents should check auditProvider value, when auditProvider is null, there is no need to construct auditEvent, which is time-consuming and will result in the performance decline of service(kakfa broker,namenode, hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)