Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Solved
Go to solution
Impala cannot read via short circuit
Labels:
- Labels:
-
Apache Impala
Guru
Created on ‎05-15-2019 11:31 PM - edited ‎09-16-2022 07:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Super Guru
Created ‎05-18-2019 05:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
1 REPLY 1
Super Guru
Created ‎05-18-2019 05:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
