[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623398#comment-17623398
]
Hudson commented on HBASE-27381:
Results for branch branch-2.4
[build #446 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/446/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
(x) {color:red}-1 jdk8 hadoop2 checks{color}
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/446/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/446/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>Assignee: Bryan Beaudreault
>Priority: Major
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613203#comment-17613203
]
Hudson commented on HBASE-27381:
Results for branch branch-2.5
[build #218 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/218/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/218/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/218/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/218/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/218/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>Assignee: Bryan Beaudreault
>Priority: Major
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613123#comment-17613123
]
Hudson commented on HBASE-27381:
Results for branch master
[build #694 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/694/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/694/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/694/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/694/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>Assignee: Bryan Beaudreault
>Priority: Major
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612974#comment-17612974
]
Hudson commented on HBASE-27381:
Results for branch branch-2.4
[build #434 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/434/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/434/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/434/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/434/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>Assignee: Bryan Beaudreault
>Priority: Major
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612850#comment-17612850
]
Hudson commented on HBASE-27381:
Results for branch branch-2
[build #656 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/656/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/656/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/656/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/656/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/656/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>Assignee: Bryan Beaudreault
>Priority: Major
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612766#comment-17612766 ] Andrew Kyle Purtell commented on HBASE-27381: - (y) > 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 >Assignee: Bryan Beaudreault >Priority: Major > Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612372#comment-17612372 ] Bryan Beaudreault commented on HBASE-27381: --- Thanks Andrew. I just put a PR up > 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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
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)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608254#comment-17608254 ] Bryan Beaudreault commented on HBASE-27381: --- Removing RegionInfo.UNDEFINED has eliminated the deadlocks we were seeing. This is probably no surprise. The initial approach taken in HBASE-24896 was to deprecate it for removal in 4.0.0, which honestly seems forever away just given how long we've been waiting to release 3.0. Given the potential severity of this bug, I wonder if it's worth pushing an incompatible change to remove. I'm not sure there's a huge value in this constant for downstream users? > 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)
