Reply
Highlighted
New Contributor
Posts: 1
Registered: ‎02-18-2019

Memory limit exceeded on insert

[ Edited ]

Hi!

 

I installed cloudera some time ago as proof of concept with cloudera manager. I tried to load database into impala and getting following error upon inserting csv-stored table into parquet table.

 

insert into parquet_compression.parquet_table select * from default.csv_table;

ERROR:

 

Query cc421051ba0b9760:12dfa5af00000000: 1% Complete (8 out of 717)
Query cc421051ba0b9760:12dfa5af00000000: 2% Complete (16 out of 717)
Memory limit exceeded: Error occurred on backend cloudera-srv:22000 by fragment cc421051ba0b9760:12dfa5af00000000
Memory left in process limit: -120.49 MB
Memory left in query limit: 31.11 GB
Query(cc421051ba0b9760:12dfa5af00000000): Limit=31.42 GB Reservation=168.00 MB ReservationLimit=388.00 MB OtherMemory=150.19 MB Total=318.19 MB Peak=330.23 MB
  Fragment cc421051ba0b9760:12dfa5af00000000: Reservation=168.00 MB OtherMemory=150.19 MB Total=318.19 MB Peak=330.23 MB
    HDFS_SCAN_NODE (id=0): Reservation=168.00 MB OtherMemory=21.49 MB Total=189.49 MB Peak=215.03 MB
      Queued Batches: Total=21.46 MB Peak=23.01 MB
    HdfsTableSink: Total=128.68 MB Peak=128.68 MB
    CodeGen: Total=8.71 KB Peak=869.00 KBProcess: memory limit exceeded. Limit=485.00 MB Total=605.49 MB Peak=613.51 MB
  Buffer Pool: Free Buffers: Total=152.50 MB
  Buffer Pool: Clean Pages: Total=0
  Buffer Pool: Unused Reservation: Total=0
  Data Stream Service Queue: Limit=24.25 MB Total=0 Peak=0
  Data Stream Manager Early RPCs: Total=0 Peak=0
  TCMalloc Overhead: Total=24.23 MB
  RequestPool=root.admin: Total=318.19 MB Peak=330.23 MB
    Query(cc421051ba0b9760:12dfa5af00000000): Limit=31.42 GB Reservation=168.00 MB ReservationLimit=388.00 MB OtherMemory=150.19 MB Total=318.19 MB Peak=330.23 MB
  Untracked Memory: Total=110.57 MB (1 of 2 similar)

I started up cloudera with -mem_limit=30G option (configured with webui Impala Daemon Command Line Argument Advanced Configuration Snippet (Safety Valve)) but it seems like adding this to command line args isn't effective.

 

Hope my description is informative, Cloudera 6.1.0 here.

 

 

Posts: 1,885
Kudos: 424
Solutions: 299
Registered: ‎07-31-2013

Re: Memory limit exceeded on insert

Were stats available for your source table before you performed the transforming insert? It may be a good idea to run a "COMPUTE STATS default.csv_table;" so the memory calculations are precise.

P.s. Within CM, you can reconfigure the memory limit via the Impala - Configuration - "Impala Daemon Memory Limit" field (search mem_limit).
Announcements