Affects Version/s: 0.5.0
Fix Version/s: 0.9.0
HADOOP-375 changed the order in which a data node registers and starts its http server.
Current version first starts the http server, then registers. As a result if the registration fails,
which can happen e.g. if the datanode has illegal storage id (=does not belong to the cluster),
the http server keeps running, which makes the data node seem running too.
I think 2 things need to be done.
1) Datanode registration should precede the http server startup.
2) The http server should shutdown when the datanode fails (in general).
I am attaching a patch for the first item.
Does anybody know how the latter can be done in the version of jetty we are on now?