[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu updated RANGER-2676: -- Priority: Trivial (was: Critical) > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Trivial > Labels: patch > Fix For: 1.2.1 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-2676: - Fix Version/s: (was: 2.0.0) > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Labels: patch > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu updated RANGER-2676: -- Labels: patch (was: ) > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Labels: patch > Fix For: 2.0.0 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu updated RANGER-2676: -- Attachment: RANGER-2676.patch > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Fix For: 2.0.0 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu updated RANGER-2676: -- Description: When after evalute policy and then process the auditlog，need to obtain AuditHandler Object and AuthzAuditEvent object (1) AuditHandler object obtained when init plugin according to the value of xasecure.audit.destination.db/solr/hdfs/... (2) So, obtaining AuthzAuditEvent should also according to the value of xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or dummyHandler, constructing AuthzAuditEvent object is useless which is very frequently called and thus result in the performance decline of service(hdfs namenode, kakfa broker,hiveserver2...) was: When after evalute policy and then process the auditlog，need to obtain AuditHandler Object and AuthzAuditEvent object (1）AuditHandler object obtained when init plugin according to the value of xasecure.audit.destination.db/solr/hdfs/... (2) So, obtaining AuthzAuditEvent should also according to the value of xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or dummyHandler, constructing AuthzAuditEvent object is useless which is very frequently called and thus result in the performance decline of service(hdfs namenode, kakfa broker,hiveserver2...) > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Fix For: 2.0.0 > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[
https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haihui Xu updated RANGER-2676:
--
Description:
When after evalute policy and then process the auditlog，need to obtain
AuditHandler Object and AuthzAuditEvent object
(1）AuditHandler object obtained when init plugin according to the value of
xasecure.audit.destination.db/solr/hdfs/...
(2) So, obtaining AuthzAuditEvent should also according to the value of
xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or
dummyHandler, constructing AuthzAuditEvent object is useless which is very
frequently called and thus result in the performance decline of service(hdfs
namenode, kakfa broker,hiveserver2...)
was:
When after evalute policy and then process the auditlog，need to obtain
AuditHandler Object and AuthzAuditEvent object
(1）AuditHandler object obtained when init plugin according to the value of
xasecure.audit.destination.{db/solor...}
(2) So, obtaining AuthzAuditEvent should also according to the value of
xasecure.audit.destination.{db/solor...},or when AuditHandler is null or
dummyHandler, constructing AuthzAuditEvent object is useless which is very
frequently called and thus result in the performance decline of service(hdfs
namenode, kakfa broker,hiveserver2...)
> Before obtaining AuthzAuditEvent Object should check
> xasecure.audit.destination.xx value
>
>
> Key: RANGER-2676
> URL: https://issues.apache.org/jira/browse/RANGER-2676
> Project: Ranger
> Issue Type: Improvement
> Components: audit, plugins
>Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Critical
> Fix For: 2.0.0
>
>
> When after evalute policy and then process the auditlog，need to obtain
> AuditHandler Object and AuthzAuditEvent object
> (1）AuditHandler object obtained when init plugin according to the value of
> xasecure.audit.destination.db/solr/hdfs/...
> (2) So, obtaining AuthzAuditEvent should also according to the value of
> xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or
> dummyHandler, constructing AuthzAuditEvent object is useless which is very
> frequently called and thus result in the performance decline of service(hdfs
> namenode, kakfa broker,hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[
https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haihui Xu updated RANGER-2676:
--
Description:
When after evalute policy and then process the auditlog，need to obtain
AuditHandler Object and AuthzAuditEvent object
(1）AuditHandler object obtained when init plugin according to the value of
xasecure.audit.destination.{db/solor...}
(2) So, obtaining AuthzAuditEvent should also according to the value of
xasecure.audit.destination.{db/solor...},or when AuditHandler is null or
dummyHandler, constructing AuthzAuditEvent object is useless which is very
frequently called and thus result in the performance decline of service(hdfs
namenode, kakfa broker,hiveserver2...)
was:
When after evalute policy and then process the auditlog，need to obtain
AuditHandler Object and AuthzAuditEvent object
(1）AuditHandler object obtained when init plugin according to the value of
xasecure.audit.destination.{db/solor...}
(2) So, obtaining AuthzAuditEvent should also according to the value of
xasecure.audit.destination.{db/solor...}, or when AuditHandler is null or
dummyHandler, constructing AuthzAuditEvent object is useless which is very
frequently called and thus result in the performance decline of service(hdfs
namenode, kakfa broker,hiveserver2...)
> Before obtaining AuthzAuditEvent Object should check
> xasecure.audit.destination.xx value
>
>
> Key: RANGER-2676
> URL: https://issues.apache.org/jira/browse/RANGER-2676
> Project: Ranger
> Issue Type: Improvement
> Components: audit, plugins
>Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Critical
> Fix For: 2.0.0
>
>
> When after evalute policy and then process the auditlog，need to obtain
> AuditHandler Object and AuthzAuditEvent object
> (1）AuditHandler object obtained when init plugin according to the value of
> xasecure.audit.destination.{db/solor...}
> (2) So, obtaining AuthzAuditEvent should also according to the value of
> xasecure.audit.destination.{db/solor...},or when AuditHandler is null or
> dummyHandler, constructing AuthzAuditEvent object is useless which is very
> frequently called and thus result in the performance decline of service(hdfs
> namenode, kakfa broker,hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[
https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haihui Xu updated RANGER-2676:
--
Summary: Before obtaining AuthzAuditEvent Object should check
xasecure.audit.destination.xx value (was: Before obtaining AuditHandler Object
should check xasecure.audit.destination.xx value)
> Before obtaining AuthzAuditEvent Object should check
> xasecure.audit.destination.xx value
>
>
> Key: RANGER-2676
> URL: https://issues.apache.org/jira/browse/RANGER-2676
> Project: Ranger
> Issue Type: Improvement
> Components: audit, plugins
>Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Critical
> Fix For: 2.0.0
>
>
> When after evalute policy and then process the auditlog，need to obtain
> AuditHandler Object and AuthzAuditEvent object
> (1）AuditHandler object obtained when init plugin according to the value of
> xasecure.audit.destination.{db/solor...}
> (2) So, obtaining AuthzAuditEvent should also according to the value of
> xasecure.audit.destination.{db/solor...}, or when AuditHandler is null or
> dummyHandler, constructing AuthzAuditEvent object is useless which is very
> frequently called and thus result in the performance decline of service(hdfs
> namenode, kakfa broker,hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
