[
https://issues.apache.org/jira/browse/HBASE-29775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JinHyuk Kim updated HBASE-29775:
--------------------------------
Description:
h2. *Description*
When {{hbase.master.ui.readonly}} is set to {{true}}, the HBase Master UI is
intended to operate in a read-only mode, preventing any state-changing
operations through the UI.
However, in the current behavior, the log level page becomes completely
inaccessible in read-only mode. This makes it impossible to *check* the current
log level configuration, even though checking log levels is a purely
observational operation and does not modify system state.
h3. *Current Behavior*
* When {{hbase.master.ui.readonly=true}}
** Access to the log level page is blocked entirely
** Users cannot check current log levels
** !screenShot 2025-12-12 pm 11.24.40.png|width=581,height=138!
h3. *Expected Behavior*
* When {{hbase.master.ui.readonly=true}}
** Users *can check* the current log levels
** Any attempt to *modify* log levels via the UI should remain rejected
h3. *Change Summary*
Allows access to the log level page in master UI read-only mode for {*}checking
purposes only{*}.
was:
h2. *Description*
When {{hbase.master.ui.readonly}} is set to {{{}true{}}}, the HBase Master UI
is intended to operate in a read-only mode, preventing any state-changing
operations through the UI.
However, in the current behavior, the log level page becomes completely
inaccessible in read-only mode. This makes it impossible to *check* the current
log level configuration, even though checking log levels is a purely
observational operation and does not modify system state.
h3. *Current Behavior*
* When {{hbase.master.ui.readonly=true}}
** Access to the log level page is blocked entirely
** Users cannot check current log levels
** !screenShot 2025-12-12 pm 11.24.40.png|width=581,height=138!
h3. *Expected Behavior*
* When {{hbase.master.ui.readonly=true}}
** Users *can check* the current log levels
** Any attempt to *modify* log levels via the UI should remain rejected
h3. *Change Summary*
Allows access to the log level page in master UI read-only mode for {*}checking
purposes only{*}.
> Allow inspecting log levels in Master UI in read-only mode
> ----------------------------------------------------------
>
> Key: HBASE-29775
> URL: https://issues.apache.org/jira/browse/HBASE-29775
> Project: HBase
> Issue Type: Bug
> Components: UI
> Reporter: JinHyuk Kim
> Assignee: JinHyuk Kim
> Priority: Minor
> Labels: pull-request-available
> Attachments: screenShot 2025-12-12 pm 11.24.40.png, screenShot
> 2025-12-13 12.20.50.png, screenShot 2025-12-13 12.29.05.png, screenShot
> 2025-12-13 12.29.17.png
>
>
> h2. *Description*
> When {{hbase.master.ui.readonly}} is set to {{true}}, the HBase Master UI is
> intended to operate in a read-only mode, preventing any state-changing
> operations through the UI.
> However, in the current behavior, the log level page becomes completely
> inaccessible in read-only mode. This makes it impossible to *check* the
> current log level configuration, even though checking log levels is a purely
> observational operation and does not modify system state.
> h3. *Current Behavior*
> * When {{hbase.master.ui.readonly=true}}
> ** Access to the log level page is blocked entirely
> ** Users cannot check current log levels
> ** !screenShot 2025-12-12 pm 11.24.40.png|width=581,height=138!
> h3. *Expected Behavior*
> * When {{hbase.master.ui.readonly=true}}
> ** Users *can check* the current log levels
> ** Any attempt to *modify* log levels via the UI should remain rejected
> h3. *Change Summary*
> Allows access to the log level page in master UI read-only mode for
> {*}checking purposes only{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
