Hi Shrikant,
The log indicated that your query needs data from a snapshot lookup table(your
query columns should contain some derived columns defined in the cube), but the
snapshot is very large, so the query is very slow. You may check the snapshot
size in the lookup table's snapshot tab in Kylin's portal.
At 2018-10-23 18:00:59, "Shrikant Bang" <b.shrikan...@gmail.com> wrote:
Hi Team,
I am observing some queries are running for longer time and getting failed.
Here is exception in kylin logs for "BadQueryDetector".
Could someone please help me to understand about Bad Queries and meaning of
below stack trace :
2018-10-23 09:36:40,647 DEBUG [BadQueryDetector]
badquery.BadQueryHistoryManager:65 : Loaded 22 Bad Query(s)
2018-10-23 09:36:40,652 INFO [BadQueryDetector]
service.BadQueryDetector:191 : Problematic thread 0x97 Query
33c76e71-450f-369b-ad81-c96ae763acf0-151, query id:
33c76e71-450f-369b-ad81-c96ae763acf0
at
org.apache.kylin.dict.TrieDictionary.lookupValueFromSeqNo(TrieDictionary.java:305)
at
org.apache.kylin.dict.TrieDictionary.getValueBytesFromIdImpl(TrieDictionary.java:262)
at
org.apache.kylin.dict.TrieDictionary.getValueBytesFromIdWithoutCache(TrieDictionary.java:249)
at
org.apache.kylin.dict.CacheDictionary.getValueFromIdImpl(CacheDictionary.java:81)
at
org.apache.kylin.common.util.Dictionary.getValueFromId(Dictionary.java:141)
at
org.apache.kylin.dict.lookup.SnapshotTable$1.getRow(SnapshotTable.java:170)
at org.apache.kylin.dict.lookup.LookupTable.init(LookupTable.java:69)
at
org.apache.kylin.dict.lookup.LookupStringTable.init(LookupStringTable.java:80)
at org.apache.kylin.dict.lookup.LookupTable.<init>(LookupTable.java:57)
at
org.apache.kylin.dict.lookup.LookupStringTable.<init>(LookupStringTable.java:66)
Thank You,
Shrikant Bang
