[STORM-2750] fix double_checked locking

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0, 1.1.2
• Labels: pull-request-available
• Assignee: Huaiyong Fu
• Reporter: Huaiyong Fu
• Created: 21/Sep/17 02:44
• Updated: 22/Sep/17 14:46
• Resolved: 22/Sep/17 14:46

Description

update HBaseSecurityUtil singleton to fix double_checked locking

Double-Checked Locking is widely cited and used as an efficient method for implementing lazy initialization in a multithreaded environment.
Unfortunately, it will not work reliably in a platform independent way when implemented in Java, without additional synchronization. When implemented in other languages, such as C+, it depends on the memory model of the processor, the reorderings performed by the compiler and the interaction between the compiler and the synchronization library. Since none of these are specified in a language such as C, little can be said about the situations in which it will work. Explicit memory barriers can be used to make it work in C+, but these barriers are not available in Java.
See url link for details: http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html