Hi,
Do you think that Kylin has too many output logs?      In Kylin, 
BadQueryDetector will check bad query every 60 seconds(default). It cannot be 
closed. You can change the interval time of detecting by changing 
kylin.query.timeout-seconds-coefficient and kylin.query.timeout-seconds.

Best wishes!

发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用

发件人: awaisaj...@gmail.com<mailto:awaisaj...@gmail.com>
发送时间: 2018年10月30日 22:31
收件人: dev@kylin.apache.org<mailto:dev@kylin.apache.org>
主题: APACHE KYLIN - Detect bad query

I am setting up Apache kylin , i configured all setting now i am and kylin is
connected to hive tables. when i make cube then it show bad query detected
and below logs continue all day.What could be the possible reason behind it
as there is no error showing in log file

*Logs are below and these line continue to generate in loop*

2018-10-30 18:55:45,614 INFO [BadQueryDetector] service.BadQueryDetector:147
: Detect bad query. 2018-10-30 18:55:50,243 INFO [FetcherRunner
1260543956-60] threadpool.DefaultFetcherRunner:96 : Job Fetcher: 1 should
running, 2 actual running, 0 stopped, 0 ready, 3 already succeed, 0 error, 0
discarded, 0 others 2018-10-30 18:56:20,240 INFO [FetcherRunner
1260543956-60] threadpool.DefaultFetcherRunner:96 : Job Fetcher: 1 should
running, 2 actual running, 0 stopped, 0 ready, 3 already succeed, 0 error, 0
discarded, 0 others

--
Sent from: http://apache-kylin.74782.x6.nabble.com/

Reply via email to