avijayanhwx commented on a change in pull request #529: HDDS-2982. Recon server
start failed with CNF exception in a cluster …
URL: https://github.com/apache/hadoop-ozone/pull/529#discussion_r375602903
##########
File path:
hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/ReconServer.java
##########
@@ -82,7 +82,13 @@ protected void configureServlets() {
LOG.info("Creating Recon Schema.");
reconSchemaManager.createReconSchema();
- httpServer = injector.getInstance(ReconHttpServer.class);
+ // TODO Remove try-catch block after HDDS-2041 is fixed.
+ // Allowing Recon server start even if HTTP server start failed
+ try {
Review comment:
@bharatviswa504 Yes that is a valid question. On further investigation, I
discovered that this may be due to jetty upgrade in hadoop in the distribution.
This affects all Ozone components. Also, in the case of SCM, even though it
withstands a HttpServer crash, since the initialization is stopped midway due
to exception, none of the event handlers are registered thereby making the
component useless.
I plan to hold on to this PR, wont commit it. If jetty version is indeed the
problem, that is being handled in HDDS-2950. I will close this PR without
merging the changes.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
