[jira] [Created] (KYLIN-4021) Async Broadcast of project schema may cause creating cube failed
Liu Shaohui created KYLIN-4021:
--
Summary: Async Broadcast of project schema may cause creating cube
failed
Key: KYLIN-4021
URL: https://issues.apache.org/jira/browse/KYLIN-4021
Project: Kylin
Issue Type: Bug
Components: Metadata
Reporter: Liu Shaohui
In our prod cluster, we found some creating cube requests failed for the model
not found.
The problem is that users will create the cube right after creating the model
success. But the the two requests may be routed to two different servers.
When the other server receive creating cube request, the project schema may be
not updated for the async Broadcast and the server can not found the model
related to the cube.
the log at query server 1
{code:java}
kylin.log.11:2019-05-27 10:26:44,143 INFO [http-bio-7070-exec-962]
model.DataModelManager:248 : Saving Model model_k1_bb_83_uyyy3636 to
Project BigBI_Hive with bigbi_kylin as owner
kylin.log.11:2019-05-27 10:26:44,144 INFO [http-bio-7070-exec-962]
model.DataModelManager:185 : Model model_k1_bb_83_uyyy3636 is missing or
unloaded yet
kylin.log.11:2019-05-27 10:26:44,145 INFO [http-bio-7070-exec-962]
persistence.ResourceStore:309 : Update resource:
/model_desc/model_k1_bb_83_uyyy3636.json with content:{code}
and the log at query server 2
{code:java}
2019-05-27 10:26:44,296 WARN [http-bio-7070-exec-132] cube.CubeDescManager:195
: Broken cube desc CubeDesc [name=cube_b_bb_83_uyyy3636]
java.lang.NullPointerException: DateModelDesc(model_k1_bb_83_uyyy3636) not
found
at
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:235)
at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:664)
at
org.apache.kylin.cube.CubeDescManager.createCubeDesc(CubeDescManager.java:193)
at
org.apache.kylin.rest.service.CubeService.createCubeAndDesc(CubeService.java:216)
at
org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:69)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673)
at
org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$20946622.createCubeAndDesc()
at
org.apache.kylin.rest.controller.CubeController.saveCubeDesc(CubeController.java:735)
at sun.reflect.GeneratedMethodAccessor341.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3961) Optimize TopN measure merge function to reduce TopNCounter errors
[ https://issues.apache.org/jira/browse/KYLIN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850322#comment-16850322 ] ASF GitHub Bot commented on KYLIN-3961: --- nichunen commented on pull request #612: KYLIN-3961 Optimize TopNCounter's merge function to reduce TopNCounter's error size. URL: https://github.com/apache/kylin/pull/612 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize TopN measure merge function to reduce TopNCounter errors > - > > Key: KYLIN-3961 > URL: https://issues.apache.org/jira/browse/KYLIN-3961 > Project: Kylin > Issue Type: Improvement > Components: Measure - TopN >Affects Versions: v2.5.2 > Environment: Huawei FusionInsight >Reporter: zhao jintao >Assignee: zhao jintao >Priority: Major > Labels: easyfix > Original Estimate: 168h > Remaining Estimate: 168h > > Hi Team: > I use "Top-N "measure to query such sql "select sum(AAA) from BBB group by > CCC,DDD", It is much better than a cube without "Top-N". > In my system, kylin cost just 0.2s to query sql with "Top-N" measure cube; If > without "Top-N" measure it may be cost 10s. > But I find that Top-N measure can be optimized to reduce errors. > I use kylin demo to test "TopN". > I build two cube using "KYLIN_SALES". The first cube has three > dimentions:"SELLER_ID","BUYER_ID" and "PART_DT", has one measures: > "SUM(PRICE)" . The second cube has one dimention:"PART_DT", has twon > measures: "SUM(PRICE)" and "TOPN(10)", the "ORDER|SUM by Column" of > "TOPN(10)" is "PRICE", the "Group by Column" of “TOPN(10)” is "SELLER_ID" > and "BUYER_ID",the "Return Type" of "TOPN(10)" is "Top 10". Then I build cube > from "2012-01-01" to "2014-01-01". > I use same sql to query two cube. I find that 2 cubes have a larger error. > The top5 "SUM PRICE" of first cube without "TopN" is "167.7269", "99.9908", > "99.9888","99.9865","99.978". > The top5 "SUM PRICE" of second cube with "TopN" is > "179.27699...","167.6320...","167.3050...","167.2069...","166.7429...". > Does any one meet same problem? > > Best regards. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] nichunen commented on issue #612: KYLIN-3961 Optimize TopNCounter's merge function to reduce TopNCounter's error size.
nichunen commented on issue #612: KYLIN-3961 Optimize TopNCounter's merge function to reduce TopNCounter's error size. URL: https://github.com/apache/kylin/pull/612#issuecomment-496763289 Close this pr for it violates the design of the topn algorithm. @zhaojintaozhao Please reopen it if you can provide more convincing evidence This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] nichunen closed pull request #612: KYLIN-3961 Optimize TopNCounter's merge function to reduce TopNCounter's error size.
nichunen closed pull request #612: KYLIN-3961 Optimize TopNCounter's merge function to reduce TopNCounter's error size. URL: https://github.com/apache/kylin/pull/612 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (KYLIN-4018) apache kylin 连接powerbi出错
[ https://issues.apache.org/jira/browse/KYLIN-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-4018: - Issue Type: Wish (was: Bug) > apache kylin 连接powerbi出错 > > > Key: KYLIN-4018 > URL: https://issues.apache.org/jira/browse/KYLIN-4018 > Project: Kylin > Issue Type: Wish > Components: Driver - ODBC > Environment: apache kylin，powerbi desktop >Reporter: jamie_lee >Priority: Major > > 我在将apache kylin的数据源连接到powebi > desktop时使用了KylinODBCDriver的驱动，好像只支持导入模式，不支持directquery模式，以至于虽然连接成功了，但是导入的数据好像格式有些问题(有些类型为bigint的字段显示为0)，所以现在apache > kylin和powerbi之间的odbc驱动不支持directquery模式了么？或者是不是我现在用的驱动不对？我应该用哪个驱动呢？求解答，谢谢！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-4018) apache kylin 连接powerbi出错
[ https://issues.apache.org/jira/browse/KYLIN-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850317#comment-16850317 ] Billy Liu commented on KYLIN-4018: -- As far as I know, Kylin ODBC Driver could not support DirectQuery mode yet. But some 3rd ODBC Driver provider for Kylin announced the support for DirectQuery between PowerBI and Kylin Query Engine. You may search for that. > apache kylin 连接powerbi出错 > > > Key: KYLIN-4018 > URL: https://issues.apache.org/jira/browse/KYLIN-4018 > Project: Kylin > Issue Type: Bug > Components: Driver - ODBC > Environment: apache kylin，powerbi desktop >Reporter: jamie_lee >Priority: Major > > 我在将apache kylin的数据源连接到powebi > desktop时使用了KylinODBCDriver的驱动，好像只支持导入模式，不支持directquery模式，以至于虽然连接成功了，但是导入的数据好像格式有些问题(有些类型为bigint的字段显示为0)，所以现在apache > kylin和powerbi之间的odbc驱动不支持directquery模式了么？或者是不是我现在用的驱动不对？我应该用哪个驱动呢？求解答，谢谢！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-4020) fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed
[ https://issues.apache.org/jira/browse/KYLIN-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850301#comment-16850301 ] Shaofeng SHI commented on KYLIN-4020: - Hi Yuzhang, there is no previous reporting; Please go ahead. Thank you! > fix_length rowkey encode without sepecified length can be saved but cause > CreateHTable step failed > -- > > Key: KYLIN-4020 > URL: https://issues.apache.org/jira/browse/KYLIN-4020 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v2.5.2 >Reporter: Yuzhang QIU >Priority: Major > > Hi dear team: > Just as title said. > Maybe there should have more strict check for advanced settings, I think. > How do you think about this? > If there already have same JIRA，please inform me and close this one. > > Best regards > > yuzhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-4015) Kylin build cube error at the "Build UHC Dictionary" step
[ https://issues.apache.org/jira/browse/KYLIN-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-4015: Fix Version/s: v2.6.3 > Kylin build cube error at the "Build UHC Dictionary" step > - > > Key: KYLIN-4015 > URL: https://issues.apache.org/jira/browse/KYLIN-4015 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.5.2 > Environment: Fusion Insight >Reporter: zhao jintao >Assignee: zhao jintao >Priority: Major > Labels: easyfix > Fix For: v2.6.3 > > Original Estimate: 168h > Remaining Estimate: 168h > > Hi All: > We know, kylin builds dimension dictionary in kylin job client. But if a cube > has uhc dimensions, it will cost much more CPU and memory resources. Kylin > provides the ability to build uhc dictionary using the MR engine to reduce > the resource consumption of the build engine. > But I find that the "Build UHC Dictionary" step build error. This step run > using MR engine. This is the error info from yarn: > org.apache.hadoop.mapred.YarnChild: Exception running child : > java.io.IOException: > hdfs://hacluster/xxx.../xxx/fact_distinct_columns/xxx/FIELD_NAME.dic-r-1 > not a SequenceFile. > at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:) > at org.apache.hadoop.io.SequenceFile$Reader.initialize(SequenceFile.java:) > at org.apache.hadoop.io.SequenceFile$Reader.(SequenceFile.java:) > The reason of this problem is that the "Extract Fact Table Distinct " step > output two type of files:".dci" and ".rldict"; but the ".dci" file is not a > sequence file, so the "Build UHC Dictionary" step should filter ".dci" file > when run with MR engine. > I resolve this problem and will summit my code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-4015) Kylin build cube error at the "Build UHC Dictionary" step
[ https://issues.apache.org/jira/browse/KYLIN-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850291#comment-16850291 ] Shaofeng SHI commented on KYLIN-4015: - I see, the ".dci" file was generated for keeping each dimension's min/max info, which is introduced in KYLIN-3370, the files should be excluded. > Kylin build cube error at the "Build UHC Dictionary" step > - > > Key: KYLIN-4015 > URL: https://issues.apache.org/jira/browse/KYLIN-4015 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.5.2 > Environment: Fusion Insight >Reporter: zhao jintao >Assignee: zhao jintao >Priority: Major > Labels: easyfix > Original Estimate: 168h > Remaining Estimate: 168h > > Hi All: > We know, kylin builds dimension dictionary in kylin job client. But if a cube > has uhc dimensions, it will cost much more CPU and memory resources. Kylin > provides the ability to build uhc dictionary using the MR engine to reduce > the resource consumption of the build engine. > But I find that the "Build UHC Dictionary" step build error. This step run > using MR engine. This is the error info from yarn: > org.apache.hadoop.mapred.YarnChild: Exception running child : > java.io.IOException: > hdfs://hacluster/xxx.../xxx/fact_distinct_columns/xxx/FIELD_NAME.dic-r-1 > not a SequenceFile. > at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:) > at org.apache.hadoop.io.SequenceFile$Reader.initialize(SequenceFile.java:) > at org.apache.hadoop.io.SequenceFile$Reader.(SequenceFile.java:) > The reason of this problem is that the "Extract Fact Table Distinct " step > output two type of files:".dci" and ".rldict"; but the ".dci" file is not a > sequence file, so the "Build UHC Dictionary" step should filter ".dci" file > when run with MR engine. > I resolve this problem and will summit my code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4020) fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed
Yuzhang QIU created KYLIN-4020: -- Summary: fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed Key: KYLIN-4020 URL: https://issues.apache.org/jira/browse/KYLIN-4020 Project: Kylin Issue Type: Improvement Components: Metadata Affects Versions: v2.5.2 Reporter: Yuzhang QIU Hi dear team: Just as title said. Maybe there should have more strict check for advanced settings, I think. How do you think about this? If there already have same JIRA，please inform me and close this one. Best regards yuzhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3996) postgresql can not to be used to construct the flat hive table in NO.1 step in building cube via datasourcedefaultSdk
[ https://issues.apache.org/jira/browse/KYLIN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849659#comment-16849659 ] haijiandu edited comment on KYLIN-3996 at 5/28/19 11:57 PM: ok,finally it is done. the method is that after kylin.source.default=16,reboot kylin, then to construct the new project , relevant model and cube instead of using previous old project when kylin.source.default=8. was (Author: duhj2): ok,finally it is done. the method is that after kylin.source.default=16,reboot kylin, then to construct the new project and relevant model and cube instead of using previous project when kylin.source.default=8. > postgresql can not to be used to construct the flat hive table in NO.1 step > in building cube via datasourcedefaultSdk > - > > Key: KYLIN-3996 > URL: https://issues.apache.org/jira/browse/KYLIN-3996 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC >Affects Versions: v2.6.1 > Environment: kylin3.0.0+hadoop2.7.4+hive2.1.1+hbase1.2.6 >Reporter: haijiandu >Assignee: XiaoXiang Yu >Priority: Critical > Labels: datasource, postgresql, sdk > Attachments: kylin_log_error_1.jpg, kylin_log_error_2.jpg, > kylin_log_error_3.jpg, kylin_log_error_4.jpg, kylin_log_error_5.jpg, > kylin_properties_duhj.jpg, kylin_sql.jpg, > kylin_sqoopToflatHiveTable_Error.jpg, postgresql_xml.jpg, > server_config_kylin_1.jpg, server_config_kylin_1.jpg, > server_config_kylin_2.jpg > > > postgresql can not to be used to construct the flat hive table in NO.1 step > in building cube via datasourcedefaultSdk. whether in kylin.properties or in > postgresql.xml，corresponding configureations have been finished as required > by official specification.There alwarys occurs a problem such as "ERROR > manager.SqlManager: Error executing statement: > org.postgresql.util.PSQLException: > ERROR: syntax error at or near ".", > when kylin is linked to postgresql databese, it seems that the errors happen > in sql brought by kylin. the sql has back quote,as it is "`" ,that causes > query failure brought by table name and columns defined by back quote(`). > as required, in kylin.properties ,its configuration has been as followings > kylin.source.default=16 > kylin.source.jdbc.connection-url=jdbc:postgresql://192.168.75.123:5432/dvdrental > kylin.source.jdbc.driver=org.postgresql.Driver > kylin.source.jdbc.dialect=postgresql > kylin.source.jdbc.adaptor=org.apache.kylin.sdk.datasource.adaptor.DefaultAdaptor > kylin.source.jdbc.user=postgres > kylin.source.jdbc.pass=1234 > kylin.source.jdbc.sqoop-home=/duhj/sqoop-1.4.7.bin__hadoop-2.6.0 > kylin.source.jdbc.filed-delimiter=| > kylin.source.jdbc.sqoop-mapper-num=4 > what is more, in > ~/apache-kylin-3.0/conf/datasource/postgresql.xml，corresponding conf is as > followings: > - > > > > > > > > > > > is there a method to solve it? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-4018) apache kylin 连接powerbi出错
[ https://issues.apache.org/jira/browse/KYLIN-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jamie_lee updated KYLIN-4018: - Environment: apache kylin，powerbi desktop Description: 我在将apache kylin的数据源连接到powebi desktop时使用了KylinODBCDriver的驱动，好像只支持导入模式，不支持directquery模式，以至于虽然连接成功了，但是导入的数据好像格式有些问题(有些类型为bigint的字段显示为0)，所以现在apache kylin和powerbi之间的odbc驱动不支持directquery模式了么？或者是不是我现在用的驱动不对？我应该用哪个驱动呢？求解答，谢谢！ > apache kylin 连接powerbi出错 > > > Key: KYLIN-4018 > URL: https://issues.apache.org/jira/browse/KYLIN-4018 > Project: Kylin > Issue Type: Bug > Components: Driver - ODBC > Environment: apache kylin，powerbi desktop >Reporter: jamie_lee >Priority: Major > > 我在将apache kylin的数据源连接到powebi > desktop时使用了KylinODBCDriver的驱动，好像只支持导入模式，不支持directquery模式，以至于虽然连接成功了，但是导入的数据好像格式有些问题(有些类型为bigint的字段显示为0)，所以现在apache > kylin和powerbi之间的odbc驱动不支持directquery模式了么？或者是不是我现在用的驱动不对？我应该用哪个驱动呢？求解答，谢谢！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4019) I had a problem when I tried to make a connection from kylin to powerbi with KylinODBCDriver,the connection was sucessful but the data seemed wrong,I was wondering whethe
jamie_lee created KYLIN-4019: Summary: I had a problem when I tried to make a connection from kylin to powerbi with KylinODBCDriver,the connection was sucessful but the data seemed wrong,I was wondering whether I used the correct driver?or the KylinODBCDriver didn't support directquery mode? r Key: KYLIN-4019 URL: https://issues.apache.org/jira/browse/KYLIN-4019 Project: Kylin Issue Type: Bug Reporter: jamie_lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4018) apache kylin 连接powerbi出错
jamie_lee created KYLIN-4018: Summary: apache kylin 连接powerbi出错 Key: KYLIN-4018 URL: https://issues.apache.org/jira/browse/KYLIN-4018 Project: Kylin Issue Type: Bug Components: Driver - ODBC Reporter: jamie_lee -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3996) postgresql can not to be used to construct the flat hive table in NO.1 step in building cube via datasourcedefaultSdk
[ https://issues.apache.org/jira/browse/KYLIN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849659#comment-16849659 ] haijiandu commented on KYLIN-3996: -- ok,finally it is done. the method is that after kylin.source.default=16,reboot kylin, then to construct the new project and relevant model and cube instead of using previous project when kylin.source.default=8. > postgresql can not to be used to construct the flat hive table in NO.1 step > in building cube via datasourcedefaultSdk > - > > Key: KYLIN-3996 > URL: https://issues.apache.org/jira/browse/KYLIN-3996 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC >Affects Versions: v2.6.1 > Environment: kylin3.0.0+hadoop2.7.4+hive2.1.1+hbase1.2.6 >Reporter: haijiandu >Assignee: XiaoXiang Yu >Priority: Critical > Labels: datasource, postgresql, sdk > Attachments: kylin_log_error_1.jpg, kylin_log_error_2.jpg, > kylin_log_error_3.jpg, kylin_log_error_4.jpg, kylin_log_error_5.jpg, > kylin_properties_duhj.jpg, kylin_sql.jpg, > kylin_sqoopToflatHiveTable_Error.jpg, postgresql_xml.jpg, > server_config_kylin_1.jpg, server_config_kylin_1.jpg, > server_config_kylin_2.jpg > > > postgresql can not to be used to construct the flat hive table in NO.1 step > in building cube via datasourcedefaultSdk. whether in kylin.properties or in > postgresql.xml，corresponding configureations have been finished as required > by official specification.There alwarys occurs a problem such as "ERROR > manager.SqlManager: Error executing statement: > org.postgresql.util.PSQLException: > ERROR: syntax error at or near ".", > when kylin is linked to postgresql databese, it seems that the errors happen > in sql brought by kylin. the sql has back quote,as it is "`" ,that causes > query failure brought by table name and columns defined by back quote(`). > as required, in kylin.properties ,its configuration has been as followings > kylin.source.default=16 > kylin.source.jdbc.connection-url=jdbc:postgresql://192.168.75.123:5432/dvdrental > kylin.source.jdbc.driver=org.postgresql.Driver > kylin.source.jdbc.dialect=postgresql > kylin.source.jdbc.adaptor=org.apache.kylin.sdk.datasource.adaptor.DefaultAdaptor > kylin.source.jdbc.user=postgres > kylin.source.jdbc.pass=1234 > kylin.source.jdbc.sqoop-home=/duhj/sqoop-1.4.7.bin__hadoop-2.6.0 > kylin.source.jdbc.filed-delimiter=| > kylin.source.jdbc.sqoop-mapper-num=4 > what is more, in > ~/apache-kylin-3.0/conf/datasource/postgresql.xml，corresponding conf is as > followings: > - > > > > > > > > > > > is there a method to solve it? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] coveralls commented on issue #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work
coveralls commented on issue #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work URL: https://github.com/apache/kylin/pull/664#issuecomment-496467819 ## Pull Request Test Coverage Report for [Build 4552](https://coveralls.io/builds/23644495) * **0** of **3** **(0.0%)** changed or added relevant lines in **2** files are covered. * **6** unchanged lines in **3** files lost coverage. * Overall coverage decreased (**-0.0007%**) to **28.298%** --- | Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | | :-|--||---: | | [core-common/src/main/java/org/apache/kylin/common/util/ZKUtil.java](https://coveralls.io/builds/23644495/source?filename=core-common%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcommon%2Futil%2FZKUtil.java#L87) | 0 | 1 | 0.0% | [core-job/src/main/java/org/apache/kylin/job/lock/zookeeper/ZookeeperDistributedLock.java](https://coveralls.io/builds/23644495/source?filename=core-job%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fjob%2Flock%2Fzookeeper%2FZookeeperDistributedLock.java#L96) | 0 | 2 | 0.0% | Files with Coverage Reduction | New Missed Lines | % | | :-|--|--: | | [server-base/src/main/java/org/apache/kylin/rest/util/QueryRequestLimits.java](https://coveralls.io/builds/23644495/source?filename=server-base%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Frest%2Futil%2FQueryRequestLimits.java#L72) | 1 | 47.62% | | [core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java](https://coveralls.io/builds/23644495/source?filename=core-job%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fjob%2Fimpl%2Fthreadpool%2FDefaultScheduler.java#L194) | 2 | 80.23% | | [core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java](https://coveralls.io/builds/23644495/source?filename=core-cube%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcube%2Finmemcubing%2FMemDiskStore.java#L449) | 3 | 78.42% | | Totals | [](https://coveralls.io/builds/23644495) | | :-- | --: | | Change from base [Build 4541](https://coveralls.io/builds/2358): | -0.0007% | | Covered Lines: | 23249 | | Relevant Lines: | 82157 | --- # - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (KYLIN-4017) Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work.
[
https://issues.apache.org/jira/browse/KYLIN-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849583#comment-16849583
]
ASF GitHub Bot commented on KYLIN-4017:
---
wangxiaojing123 commented on pull request #664: KYLIN-4017 Build engine get
zk(zookeeper) lock failed when building job, it causes the whole build engine
doesn't work
URL: https://github.com/apache/kylin/pull/664
```
【Type】：BUG
【Severity】：1-Blocker
【Module】：Build Engine
【Description】：Kylin build engine occasionally appears to be unable to get
the ZK lock exception, and once this build engine appears, it will not work and
can only be restarted to solve.Usually this problem will recur one day after
the build engine starts.
【Design】：Setting the cache for curator is never invalid (unless the service
stops) and check the state before use curator instance (if closed ,create a new
curator instance and put into the cache)
```
```
issue: https://issues.apache.org/jira/browse/KYLIN-4017
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Build engine get zk(zookeeper) lock failed when building job, it causes the
> whole build engine doesn't work.
>
>
> Key: KYLIN-4017
> URL: https://issues.apache.org/jira/browse/KYLIN-4017
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine, Tools, Build and Test
>Affects Versions: Future, v3.0.0, v3.0.0-alpha
>Reporter: wangxiaojing
>Priority: Critical
> Labels: build
> Fix For: Future, v3.0.0-alpha
>
> Attachments: zkinstancestart.png
>
>
> Kylin has ZK acquisition lock exception when it is building job. Only restart
> can solve this problem. Otherwise, it can't build job ,the whole build engine
> doesn't work.This problem will continue to occur one day after restart. Log
> looks like below:
> {code:java}
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:59 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} prepare to schedule and its priority is 20
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:63 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} scheduled
> 2019-05-15 11:09:43,209 DEBUG [Scheduler 719764581 Job
> 878974c4-4c65-88a4-a912-b238fcc33bdc-132]
> zookeeper.ZookeeperDistributedLock:92 :
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> 2019-05-15 11:09:43,212 ERROR [pool-12-thread-10]
> threadpool.DistributedScheduler:115 : unknown error execute
> job:878974c4-4c65-88a4-a912-b238fcc33bdc in server:
> 18...@bigdata-kylin-build01.gz01.diditaxi.com
> java.lang.IllegalStateException: Error while
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:99)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperJobLock.lock(ZookeeperJobLock.java:41)
> at
> org.apache.kylin.job.impl.threadpool.DistributedScheduler$JobRunner.run(DistributedScheduler.java:105)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: instance must be started before
> calling this method
> at
> org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:176)
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.create(CuratorFrameworkImpl.java:351)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:95)
> ... 5 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [kylin] asfgit commented on issue #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work
asfgit commented on issue #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work URL: https://github.com/apache/kylin/pull/664#issuecomment-496459129 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [kylin] wangxiaojing123 opened a new pull request #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work
wangxiaojing123 opened a new pull request #664: KYLIN-4017 Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work URL: https://github.com/apache/kylin/pull/664 ``` 【Type】：BUG 【Severity】：1-Blocker 【Module】：Build Engine 【Description】：Kylin build engine occasionally appears to be unable to get the ZK lock exception, and once this build engine appears, it will not work and can only be restarted to solve.Usually this problem will recur one day after the build engine starts. 【Design】：Setting the cache for curator is never invalid (unless the service stops) and check the state before use curator instance (if closed ,create a new curator instance and put into the cache) ``` ``` issue: https://issues.apache.org/jira/browse/KYLIN-4017 ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (KYLIN-4017) Build engine get zk(zookeeper) lock failed when building job, it causes the whole build engine doesn't work.
[
https://issues.apache.org/jira/browse/KYLIN-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangxiaojing updated KYLIN-4017:
Summary: Build engine get zk(zookeeper) lock failed when building job, it
causes the whole build engine doesn't work. (was: Build engine get
zk(zookeeper) lock failed when building job, it can't build job ,the whole
build engine doesn't work.)
> Build engine get zk(zookeeper) lock failed when building job, it causes the
> whole build engine doesn't work.
>
>
> Key: KYLIN-4017
> URL: https://issues.apache.org/jira/browse/KYLIN-4017
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine, Tools, Build and Test
>Affects Versions: Future, v3.0.0, v3.0.0-alpha
>Reporter: wangxiaojing
>Priority: Critical
> Labels: build
> Fix For: Future, v3.0.0-alpha
>
> Attachments: zkinstancestart.png
>
>
> Kylin has ZK acquisition lock exception when it is building job. Only restart
> can solve this problem. Otherwise, it can't build job ,the whole build engine
> doesn't work.This problem will continue to occur one day after restart. Log
> looks like below:
> {code:java}
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:59 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} prepare to schedule and its priority is 20
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:63 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} scheduled
> 2019-05-15 11:09:43,209 DEBUG [Scheduler 719764581 Job
> 878974c4-4c65-88a4-a912-b238fcc33bdc-132]
> zookeeper.ZookeeperDistributedLock:92 :
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> 2019-05-15 11:09:43,212 ERROR [pool-12-thread-10]
> threadpool.DistributedScheduler:115 : unknown error execute
> job:878974c4-4c65-88a4-a912-b238fcc33bdc in server:
> 18...@bigdata-kylin-build01.gz01.diditaxi.com
> java.lang.IllegalStateException: Error while
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:99)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperJobLock.lock(ZookeeperJobLock.java:41)
> at
> org.apache.kylin.job.impl.threadpool.DistributedScheduler$JobRunner.run(DistributedScheduler.java:105)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: instance must be started before
> calling this method
> at
> org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:176)
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.create(CuratorFrameworkImpl.java:351)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:95)
> ... 5 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-4017) Build engine get zk(zookeeper) lock failed when building job, it can't build job ,the whole build engine doesn't work.
[
https://issues.apache.org/jira/browse/KYLIN-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangxiaojing updated KYLIN-4017:
Summary: Build engine get zk(zookeeper) lock failed when building job, it
can't build job ,the whole build engine doesn't work. (was: Zookeeper trying
to get lock exception, Only restart can solve this problem. Otherwise, it can't
build job ,the whole build engine doesn't work.)
> Build engine get zk(zookeeper) lock failed when building job, it can't build
> job ,the whole build engine doesn't work.
> --
>
> Key: KYLIN-4017
> URL: https://issues.apache.org/jira/browse/KYLIN-4017
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine, Tools, Build and Test
>Affects Versions: Future, v3.0.0, v3.0.0-alpha
>Reporter: wangxiaojing
>Priority: Critical
> Labels: build
> Fix For: Future, v3.0.0-alpha
>
> Attachments: zkinstancestart.png
>
>
> Kylin has ZK acquisition lock exception when it is building job. Only restart
> can solve this problem. Otherwise, it can't build job ,the whole build engine
> doesn't work.This problem will continue to occur one day after restart. Log
> looks like below:
> {code:java}
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:59 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} prepare to schedule and its priority is 20
> 2019-05-15 11:09:43,209 INFO [FetcherRunner 1910115020-57]
> threadpool.FetcherRunner:63 :
> CubingJob{id=878974c4-4c65-88a4-a912-b238fcc33bdc, name=BUILD CUBE -
> es_report_respnse_rate_cube - 2019051300_2019051400 - GMT+08:00
> 2019-05-15 11:03:15, state=READY} scheduled
> 2019-05-15 11:09:43,209 DEBUG [Scheduler 719764581 Job
> 878974c4-4c65-88a4-a912-b238fcc33bdc-132]
> zookeeper.ZookeeperDistributedLock:92 :
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> 2019-05-15 11:09:43,212 ERROR [pool-12-thread-10]
> threadpool.DistributedScheduler:115 : unknown error execute
> job:878974c4-4c65-88a4-a912-b238fcc33bdc in server:
> 18...@bigdata-kylin-build01.gz01.diditaxi.com
> java.lang.IllegalStateException: Error while
> 18...@bigdata-kylin-build01.gz01.diditaxi.com trying to lock
> /job_engine/lock/878974c4-4c65-88a4-a912-b238fcc33bdc
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:99)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperJobLock.lock(ZookeeperJobLock.java:41)
> at
> org.apache.kylin.job.impl.threadpool.DistributedScheduler$JobRunner.run(DistributedScheduler.java:105)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: instance must be started before
> calling this method
> at
> org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:176)
> at
> org.apache.curator.framework.imps.CuratorFrameworkImpl.create(CuratorFrameworkImpl.java:351)
> at
> org.apache.kylin.job.lock.zookeeper.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:95)
> ... 5 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
