Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/879
Increasing the minimum means each sort uses more memory than before. This
means that the query uses more memory than the 2 GB the user has allotted.
Drill cannot create new memory, so that memory is coming from somewhere. So,
you are right that increasing memory has impact, but we've already incurred
that impact by increasing the minimum (that's why we did it.)
So, I'm asking if we should increase the aggregate maximum to reflect that
memory use is no longer constrained by the per-query maximum.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
