Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
The crypto -reencryptZone <action> -path <zone> command takes in a path argument. But when creating HdfsAdmin object, it takes the defaultFs instead of resolving from the path. This causes the following exception if the authority component in path does not match the authority of default Fs.
$ hdfs crypto -reencryptZone -start -path hdfs://mycluster-node-1:8020/zone1 IllegalArgumentException: Wrong FS: hdfs://mycluster-node-1:8020/zone1, expected: hdfs://ns1
$ hdfs crypto -reencryptZone -start -path hdfs://ns2/zone2 IllegalArgumentException: Wrong FS: hdfs://ns2/zone2, expected: hdfs://ns1