fe/src/test/resources/minicluster-llama-site.xml

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <property>
    <!-- Max memory limit given to queries by default. This will allow
         running one large query and multiple small queries on a typical
         minicluster where each impalad has ~7gb of memory. -->
    <name>impala.admission-control.max-query-mem-limit.root.default</name>
    <value>4294967296</value><!--4GB-->
  </property>
  <property>
    <!-- Min memory limit given to queries by default. Set low enough
         so as not to reduce query concurrency but high enough that
         queries don't get starved for memory because of low estimates. -->
    <name>impala.admission-control.min-query-mem-limit.root.default</name>
    <value>314572800</value><!--300MB-->
  </property>
  <property>
    <!--Allow individual tests to set mem_limit to any value, if needed.-->
    <name>impala.admission-control.clamp-mem-limit-query-option.root.default</name>
    <value>false</value>
  </property>
  <!-- We need to increase the pool queue timeout to avoid flakiness from queries
       getting stuck behind queries from other tests and timed out. Set to a
       very high value to avoid failures unless queries are genuinely stuck. -->
  <property>
    <name>impala.admission-control.pool-queue-timeout-ms.root.default</name>
    <value>1800000</value> <!-- 30 minutes -->
  </property>
  <property>
    <name>llama.am.throttling.maximum.placed.reservations.root.no-limits</name>
    <value>1</value>
  </property>
  <!-- We need to increase the pool queue timeout to avoid flakiness from queries
       getting stuck behind queries from other tests and timed out. Set to a
       very high value to avoid failures unless queries are genuinely stuck. -->
  <property>
    <name>impala.admission-control.pool-queue-timeout-ms.root.no-limits</name>
    <value>1800000</value> <!-- 30 minutes -->
  </property>
</configuration>