kylin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Li Yang <liy...@apache.org>
Subject Re: The coprocessor thread stopped itself due to scan timeout or scan threshold(check region server log), failing current query
Date Fri, 02 Jun 2017 09:56:24 GMT
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 <35925138@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,还是不管用

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message