[ https://issues.apache.org/jira/browse/RANGER-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915827#comment-16915827 ]
Madhan Neethiraj commented on RANGER-2551: ------------------------------------------ [~Seymour Xu] - ihe stacktrace in the description suggests that the fix in RANGER-809 may not be present in your env; [commitdiff|https://gitbox.apache.org/repos/asf?p=ranger.git;a=commitdiff;h=ffb895e2]. Can you please review? > Optimize obtaining the agentHostname of audit log > -------------------------------------------------- > > Key: RANGER-2551 > URL: https://issues.apache.org/jira/browse/RANGER-2551 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger > Affects Versions: 1.1.0, 2.0.0, 1.2.0 > Reporter: Haihui Xu > Assignee: Haihui Xu > Priority: Major > Labels: patch > Fix For: 2.1.0 > > Attachments: RANGER-2551.patch > > > Firstly, kafka enable ranger-kafka-plugin,. The ranger audit log event > happens very frequently when the kafka client access kafka broker, thus > affectting kafka performance. The jstack of kakfa broker pid logs is: > "kafka-request-handler-23" #101 daemon prio=5 os_prio=0 > tid=0x00007fbcce7d5000 nid=0x3331a runnable [0x00007fb356e3000] > java.lang.Thread.State: RUNNABLE > at java.net.Inet4AddressImpl.getLocalHostName(Native Method) > at java.net.InetAddress.getLocalHost(InetAddress.java:1474) > at > org.apache.ranger.audit.provider.MiscUtil.getHostname(MiscUtil.java 166) > at > org.apache.ranger.plugin.audit.RangerDefaultAuditHandler.populateDefaults(RangerDefaultAuditHandler.java:198) > at > org.apache.ranger.plugin.audit.RangerDefaultAuditHandler.getAuthezEvents(RangerDefaultAuditHandler.java:132) -- This message was sent by Atlassian Jira (v8.3.2#803003)