bharatviswa504 edited a comment on pull request #1031: URL: https://github.com/apache/hadoop-ozone/pull/1031#issuecomment-642797538
> **Some background** > `gerServiceInfo` call was introduced as part of `Service Discovery API` (HDFS-12868). > The idea behind `Service Discovery API` was to not worry about setting multiple properties at client to connect to Ozone. > Point the client to any one of the OzoneManager (even in case of HA), the client should be able to get all the required configuration and be able to connect to Ozone. > This will make the client configuration simple. > > When `gerServiceInfo` was introduced, Ozone client just needed OM's IP and port to connect, nothing else. Over time we made lot of code change and never revisited `Service Discovery API`. > After OM HA, it is no longer true that we can discover other services and required configurations just with single OM's IP/Port. We need `ozone-site.xml` at client and set of properties that will allow us to interact with OM HA. > > Now I'm not even sure where and why `gerServiceInfo` is getting used. For OM HA, the reason for not using the getServiceInfo was if client knows one of the OzoneManager addresses, and if that is down, client will not be able to talk to the ozone cluster. Even right now getServiceInfo, will now return quorum of OM address with each role, but this information cannot be used for the above reason, so the client still needs a quorum of OM address. ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
