You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anuj Sharma (Jira)" <ji...@apache.org> on 2025/12/07 15:54:00 UTC
[jira] [Updated] (HBASE-29756) Programmatically register related co-processor during initialization
[ https://issues.apache.org/jira/browse/HBASE-29756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anuj Sharma updated HBASE-29756:
--------------------------------
Description:
Currently, when user wants to make cluster read-only, he has to add property
{{ <property>}}
{{ <name>hbase.global.readonly.enabled</name>}}
{{ <value>false</value>}}
{{ </property>}}
and coprocessors for master, region and region server as follows:
{{ <property>}}
{{ <name>hbase.coprocessor.master.classes</name>}}
{{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
{{ </property>}}
{{ <property>}}
{{ <name>hbase.coprocessor.regionserver.classes</name>}}
{{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
{{ </property>}}
{{ <property>}}
{{ <name>hbase.coprocessor.region.classes</name>}}
{{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
{{ </property>}}
In this change we are planning to remove this manual process and when user add the read-only property then co-processors will get automatically registered during initialization.
was:
Currently, when user wants to make cluster read-only, he has to add property
<property>
<name>hbase.global.readonly.enabled</name>
<value>false</value>
</property>
and coprocessors for master, region and region server as follows:
<property>
<name>hbase.coprocessor.master.classes</name>
<value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>
</property>
<property>
<name>hbase.coprocessor.regionserver.classes</name>
<value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>
</property>
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>
</property>
In this change we are planning to remove this manual process and when user add the read-only property then co-processors will get automatically registered during initialization.
> Programmatically register related co-processor during initialization
> --------------------------------------------------------------------
>
> Key: HBASE-29756
> URL: https://issues.apache.org/jira/browse/HBASE-29756
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anuj Sharma
> Assignee: Anuj Sharma
> Priority: Major
>
> Currently, when user wants to make cluster read-only, he has to add property
> {{ <property>}}
> {{ <name>hbase.global.readonly.enabled</name>}}
> {{ <value>false</value>}}
> {{ </property>}}
> and coprocessors for master, region and region server as follows:
> {{ <property>}}
> {{ <name>hbase.coprocessor.master.classes</name>}}
> {{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
> {{ </property>}}
> {{ <property>}}
> {{ <name>hbase.coprocessor.regionserver.classes</name>}}
> {{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
> {{ </property>}}
> {{ <property>}}
> {{ <name>hbase.coprocessor.region.classes</name>}}
> {{ <value>org.apache.hadoop.hbase.security.access.ReadOnlyController</value>}}
> {{ </property>}}
>
> In this change we are planning to remove this manual process and when user add the read-only property then co-processors will get automatically registered during initialization.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)