Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Steps:
- Deployed cluster.
- Enabled security.
- Enabled wire encryption.
- Set up dfs.datanode.address to value <=1023.
- Set up dfs.datahode.http.address to value <=1023.
- Set up dfs.datahode.https.address to value > 1023.
- Set up dfs.http.policy value to HTTP_AND_HTTPS.
- Restart HDFS components.
Restart was failed with [^datanodeRestart.txt] for datanode.
After that was executed:
- Set up dfs.datanode.address to use ports > 1023.
- Set up dfs.datanode.https.address to use ports > 1023.
- Set up dfs.data.transfer.protection to authentication.
- Set up dfs.http.policy value to HTTPS_ONLY.
- Restart HDFS components.
Restart was failed for datanode also.
Next steps:
- Set up dfs.datanode.address to use ports > 1023.
- Set up dfs.datanode.https.address to use ports > 1023.
- Set up dfs.data.transfer.protection to integrity.
- Set up dfs.http.policy value to HTTPS_ONLY.
- Restart HDFS components.
Restart was passed.
Next steps:
- Set up dfs.datanode.address to use ports <= 1023.
- Set up dfs.datanode.http.address to use ports <= 1023.
- Set up dfs.http.policy value to HTTP_ONLY.
- Delete dfs.data.transfer.protection.
- Restart HDFS components.
Restart was failed with [^namenodeStart.txt] for namenode.
Now NameNode can not to be restarted/started.
Attachments
Attachments
Issue Links
- links to