[
https://issues.apache.org/jira/browse/HBASE-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080069#comment-17080069
]
Hudson commented on HBASE-24121:
--------------------------------
Results for branch branch-2.2
[build #835 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/835/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/835//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/835//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/835//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [Authorization] ServiceAuthorizationManager isn't dynamically updatable. And
> it should be.
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-24121
> URL: https://issues.apache.org/jira/browse/HBASE-24121
> Project: HBase
> Issue Type: Bug
> Components: rpc, security
> Reporter: Reid Chan
> Assignee: Reid Chan
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 1.7.0, 1.4.14, 2.2.5
>
>
> Some more background information.
> ServiceAuthorizationManager is responsible for the Services access rights
> defined in hbase-policy.xml which locates under $hbase_home/conf directory.
> Currently, since it doesn't support update dynamically, we need to restart
> master/regionservers to make configurations take effect. It is an expensive
> and low efficient admin operation.
> HDFS has the refreshPolicy to do that, HBase also has update_config command,
> we can make use of that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
