Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1082
Done the following changes:
1. The file names have been changed to the following:
* `./bin/auto-setup.sh`
* `./conf/distrib-setup.sh`
* `./conf/drill-setup.sh`
`auto-setup.sh` and `distrib-setup.sh` files are mutually exclusive in
execution.
i. `distrib-setup.sh` -> if it has executable content. Else
`auto-setup.sh`
The assumption here is that the distribution might have a
different mechanism for doing things (along lines of specifying a preferred
setup service).
ii. `drill-setup.sh` --> This is any additional setup activities beyond
what the distribution offers. I don't think this should be mutually exclusive
to the previous step, but should be an add on.
A distribution of Drill should reimplement the setup task done by
`auto-setup.sh` , if it wants to do the same separately.
2. For managing memory automatically, the `auto-setup.sh` script is looking
for the `DRILLBIT_MAX_PROC_MEM` variable.
If this is not set (which is the case by default), the existing procedure
for inferring memory parameters will be followed.
3. If the `DRILLBIT_MAX_PROC_MEM` variable is set, the logic defined within
the `auto-setup.sh` script is executed to assign and validate that the total
memory allocation of Heap, Direct and CodeCache is within that value.
4. The JIRA and the PR has been updated with the details of the feature.
---
