drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sudheesh Katkam <skat...@maprtech.com>
Subject Re: strange output from sys.memory
Date Thu, 30 Apr 2015 23:05:27 GMT
See exec/store/sys/MemoryIterator.java

memoryInfo.direct_current = context.getDrillbitContext().getAllocator().getAllocatedMemory();
memoryInfo.direct_max = TopLevelAllocator.MAXIMUM_DIRECT_MEMORY;

> On Apr 30, 2015, at 3:57 PM, Abdel Hakim Deneche <adeneche@maprtech.com> wrote:
> 
> After running the query described in DRILL-2851
> <https://issues.apache.org/jira/browse/DRILL-2851> I get a failure as
> expected, but when I run "select * from sys.memory" I get the following
> output:
> 
> hostname|user_port|heap_current|heap_max  |direct_current|direct_max
>> ...     |31010    |542977168   |3817865216|-2129977243   |8589934592
> 
> 
> how's the "direct_current" value computing ? could someone point me to the
> source code where sys.memory is computed ?
> 
> Thanks!
> -- 
> 
> Abdelhakim Deneche
> 
> Software Engineer
> 
>  <http://www.mapr.com/>
> 
> 
> Now Available - Free Hadoop On-Demand Training
> <http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message