This is an evolution of the problem stated in
Currently, Drill does not leverage any information about the host machine during start up and makes assumptions about the available resources (like memory).
Further more, it is, often, up to the user to define the individual parameters of memory for Drill: Heap, Direct and CodeCache.
The idea is to introduce a distribution and user specific configuration checking scripts (distrib-auto.sh and drill-auto.sh) which follow the same precedence as on the lines of distrib-env.sh and drill-env.sh.
A check for the existence of the `distrib-auto.sh` / `drill-auto.sh` scripts will be performed and executed only if there is any executable lines of code. Otherwise, the expected behaviour is that the startup functionality Drill will continue as previous versions.
In combination with the requirement described for
DRILL-5741; it would be nice if a starting up Drillbit could be told upfront on the amount of memory it can assume to access and automatically perform the allocations for the individual parameters, while providing the ability for users to override (some or all of) those settings.