Hi folks, I read Uber's article https://eng.uber.com/cost-efficient-big-data-platform/. This article is very interesting for me, and now I have some questions.
> For example, we identified that the Capacity Scheduler has some complex logic > that slows down task assignment. However, code changes to get rid of those > won’t be able to merge into Apache Hadoop trunk, since those sophisticated > features may be needed by other companies. - What are those sophisticated features in the Capacity Scheduler? - In the future, can we turn off the features by some flags in Apache Hadoop? - Is there any other examples like this? Thanks and regards, Akira --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
