Hi all,
We are facing some errors due to timeout exception.
{"url":"http://<masternode>:7070/kylin/api/jobs/349d62e3-7748-46ee-8009-3085726b5933","exception":"java.lang.RuntimeException:
org.apache.kylin.job.exception.PersistentException:
java.net.SocketTimeoutException: callTimeout=60000, callDuration=63012: row
'/execute/349d62e3-7748-46ee-8009-3085726b5933' on table 'kylin_metadata' at
region=kylin_metadata,/dict/VIEW_CREDITO/COD_PROMOTOR/a61c83e7-01e7-4971-9539-dd5c7ed07dff.dict,1500376865680.301b695304237ff0d1a7774bbff83b67.,
hostname=<node>,16020,1501960877256,
seqNum=163046"}----------------------------------------------------------------------
We have already changed the following properties
hbase.client.scanner.timeout.period and hbase.rpc.timeout to 600.000. Is
there any other property to change?
Sometimes, after getting timeout error Kylin_log_timeout.Kylin_log_timeout
<http://apache-kylin.74782.x6.nabble.com/file/n8658/Kylin_log_timeout.Kylin_log_timeout>
s, some jobs just disappear from web monitor or get its status changed to
Error.
We are also facing some errors like "java.lang.IllegalStateException: No
resource found at -- /dict/", is there any chance this occur because of
timeout error?
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/Timeout-when-refreshing-a-cube-tp8658.html
Sent from the Apache Kylin mailing list archive at Nabble.com.
