Github user arina-ielchiieva commented on the issue:
https://github.com/apache/drill/pull/1160
+1, thanks for making the changes.
---
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1160
During a freshly setup Drillbit:
While running 2 large (600M rows) join query
Github user arina-ielchiieva commented on the issue:
https://github.com/apache/drill/pull/1160
+1
---
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1160
@arina-ielchiieva
Restricting this PR to address the bug in `metrics.ftl`
Will create a new PR for
[DRILL-6289](https://issues.apache.org/jira/browse/DRILL-6289)
---
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1160
I think I need to put up some tooltips.
We're getting the metrics from the `drill.allocator.root.[peak|used]`
values. I haven't seen a metric that shows the actual Direct allocation from
the
Github user parthchandra commented on the issue:
https://github.com/apache/drill/pull/1160
Looks wrong dunnit? Direct memory is (still?) showing as zero?
---
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1160
@parthchandra / @arina-ielchiieva would you guys want to review this?
Here is a preview of how the details appear on the default page:
