Hi Shaofeng Shi, 

Looking for some information on Hbase UI I realized that the node informed
in the log was stopped during the process. So this explaind the timeout,

java.net.SocketTimeoutException: callTimeout=60000, callDuration=63012: row
'/execute/349d62e3-7748-46ee-8009-3085726b5933' on table 'kylin_metadata' at
/hostname=<node>,/16020,1501960877256, seqNum=163046"}

We are running a Cluster on AWS EMR (hbase in S3) and using the tasknodes
with autoscalling feature turned on, I´m understandig that this node was
decomissioned due this configuration.

Can you see any other problem we migth face?    

Thanks for answering my post.

View this message in context: 
Sent from the Apache Kylin mailing list archive at Nabble.com.

Reply via email to