You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/12 00:14:00 UTC
[jira] [Updated] (HDDS-6990) AuthorizerLockImpl.java#tryWriteLockInOMRequest: move sanity arg check to after tryWriteLockThrowOnTimeout();
[ https://issues.apache.org/jira/browse/HDDS-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-6990:
---------------------------------
Labels: pull-request-available (was: )
> AuthorizerLockImpl.java#tryWriteLockInOMRequest: move sanity arg check to after tryWriteLockThrowOnTimeout();
> -------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-6990
> URL: https://issues.apache.org/jira/browse/HDDS-6990
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: George Huang
> Assignee: George Huang
> Priority: Major
> Labels: pull-request-available
>
> IllegalArgumentException from Preconditions check in tryWriteLockInOMRequest when another tenant write request is in-progress
> The IllegalArgumentException looks scary and misleading. We're now moving the sanity arg check to after the call ofÂ
> long stamp = tryWriteLockThrowOnTimeout();
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org