[jira] [Commented] (RANGER-3758) Decrease log-level when no HBase remote client address is found
[
https://issues.apache.org/jira/browse/RANGER-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536954#comment-17536954
]
Ramesh Mani commented on RANGER-3758:
-
+1 for the patch. Thanks [~elserj]
> Decrease log-level when no HBase remote client address is found
> ---
>
> Key: RANGER-3758
> URL: https://issues.apache.org/jira/browse/RANGER-3758
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Josh Elser
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 146.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We deal with really annoying logging in HBase services because of this one
> line
> {noformat}
> 2022-04-17 17:51:05,481 INFO
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor: Unable
> to get remote Address {noformat}
> 20% of all HBase logging in one RegionServer is from this one log message.
> There is zero value derived from this log message as it is completely
> expected that HBase will perform operations on its own which Ranger would
> audit.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3758) Decrease log-level when no HBase remote client address is found
[
https://issues.apache.org/jira/browse/RANGER-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated RANGER-3758:
Fix Version/s: 3.0.0
> Decrease log-level when no HBase remote client address is found
> ---
>
> Key: RANGER-3758
> URL: https://issues.apache.org/jira/browse/RANGER-3758
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Josh Elser
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 146.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We deal with really annoying logging in HBase services because of this one
> line
> {noformat}
> 2022-04-17 17:51:05,481 INFO
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor: Unable
> to get remote Address {noformat}
> 20% of all HBase logging in one RegionServer is from this one log message.
> There is zero value derived from this log message as it is completely
> expected that HBase will perform operations on its own which Ranger would
> audit.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3758) Decrease log-level when no HBase remote client address is found
[
https://issues.apache.org/jira/browse/RANGER-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated RANGER-3758:
Affects Version/s: 3.0.0
> Decrease log-level when no HBase remote client address is found
> ---
>
> Key: RANGER-3758
> URL: https://issues.apache.org/jira/browse/RANGER-3758
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Josh Elser
>Priority: Major
> Attachments: 146.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We deal with really annoying logging in HBase services because of this one
> line
> {noformat}
> 2022-04-17 17:51:05,481 INFO
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor: Unable
> to get remote Address {noformat}
> 20% of all HBase logging in one RegionServer is from this one log message.
> There is zero value derived from this log message as it is completely
> expected that HBase will perform operations on its own which Ranger would
> audit.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3758) Decrease log-level when no HBase remote client address is found
[
https://issues.apache.org/jira/browse/RANGER-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated RANGER-3758:
Attachment: 146.patch
> Decrease log-level when no HBase remote client address is found
> ---
>
> Key: RANGER-3758
> URL: https://issues.apache.org/jira/browse/RANGER-3758
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Josh Elser
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 146.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We deal with really annoying logging in HBase services because of this one
> line
> {noformat}
> 2022-04-17 17:51:05,481 INFO
> org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor: Unable
> to get remote Address {noformat}
> 20% of all HBase logging in one RegionServer is from this one log message.
> There is zero value derived from this log message as it is completely
> expected that HBase will perform operations on its own which Ranger would
> audit.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536839#comment-17536839 ] Ramesh Mani commented on RANGER-3755: - [~aakashnand] Please update the patch. Thank you > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3724) Create Ranger Admin API to refresh policy cache
[ https://issues.apache.org/jira/browse/RANGER-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536567#comment-17536567 ] Kishor Gollapalliwar commented on RANGER-3724: -- master follow-up commit: https://github.com/apache/ranger/commit/2f776deceaccd94ec4402679acbf528af42b1c76 > Create Ranger Admin API to refresh policy cache > --- > > Key: RANGER-3724 > URL: https://issues.apache.org/jira/browse/RANGER-3724 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create Ranger Admin API to refresh policy cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
Re: Review Request 73985: RANGER-3724: Create Ranger Admin API to refresh policy cache -- follow-up patch
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73985/#review224443 --- Ship it! Ship It! - Mehul Parikh On May 12, 2022, 8:48 a.m., Kishor Gollapalliwar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73985/ > --- > > (Updated May 12, 2022, 8:48 a.m.) > > > Review request for ranger, bhavik patel, Dineshkumar Yadav, Kirby Zhou, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-3724 > https://issues.apache.org/jira/browse/RANGER-3724 > > > Repository: ranger > > > Description > --- > > Create Ranger Admin API to refresh policy cache, which will help refreshing > cache externally. > > Problem: In the current API, if a user accidently do not pass service_name, > it resets everything. > > Changes: > 1. Updated existing API: enforcing service_name as mandatory parameter > 2. Created new API: reset/ remove everything (all service policy cache) > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java > 1aa861424 > > > Diff: https://reviews.apache.org/r/73985/diff/2/ > > > Testing > --- > > 1. mvn clean compile package install -U > 2. Hit API with invalid service name > (http://localhost:6080/service/plugins/policies/cache/reset?name=invalid_service) > 3. Hit API with empty service name > (http://localhost:6080/service/plugins/policies/cache/reset) > 3. Hit API with valid service name > (http://localhost:6080/service/plugins/policies/cache/reset?name=test_hdfs) > 4. Hit API with valid service name when cache is empty > (http://localhost:6080/service/plugins/policies/cache/reset?name=test_hdfs) > 5. Hit API when cache is not empty > (http://localhost:6080/service/plugins/policies/cache/reset-all) > 6. Hit API when cache is empty > (http://localhost:6080/service/plugins/policies/cache/reset-all) > > > Thanks, > > Kishor Gollapalliwar > >
