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/16 14:10:00 UTC

[jira] [Updated] (HBASE-29778) Abort the operation if not allowed in read-only mode

     [ https://issues.apache.org/jira/browse/HBASE-29778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anuj Sharma updated HBASE-29778:
--------------------------------
    Description: 
Currently, if we discover that the operation is not allowed in Read-Only Mode then we are sending exception, but the context does not get aborted leading to multiple same exceptions gets thrown.

In this task, will be aborting the operation after the first exception gets thrown.

  was:
Currently, if we discover that operation is not allowed in Read-Only Mode we are sending exception, but the context does not get aborted leading to multiple same exceptions gets thrown.

In this task, will be aborting the operation after the first exception gets thrown.


> Abort the operation if not allowed in read-only mode
> ----------------------------------------------------
>
>                 Key: HBASE-29778
>                 URL: https://issues.apache.org/jira/browse/HBASE-29778
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anuj Sharma
>            Assignee: Anuj Sharma
>            Priority: Major
>
> Currently, if we discover that the operation is not allowed in Read-Only Mode then we are sending exception, but the context does not get aborted leading to multiple same exceptions gets thrown.
> In this task, will be aborting the operation after the first exception gets thrown.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)