You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Zhengxi Li (Jira)" <ji...@apache.org> on 2021/02/26 06:49:00 UTC
[jira] [Created] (HDFS-15862) Rename file back to original in
TestViewfsWithNfs3.testNfsRenameSingleNN
Zhengxi Li created HDFS-15862:
---------------------------------
Summary: Rename file back to original in TestViewfsWithNfs3.testNfsRenameSingleNN
Key: HDFS-15862
URL: https://issues.apache.org/jira/browse/HDFS-15862
Project: Hadoop HDFS
Issue Type: Test
Reporter: Zhengxi Li
Assignee: Zhengxi Li
The 'org.apache.hadoop.hdfs.nfs.nfs3.TestViewfsWithNfs3.testNfsRenameSingleNN' test is not idempotent and fails if run twice in the same JVM, because it pollutes state shared among tests. It may be good to clean this state pollution so that some other tests do not fail in the future due to the shared state polluted by this test.
Running {{TestViewfsWithNfs3.testNfsRenameSingleNN}} twice would result in the second run failing with a NullPointer exception:
{noformat}
[ERROR] Errors:
[ERROR] TestViewfsWithNfs3.testNfsRenameSingleNN:317 NullPointer
{noformat}
The reason for this is that the {{/user1/renameSingleNN}} file is created in {{setup()}}, but gets renamed in {{testNfsRenameSingl{{eNN}}}}. When the second run of {{testNfsRenameSingleNN}} tries to get info of the file by its original name, it returns a NullPointer since the file no longer exists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org