Hi all,

I am facing issue when Tableau 10.2 runs query, the kylin node going down
whenever Tableau runs query.
I am not understanding what is the actual issue? Should we load the whole
data in Tableau then prepare a sheet or something other than this. 

Whenever I check the kylin logs I am getting below exception.

2017-04-24 23:55:06,074 INFO  [BadQueryDetector]
service.BadQueryDetector:179 : Slow query has been running 1881.406 seconds
(project:MyTaxMarketing, thread: 0x79, user:ANALYST) -- SELECT * FROM
"DEFAULT"."Tablename"
2017-04-24 23:55:30,967 DEBUG [BadQueryDetector]
badquery.BadQueryHistoryManager:84 : Loaded 10 Bad Query(s)
2017-04-24 23:56:05,746 DEBUG [BadQueryDetector]
hbase.HBaseResourceStore:262 : Update row /bad_query/******.json from oldTs:
1493103211146, to newTs: 1493103330968, operation result: true
2017-04-24 23:56:57,935 INFO  [BadQueryDetector]
service.BadQueryDetector:169 : Problematic thread 0x79
        at java.nio.HeapByteBuffer.slice(HeapByteBuffer.java:98)
        at org.apache.kylin.common.util.ByteArray.asBuffer(ByteArray.java:136)
        at org.apache.kylin.gridtable.GTRecord.getValues(GTRecord.java:129)
        at
org.apache.kylin.storage.gtrecord.CubeTupleConverter.translateResult(CubeTupleConverter.java:207)
        at
org.apache.kylin.storage.gtrecord.SegmentCubeTupleIterator.hasNext(SegmentCubeTupleIterator.java:100)
        at com.google.common.collect.Iterators$5.hasNext(Iterators.java:596)
        at
org.apache.kylin.storage.gtrecord.SequentialCubeTupleIterator.hasNext(SequentialCubeTupleIterator.java:84)
        at
org.apache.kylin.query.enumerator.OLAPEnumerator.moveNext(OLAPEnumerator.java:68)
        at
org.apache.calcite.linq4j.Linq4j$EnumeratorIterator.next(Linq4j.java:673)
        at
org.apache.calcite.avatica.util.IteratorCursor.next(IteratorCursor.java:46)

Thank You,
Rahul Singh

--
View this message in context: 
http://apache-kylin.74782.x6.nabble.com/Server-goes-down-while-Tableau-query-is-running-tp7764.html
Sent from the Apache Kylin mailing list archive at Nabble.com.

Reply via email to