[PHOENIX-6510] Double-Checked Locking field must be volatile

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.17.0, 5.2.0, 4.16.2, 5.1.3
• Assignee: Wei-Chiu Chuang
• Reporter: Wei-Chiu Chuang
• Created: 12/Jul/21 08:33
• Updated: 15/Jul/21 10:18
• Resolved: 15/Jul/21 09:54

Description

There are three places where the field used for double-checked locking isn't volatile. Change them to volatile to ensure thread-safety.

More details on the double-checked locking paradigm: https://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html

Issue Links

• links to: GitHub Pull Request #1264