[
https://issues.apache.org/jira/browse/KYLIN-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315206#comment-17315206
]
Xiaoxiang Yu commented on KYLIN-4952:
-------------------------------------
# Did your query hit the right cuboid?
# Have you ever try to configure "kylin.hbase.region.cut" to make this HTable
contains more regions.
> kylin - coprocessor timeout after scanning 10 439 900 rows
> ----------------------------------------------------------
>
> Key: KYLIN-4952
> URL: https://issues.apache.org/jira/browse/KYLIN-4952
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: v3.0.1
> Environment: Server details
> 1. OS : Ubuntu 18.04.5 LTS
> 2. RAM : 32 GB
> 3. Storage: 1 TB
> 4. CPU : 4 cpu
> Software version details
> · kylin-3.0.1
> · hadoop-2.7.0
> · hbase-1.1.2
> · hive-1.2.1
> Reporter: mohamed ismaiel
> Priority: Critical
> Attachments: KYLIN_COPROCESSOR_ISSUE.png
>
>
> We are using Kylin for OLAP which is integrated to HDFS system running in
> cloud environment. Kylin is connected to our Java BI Application using JDBC.
> Our's is currently a Standalone setup almost like a DEV environment without
> clusters.
> *{color:#FF0000}Coprocessor timeout issue{color}*
> Current data size in a fact table is about 150 million per year.
> h5. Segment: *20190401000000_20200331000000*
> * Status: READY
> * Start Time: 2019-04-01 00:00:00
> * End Time: 2020-03-31 00:00:00
> * Source Count: 152032244
> * HBase Table: KYLIN_X8BBJ2V6Q3
> * Region Count: 1
> * Size: 4.39844 GB
> while executing the Cube query we are getting coprocessor timeout after
> scanning 10439900 rows while executing SQL
> *Cube details*
> # Total Dimension count - 50
> # Total Metrics count - 7
> # Cuboid Count - 128
> # Lookup table - 10
> # Total Aggregation -10
> # joint dimension – 3
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
