Reply
Explorer
Posts: 13
Registered: ‎11-08-2017

Unable to advance iterator: Not found: Scanner not found

Hi,

we got below message in a lot of our impala queries, 

Do you have idea how can we solve this isse?

 

Query Status: Unable to advance iterator: Timed out: Scan RPC to x.x.x.x:7050 timed out after 0.000s (SENT): Not found: Scanner not found

 

regards,

Beata

Highlighted
Cloudera Employee
Posts: 14
Registered: ‎11-12-2013

Re: Unable to advance iterator: Not found: Scanner not found

This error indicates that a Kudu tablet server has closed a scanner because it hadn't been accessed in some time. It could manifest on a particularly slow query that very infrequently fetches new data from Kudu.

 

Can you share the Impala query profile for one of the failed queries, as well as the Impala daemon coordinator log?

 

You can also work around the issue by reconfiguring Kudu's --scanner_ttl_ms flag to a much higher value (the default is 60s), though this will come at the potential cost of Kudu memory if any clients are orphaning their scanners.

Announcements