Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/922
Closing this until a rework is complete, based on the recommendations.
---
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/922
This may be one of those times when we need to resort to a bit of design
thinking.
The core idea is that the user sets one environment variable to check the
others. The first issue is
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/922
@kkhatua, thanks for the note. No doubt the proposed model helps in _some_
cases. The problem is, it adds complexity for other cases.
Perhaps offer the change as an additional script that
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/922
@paul-rogers
The reason this would be needed is because the system admin might not be
the one managing the specifics of the Drill memory allocations. This allows a
node admin to define the
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/922
-1
This seems like a good idea. But, I don't think this is the way we should
go for reasons identified in the JIRA.
For one, we count on the user to provide a parameter to
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/922
@ppadma Can you please review this?
The changes have been tested with and without the parameter.
If the env variable is set as `40%` , `drillbit.out` reports
```
Aug 25, 2017 4:30:59
