Hi Shaofeng, Glad to hear from you. Thank you for your information. Another quick question, I understand that the estimated size is calculated before the cube built. However, when I tried to use count distinct (hyperloglog), it says "The coprocessor thread stopped itself due to scan timeout or scan threshold(check region server log), failing current query." I looked into this error and it seems like that this error happens because it used too much memory during query process. I set "kylin.query.memory-budget-bytes" to 3GB. I was wondering why this happens because the cube size is only 700MB. I checked the log and found that "gtrecord.GTCubeStorageQueryBase:343 : Memory budget is set to 49140 rows". I think this number is calculated by using 3GB/eachRowSize(16KB). Is that correct?
Thanks, Zhuoran -- View this message in context: http://apache-kylin.74782.x6.nabble.com/A-problem-in-cube-size-tp7737p7751.html Sent from the Apache Kylin mailing list archive at Nabble.com.
