Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Impala cannot read via short circuit

avatar

Hi Cloudera, 

I see a lot of these warnings in Impala Daemon logs:

 

W0516 07:12:24.227567  1049 ShortCircuitCache.java:826] ShortCircuitCache(0x119fb869): could not load 1399296933_BP-76826636-10.197.31.86-1501521881839 due to InvalidToken exception.

Does it indicate some bad configuration? What can I do to eliminate these warnings?

Thanks

 

1 ACCEPTED SOLUTION

avatar
Super Guru
Hi Tomas,

This message is normal behaviour and expected to happen when the Datanode's security key manager rolls its keys.

It will cause clients to print this whenever they use the older cached keys, but the post-action of printing this message is that the client refetches the new key and the job completes.

Since Impala is a client of HDFS, there is no concern or worry about this message, as it is part of normal operation. We also see this from HBase logs, which is again, normal.

Hope above helps.

Cheers
Eric

View solution in original post

1 REPLY 1

avatar
Super Guru
Hi Tomas,

This message is normal behaviour and expected to happen when the Datanode's security key manager rolls its keys.

It will cause clients to print this whenever they use the older cached keys, but the post-action of printing this message is that the client refetches the new key and the job completes.

Since Impala is a client of HDFS, there is no concern or worry about this message, as it is part of normal operation. We also see this from HBase logs, which is again, normal.

Hope above helps.

Cheers
Eric