AnanyaSingh2121 commented on PR #3782: URL: https://github.com/apache/ambari/pull/3782#issuecomment-2079794895
Hi @JiaLiangC , Thank you for addressing the points in detail. I have some more feedback. - Ideally we will not have a federated cluster without Router as to manage Federation we will be using Router only. So installing it as a separate separate does not provide the required decoupling. Once federation is enabled Router is a requirement. So it does not make sense to just delete Router. If Router needs to be uninstalled then federation also will have to disabled. We cannot separate the two in my opinion. - About the client requests, yes you are correct we will have to eventually modify the core-site and hdfs-site. So better to have all the conf files at one place. Also my concern was regarding managing multiple Routers as in that case you will not be able to modify the default Fs to one Router rpc. For this purpose Hadoop community proposes ns-fed a logical namespace for router. That will require testing in Ambari as those configurations will give rise to conflict. Hadoop community has also raised a jira for the same. - Also we have developed and tested the Router based federation with Router as component of HDFS. We have also included several UI changes where Router can be enabled as part of Federation flow. Will be raising a jira for the same and submit a patch. Request your inputs also on the same. Thanks -- 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: dev-unsubscr...@ambari.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For additional commands, e-mail: dev-h...@ambari.apache.org
