Details
Description
This happened in RC3 and is a regression compared to RC2.
As per discussion on the ml a flag should be added to disable quota support in these large deployments until quota can be used in a "cluster against single data dir" setup (much like metastore)
Perhaps a quick fix would be to simply omit the disk quota jar from the built artifacts for now? Or will this not work?