Most likely it is hbase performance issue. You can verify by scanning the KYLIN_XXX htable directly in hbase shell.
On Tue, Jun 6, 2017 at 9:43 AM, 35925138 <35925...@qq.com> wrote: > fdz的基数没有多少，几百个最多了。 > > > > > ------------------ 原始邮件 ------------------ > 发件人: "Li Yang";<liy...@apache.org>; > 发送时间: 2017年6月2日(星期五) 下午5:56 > 收件人: "dev"<dev@kylin.apache.org>; > > 主题: Re: The coprocessor thread stopped itself due to scan timeout or > scanthreshold(check region server log), failing current query > > > > The region server has scanner too many rows or for too long and aborted > itself. > > How many powerful is your hbase cluster? And what cardinality of fdz is? > > On Fri, Jun 2, 2017 at 11:15 AM, 35925138 <35925...@qq.com> wrote: > > > 在查询cube时，遇到如下错误，可能会是哪方面的原因Error while executing SQL "select > > count(distinct userid) as nums,fdz from useraction group by fdz order by > > nums desc LIMIT 10": <sub-thread for Query 4c0b9af3-afde-44b8-bcb0- > 9e51738d4126 > > GTScanRequest 17fa104d>The coprocessor thread stopped itself due to scan > > timeout or scan threshold(check region server log), failing current > query... > > > > > > 我再kylin.properties里，设置了kylin.query.scan.threshold=900000000，还是不管用 >
