[HDFS-8332] DFS client API calls should check filesystem closed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha1
• Target Version/s: 2.8.0
• Hadoop Flags: Incompatible change, Reviewed

Release Note

Users may need special attention for this change while upgrading to this version. Previously user could call some APIs(example: setReplication) wrongly even after closing the fs object. With this change DFS client will not allow any operations to call on closed fs objects. As calling fs operations on closed fs is not right thing to do, users need to correct the usage if any.

• Assignee: Rakesh Radhakrishnan
• Reporter: Rakesh Radhakrishnan
• Created: 06/May/15 06:56
• Updated: 12/May/16 18:14
• Resolved: 18/May/15 09:30

Description

I could see listCacheDirectives() and listCachePools() APIs can be called even after the filesystem close. Instead these calls should do checkOpen and throws:

java.io.IOException: Filesystem closed
	at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:464)

Issue Links

• breaks: HDFS-8412 Fix the test failures in HTTPFS: In some tests setReplication called after fs close.