Reply
Highlighted
Contributor
Posts: 54
Registered: ‎11-24-2017

Missing tables were not received in 120000m

[ Edited ]

Hi everyone!

 

I have some tables in an Hive database (let's call it db1) that are imported in another database (let's call it db2) with some transformations like table renaming and fields renaming like so:

 

 

CREATE TABLE db2.EMAIL_ADDRESS
LOCATION '/user/username/data/EMAIL_ADDRESS'
AS select * from db1.VCLIEML;

ALTER TABLE db2.EMAIL_ADDRESS CHANGE DESCNL CHANNEL_DESCRIPTION STRING;
ALTER TABLE db2.EMAIL_ADDRESS CHANGE CODCNL CHANNEL_CODE STRING;

 

 

The problem is that after this operation any query from Impala on these new tables hangs indefinitely. The same queries work fine on Hive.

 

I've looked in the impalad logs, and I found the following lines:

 

 

W0321 14:05:50.322782 21142 Frontend.java:914] Missing tables were not received in 120000ms. Load request will be retried.
W0321 14:05:50.323249 21129 Frontend.java:914] Missing tables were not received in 120000ms. Load request will be retried.
W0321 14:05:50.323366 21155 Frontend.java:914] Missing tables were not received in 120000ms. Load request will be retried.
I0321 14:05:50.323456 21142 Frontend.java:831] Requesting prioritized load of table(s): db2.EMAIL_ADDRESS
I0321 14:05:50.323627 21129 Frontend.java:831] Requesting prioritized load of table(s): db2.EMAIL_ADDRESS
I0321 14:05:50.323984 21155 Frontend.java:831] Requesting prioritized load of table(s): db2.EMAIL_ADDRESS W0321 14:05:54.322346 21145 Frontend.java:914] Missing tables were not received in 120000ms. Load request will be retried. . . .

 

It seems like Impala can't find the tables. Anyone knows how to fix this issue?

 

 

 

 

Cloudera Employee
Posts: 301
Registered: ‎10-16-2013

Re: Missing tables were not received in 120000m

What version of Impala are you running?

 

It would be great to understand in more depth how you got into this strange state. My guess is that if you run "invalidate metadata db2.EMAIL_ADDRESS" after doing the DDL transformations, then it shoud work in Impala.

 

The impalad logs you pasted show that the coordinator is waiting for the table metadata to be loaded and disseminated. You might find more information in the catalogd logs, for example, if the table loading failed for some reason.

 

Contributor
Posts: 54
Registered: ‎11-24-2017

Re: Missing tables were not received in 120000m

Impala version is: 

2.10.0-cdh5.13.1

 

I solved swithing from ALTER to CREATE statement and renaming fields directly in the query ("..SELECT field as field.."). For some reason the CREATE makes the Impala invalidate metadata working..

Announcements