JiaLiangC commented on PR #3782: URL: https://github.com/apache/ambari/pull/3782#issuecomment-2073814703
@AnanyaSingh2121 Thank you for your feedback. Let me address your questions: 1. **Why treat the router as a separate service?** Although the router is part of the Hadoop source code, from an architectural standpoint, in a federated cluster, the router cluster operates independently from any specific Hadoop cluster, representing a routing layer. Thus, I believe it's inappropriate to associate the router with any particular Hadoop cluster during deployment. Moreover, having the router deployed independently allows for more flexible and clearer scalability and maintenance. To transition a cluster into a federated cluster, one simply needs to add a router and modify a few configurations. If a cluster with a router wishes to dismount from a federated setup and return to being an independent cluster, this can easily be done by uninstalling the router service and adjusting the current Hadoop configurations, which keeps the coupling low. 2. **About routing client requests to clusters and the configuration:** After deploying the router and configuring it to monitor the current cluster, along with modifying the cluster's hdfs-site, then you can perform directory mounts using `dfsrouteradmin` from the command line. Clients access using the `core-site` and `hdfs-site` configurations. By modifying the configuration, all client configurations can point to the router cluster. 3. **On your third point:** That's a great idea. It requires coordination with the frontend. Perhaps we can iterate over it step by step; achieving perfection right away is challenging. 4. **Regarding the router `service_advisor` you mentioned:** If you're interested, you might consider submitting a PR to address this. -- 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
