You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2022/03/13 22:00:00 UTC
[jira] [Updated] (HADOOP-17858) Avoid possible class loading deadlock with VerifierNone initialization
[ https://issues.apache.org/jira/browse/HADOOP-17858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Masatake Iwasaki updated HADOOP-17858:
--------------------------------------
Fix Version/s: 3.2.4
(was: 3.2.3)
> Avoid possible class loading deadlock with VerifierNone initialization
> ----------------------------------------------------------------------
>
> Key: HADOOP-17858
> URL: https://issues.apache.org/jira/browse/HADOOP-17858
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2, 3.2.4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Superclass Verifier has a static initializer VERIFIER_NONE that initializes sub-class VerifierNone. This reference can result in deadlock during class loading as per [https://docs.oracle.com/javase/specs/jls/se8/html/jls-12.html#jls-12.4.2].
> As of today, only RpcProgram use this instance and hence it is safe but if more clients start using this (specifically static ones), it has potential to bring deadlock. We should break this referencing before it is late.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org