mirror of
https://github.com/apache/impala.git
synced 2026-01-05 21:00:54 -05:00
6dc13d933b
Remove Yarn from minicluster by default. Turns out that we start Yarn as part of the minicluster, but we never use it. (HiveServer2 is configured to run MR jobs "locally" in process.) Likely, this Yarn integration is a vestige of Yarn/Llama integration. We can save memory by not starting it by default. There are some less-common tooks like tests/comparison/cluster.py which use Yarn (and Hadoop Streaming). In deference to those tools, I've left a mechanism to start Yarn rather than excising it altogether. After running buildall the regular way, add Yarn to the cluster by running: testdata/cluster/admin -y start_cluster I tested by running core tests. I did not test the kerberized minicluster. [Due to a git mishap, a version of this was previously checked in and reverted.] Change-Id: I97053a44bbe32048e6c35cc28680d1c7696af13f Reviewed-on: http://gerrit.cloudera.org:8080/9970 Reviewed-by: Michael Brown <mikeb@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>