virajjasani opened a new pull request #3434:
URL: https://github.com/apache/hadoop/pull/3434
### Description of PR
When dfs.federation.router.federation.rename.option is set to DISTCP and
hdfs.fedbalance.procedure.scheduler.journal.uri is not set, DFSRouter fails to
launch.
```
2021-09-08 15:39:11,818 ERROR
org.apache.hadoop.hdfs.server.federation.router.DFSRouter: Failed to start
router
java.lang.NullPointerException
at java.base/java.net.URI$Parser.parse(URI.java:3104)
at java.base/java.net.URI.<init>(URI.java:600)
at
org.apache.hadoop.hdfs.server.federation.router.RouterRpcServer.initRouterFedRename(RouterRpcServer.java:444)
at
org.apache.hadoop.hdfs.server.federation.router.RouterRpcServer.<init>(RouterRpcServer.java:419)
at
org.apache.hadoop.hdfs.server.federation.router.Router.createRpcServer(Router.java:391)
at
org.apache.hadoop.hdfs.server.federation.router.Router.serviceInit(Router.java:188)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
at
org.apache.hadoop.hdfs.server.federation.router.DFSRouter.main(DFSRouter.java:69)
```
hdfs.fedbalance.procedure.scheduler.journal.uri is
hdfs://localhost:8020/tmp/procedure by default, however, the default value is
not used in DFSRouter.
### How was this patch tested?
Local dev testing. After applying fix for HDFS-16219, we can reproduce above
error. And the fix provides default value to
hdfs.fedbalance.procedure.scheduler.journal.uri.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
