Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
MIME-Version: 1.0
Date: Tue, 7 Jul 2015 09:13:41 -0700
Message-ID: 
 <CAKTYAC9spSXArzLBmF+Eus_YWAEA0GSGjzz0L0XFj2MdGHZzug@mail.gmail.com>
Subject: connection allocator in rpc layer is using too much memory
From: Abdel Hakim Deneche <adeneche@maprtech.com>
To: "dev@drill.apache.org" <dev@drill.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c07e99248aed4051a4b4e7f

--94eb2c07e99248aed4051a4b4e7f
Content-Type: text/plain; charset=UTF-8

Trying to investigate DRILL-3241
<https://issues.apache.org/jira/browse/DRILL-3241> (query hangs if out of
memory in RPC layer), I see the following warning in the logs:

WARN: Failure allocating buffer on incoming stream due to

 memory limits.  Current Allocation: 1372678764.


This happening in ProtobufLengthDecoder.decode() on the receiver side (data
server).

Is it expected for the connection allocation to allocation > 1GB of memory
? shouldn't the allocated batches be transferred to the receiving
fragment's allocator ?

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>

--94eb2c07e99248aed4051a4b4e7f--