[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612367#comment-17612367 ]
Andrew Kyle Purtell commented on HBASE-27381: --------------------------------------------- {quote}Removing RegionInfo.UNDEFINED has eliminated the deadlocks we were seeing. This is probably no surprise {quote} +1 for removal. We should get this into the next 2.4 and 2.5 releases. I will defend the change. > Still seeing 'Stuck' in static initialization creating RegionInfo instance > -------------------------------------------------------------------------- > > Key: HBASE-27381 > URL: https://issues.apache.org/jira/browse/HBASE-27381 > Project: HBase > Issue Type: Bug > Reporter: Bryan Beaudreault > Priority: Major > > See https://issues.apache.org/jira/browse/HBASE-24896 for the original > description. Despite having that fix, we are seeing this issue in a > 2.4.6-based deploy. We recently started seeing it as we were moving to > centos8. I'm not sure why the centos version would affect this, otherwise the > hbase server version and java versions were not changing. > We're seeing this in a non-trivial number of new centos8 servers that we spin > up. I'm pushing a hotfix which removes RegionInfo.UNDEFINED to see if that > resolves our issue. > As mentioned in my last comments on that jira, it could be that this field is > still an issue because according to > [https://stackoverflow.com/questions/28631656/runnable-thread-state-but-in-object-wait:] > > Such deadlocks may be caused by a [typical > > bug|https://bugs.openjdk.org/browse/JDK-8037567] when a subclass is > > referenced from a static initializer. > If that's true, in this case MutableRegionInfo is a subclass/implementer of > RegionInfo, so that could trigger it. Granted the linked bug is marked "Not > An Issue". -- This message was sent by Atlassian Jira (v8.20.10#820010)