[
https://issues.apache.org/jira/browse/HDFS-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HDFS-17224:
----------------------------------
Description:
TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing because the
static mbean isn't null. This is inevitably related to the fact that in test
runs, the jvm is reused and so the mbean may be present from a previous test
-maybe one which didn't clean up.
it does not fail standalone
was:TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing because the
static mbean isn't null. This is inevitably related to the fact that in test
runs, the jvm is reused and so the mbean may be present from a previous test
-maybe one which didn't clean up.
Summary: TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing
intermittently (was: TestRollingUpgrade.testDFSAdminRollingUpgradeCommands
failing)
> TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing intermittently
> ----------------------------------------------------------------------------
>
> Key: HDFS-17224
> URL: https://issues.apache.org/jira/browse/HDFS-17224
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: dfsadmin, test
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Priority: Major
>
> TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing because the
> static mbean isn't null. This is inevitably related to the fact that in test
> runs, the jvm is reused and so the mbean may be present from a previous test
> -maybe one which didn't clean up.
> it does not fail standalone
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
