[jira] [Resolved] (KYLIN-2573) 'kylin.sh stop' can't kill kylin's process by sometimes.
[
https://issues.apache.org/jira/browse/KYLIN-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billy Liu resolved KYLIN-2573.
--
Resolution: Fixed
> 'kylin.sh stop' can't kill kylin's process by sometimes.
>
>
> Key: KYLIN-2573
> URL: https://issues.apache.org/jira/browse/KYLIN-2573
> Project: Kylin
> Issue Type: Bug
> Components: General
>Affects Versions: v1.6.0
> Environment: centos 6.7 X64
> jdk 1.7.o_55
> Hadoop 2.7.0
> hive 2.1.0
> kylin 1.6.0
> hbase 1.2.0
>Reporter: liuzhijiang
>Assignee: liuzhijiang
> Labels: patch
> Fix For: v2.1.0
>
> Attachments:
> 0001-KYLIN-2573-kylin.sh-stop-can-t-kill-kylin-s-process-.patch
>
>
> Somtime, Using 'kylin.sh stop' can't kill kylin process,it's better to use
> 'kill -9' to kill process.
> It will cause 'port is used' error when start kylin, and error messages like
> this"
> 信息: Initializing ProtocolHandler ["http-bio-7070"]
> 四月 27, 2017 2:56:16 下午 org.apache.coyote.AbstractProtocol init
> 严重: Failed to initialize end point associated with ProtocolHandler
> ["http-bio-7070"]
> java.net.BindException: 地址已在使用 :7070
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:413)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:650)
> at
> org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
> at
> org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtoc
> ol.java:119)
> "
> Which error is kylin.sh script,
> if [ -f "${KYLIN_PID}" ]
> then
> PID=`cat $KYLIN_PID`
> if ps -p $PID > /dev/null
> then
>echo "stopping Kylin:$PID"
>kill $PID -- sometime, this action couldn't kill process
>rm ${KYLIN_PID}
>exit 0
> It is should use 'kill -9 $PID' to instead 'kill $PID'.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2573) 'kylin.sh stop' can't kill kylin's process by sometimes.
[
https://issues.apache.org/jira/browse/KYLIN-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002088#comment-16002088
]
Billy Liu commented on KYLIN-2573:
--
Thanks [~liuzhijiang], patch merged.
https://github.com/apache/kylin/commit/901b10cee549a9c1e8d2df711a8c8d83789d7717
> 'kylin.sh stop' can't kill kylin's process by sometimes.
>
>
> Key: KYLIN-2573
> URL: https://issues.apache.org/jira/browse/KYLIN-2573
> Project: Kylin
> Issue Type: Bug
> Components: General
>Affects Versions: v1.6.0
> Environment: centos 6.7 X64
> jdk 1.7.o_55
> Hadoop 2.7.0
> hive 2.1.0
> kylin 1.6.0
> hbase 1.2.0
>Reporter: liuzhijiang
>Assignee: liuzhijiang
> Labels: patch
> Fix For: v2.1.0
>
> Attachments:
> 0001-KYLIN-2573-kylin.sh-stop-can-t-kill-kylin-s-process-.patch
>
>
> Somtime, Using 'kylin.sh stop' can't kill kylin process,it's better to use
> 'kill -9' to kill process.
> It will cause 'port is used' error when start kylin, and error messages like
> this"
> 信息: Initializing ProtocolHandler ["http-bio-7070"]
> 四月 27, 2017 2:56:16 下午 org.apache.coyote.AbstractProtocol init
> 严重: Failed to initialize end point associated with ProtocolHandler
> ["http-bio-7070"]
> java.net.BindException: 地址已在使用 :7070
> at
> org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:413)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:650)
> at
> org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
> at
> org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtoc
> ol.java:119)
> "
> Which error is kylin.sh script,
> if [ -f "${KYLIN_PID}" ]
> then
> PID=`cat $KYLIN_PID`
> if ps -p $PID > /dev/null
> then
>echo "stopping Kylin:$PID"
>kill $PID -- sometime, this action couldn't kill process
>rm ${KYLIN_PID}
>exit 0
> It is should use 'kill -9 $PID' to instead 'kill $PID'.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2557) The kylin will start failed because of creating HBase table confict when multiple instances of the kylin are started at the same time.
[ https://issues.apache.org/jira/browse/KYLIN-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002069#comment-16002069 ] peng.jianhua commented on KYLIN-2557: - Hi liyang, I had update the patch.Thanks. > The kylin will start failed because of creating HBase table confict when > multiple instances of the kylin are started at the same time. > -- > > Key: KYLIN-2557 > URL: https://issues.apache.org/jira/browse/KYLIN-2557 > Project: Kylin > Issue Type: Bug > Components: Storage - HBase >Affects Versions: v2.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Critical > Labels: patch > Attachments: 0001-KYLIN-2557-The-kylin-will-start-failed.patch > > > Muliple instances were started at the same time after we installed the kylin. > A conflict will occurs because these instances create kylin_metadata_acl > table at the same time. The result is that the kylin start failed. The error > log is as following: > Caused by: org.apache.hadoop.hbase.TableExistsException: kylin_metadata_acl > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.util.ForeignExceptionUtil.toIOException(ForeignExceptionUtil.java:45) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.convertResult(HBaseAdmin.java:4448) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:4406) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:4339) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:674) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:604) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:307) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:262) > at > org.apache.kylin.rest.security.RealAclHBaseStorage.prepareHBaseTable(RealAclHBaseStorage.java:50) > at > org.apache.kylin.rest.security.MockAclHBaseStorage.prepareHBaseTable(MockAclHBaseStorage.java:53) > at org.apache.kylin.rest.service.AclService.init(AclService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:344) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:295) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:130) > ... 125 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2586) use random port for CacheServiceTest as fixed port 7777 might have been occupied
[
https://issues.apache.org/jira/browse/KYLIN-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billy Liu resolved KYLIN-2586.
--
Resolution: Fixed
Fix Version/s: v2.1.0
https://github.com/apache/kylin/commit/783bb4eecdcd9d455d61009eef27f2508f14d8c8
> use random port for CacheServiceTest as fixed port might have been
> occupied
>
>
> Key: KYLIN-2586
> URL: https://issues.apache.org/jira/browse/KYLIN-2586
> Project: Kylin
> Issue Type: Improvement
>Reporter: hongbin ma
>Assignee: hongbin ma
> Fix For: v2.1.0
>
>
> https://builds.apache.org/job/Kylin-Master-JDK-1.7/442/
> 2017-05-04 02:24:45,913 WARN [main AbstractLifeCycle:212]: FAILED
> ServerConnector@29065a9f{HTTP/1.1}{0.0.0.0:}: java.net.BindException:
> Address already in use
> java.net.BindException: Address already in use
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2581) It seems to contention happening in Build Dimension Dictionary step
[ https://issues.apache.org/jira/browse/KYLIN-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001995#comment-16001995 ] Billy Liu commented on KYLIN-2581: -- Hi [~kangkaisen], do you think it's related to the issue you found in Kylin's broadcast sync? > It seems to contention happening in Build Dimension Dictionary step > --- > > Key: KYLIN-2581 > URL: https://issues.apache.org/jira/browse/KYLIN-2581 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.6.0 >Reporter: Kanta Kuramoto > Attachments: log.txt > > > If we put a list of servers include the server on which the configuration is > place kylin.rest.servers in Kylie properties, it rarely causes deadlock. > I have attached the log in case of deadlock happens. > We observed if we remove the server itself on which the configuration is > place from kylin.rest.servers, we can avoid the problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001989#comment-16001989 ] Billy Liu commented on KYLIN-2595: -- Hi [~wuyingjun], please follow http://kylin.apache.org/development/howto_contribute.html to prepare the patch. Thank you. > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: wuyingjun > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu reassigned KYLIN-2595: Assignee: wuyingjun (was: Zhong,Jason) > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: wuyingjun > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001984#comment-16001984 ] wuyingjun commented on KYLIN-2595: -- [~yimingliu] [~Shaofengshi] > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001980#comment-16001980 ] Billy Liu commented on KYLIN-2595: -- OK. I see. The "COL2" in your original case is the column name, not the alias name. My misunderstanding. It's a bug, the patch is welcomed. > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001978#comment-16001978 ] wuyingjun commented on KYLIN-2595: -- the dimesion result title is column name, but measure funcion result is alias > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2557) The kylin will start failed because of creating HBase table confict when multiple instances of the kylin are started at the same time.
[ https://issues.apache.org/jira/browse/KYLIN-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2557: Attachment: 0001-KYLIN-2557-The-kylin-will-start-failed.patch > The kylin will start failed because of creating HBase table confict when > multiple instances of the kylin are started at the same time. > -- > > Key: KYLIN-2557 > URL: https://issues.apache.org/jira/browse/KYLIN-2557 > Project: Kylin > Issue Type: Bug > Components: Storage - HBase >Affects Versions: v2.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Critical > Labels: patch > Attachments: 0001-KYLIN-2557-The-kylin-will-start-failed.patch > > > Muliple instances were started at the same time after we installed the kylin. > A conflict will occurs because these instances create kylin_metadata_acl > table at the same time. The result is that the kylin start failed. The error > log is as following: > Caused by: org.apache.hadoop.hbase.TableExistsException: kylin_metadata_acl > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.util.ForeignExceptionUtil.toIOException(ForeignExceptionUtil.java:45) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.convertResult(HBaseAdmin.java:4448) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:4406) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:4339) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:674) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:604) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:307) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:262) > at > org.apache.kylin.rest.security.RealAclHBaseStorage.prepareHBaseTable(RealAclHBaseStorage.java:50) > at > org.apache.kylin.rest.security.MockAclHBaseStorage.prepareHBaseTable(MockAclHBaseStorage.java:53) > at org.apache.kylin.rest.service.AclService.init(AclService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:344) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:295) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:130) > ... 125 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Attachment: QQ截图20170509113741.jpg > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: QQ截图20170509113741.jpg, screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2557) The kylin will start failed because of creating HBase table confict when multiple instances of the kylin are started at the same time.
[ https://issues.apache.org/jira/browse/KYLIN-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2557: Attachment: (was: 0001-KYLIN-2557-The-kylin-will-start-failed.patch) > The kylin will start failed because of creating HBase table confict when > multiple instances of the kylin are started at the same time. > -- > > Key: KYLIN-2557 > URL: https://issues.apache.org/jira/browse/KYLIN-2557 > Project: Kylin > Issue Type: Bug > Components: Storage - HBase >Affects Versions: v2.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Critical > Labels: patch > > Muliple instances were started at the same time after we installed the kylin. > A conflict will occurs because these instances create kylin_metadata_acl > table at the same time. The result is that the kylin start failed. The error > log is as following: > Caused by: org.apache.hadoop.hbase.TableExistsException: kylin_metadata_acl > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at > org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) > at > org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95) > at > org.apache.hadoop.hbase.util.ForeignExceptionUtil.toIOException(ForeignExceptionUtil.java:45) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.convertResult(HBaseAdmin.java:4448) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:4406) > at > org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:4339) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:674) > at > org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:604) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:307) > at > org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:262) > at > org.apache.kylin.rest.security.RealAclHBaseStorage.prepareHBaseTable(RealAclHBaseStorage.java:50) > at > org.apache.kylin.rest.security.MockAclHBaseStorage.prepareHBaseTable(MockAclHBaseStorage.java:53) > at org.apache.kylin.rest.service.AclService.init(AclService.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:344) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:295) > at > org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:130) > ... 125 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2413) Use one branch for HBase 1.x and CDH 5.7 binary packages
[ https://issues.apache.org/jira/browse/KYLIN-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu resolved KYLIN-2413. -- Resolution: Fixed Fix Version/s: v2.0.0 > Use one branch for HBase 1.x and CDH 5.7 binary packages > > > Key: KYLIN-2413 > URL: https://issues.apache.org/jira/browse/KYLIN-2413 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Dong Li >Assignee: Dong Li > Fix For: v2.0.0 > > > Currently the patch for cdh 5.7 contains little production code changes. > After we change hbase dependecy to 1.x on master branch, we can also use this > branch to generate CDH binary package with specific maven profile. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2592) build failed when it has distinct count measure with spark cubing
[ https://issues.apache.org/jira/browse/KYLIN-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001973#comment-16001973 ] Billy Liu commented on KYLIN-2592: -- Hi [~readme_kylin], you are right. Kylin should register MappeableBitmapContainer in "KylinKyroRegistrator.java". Do you want to contribute a patch, and verify it in your environment? > build failed when it has distinct count measure with spark cubing > -- > > Key: KYLIN-2592 > URL: https://issues.apache.org/jira/browse/KYLIN-2592 > Project: Kylin > Issue Type: Bug > Components: Spark Engine >Affects Versions: v2.0.0 > Environment: hadoop:2.6.4 > hive:2.1.0 > hbase:1.2.4 > spark(on yarn) >Reporter: readme_kylin > > I build the cube with distinct count measure using spark cubing engine,it > failed,it seems that something wrong with the bitMap. > Exception in thread "main" java.lang.RuntimeException: error execute > org.apache.kylin.engine.spark.SparkCubingByLayer > at > org.apache.kylin.common.util.AbstractApplication.execute(AbstractApplication.java:42) > at org.apache.kylin.common.util.SparkEntry.main(SparkEntry.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:731) > at > org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:181) > at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:206) > at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:121) > at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala) > Caused by: org.apache.spark.SparkException: Job aborted due to stage failure: > Task 133 in stage 13.0 failed 4 times, most recent failure: Lost task 133.3 > in stage 13.0 (TID 11796, QZ141): com.esotericsoftware.kryo.KryoException: > java.lang.IllegalArgumentException: Class is not registered: > org.apache.kylin.job.shaded.org.roaringbitmap.buffer.MappeableBitmapContainer > Note: To register this class use: > kryo.register(org.apache.kylin.job.shaded.org.roaringbitmap.buffer.MappeableBitmapContainer.class); > Serialization trace: > values > (org.apache.kylin.job.shaded.org.roaringbitmap.buffer.MutableRoaringArray) > highLowContainer > (org.apache.kylin.job.shaded.org.roaringbitmap.buffer.MutableRoaringBitmap) > bitmap (org.apache.kylin.measure.bitmap.RoaringBitmapCounter) > at > com.esotericsoftware.kryo.serializers.FieldSerializer$ObjectField.write(FieldSerializer.java:585) > at > com.esotericsoftware.kryo.serializers.FieldSerializer.write(FieldSerializer.java:213) > at com.esotericsoftware.kryo.Kryo.writeObject(Kryo.java:501) > at > com.esotericsoftware.kryo.serializers.FieldSerializer$ObjectField.write(FieldSerializer.java:564) > at > com.esotericsoftware.kryo.serializers.FieldSerializer.write(FieldSerializer.java:213) > at com.esotericsoftware.kryo.Kryo.writeObject(Kryo.java:501) > at > com.esotericsoftware.kryo.serializers.FieldSerializer$ObjectField.write(FieldSerializer.java:564) > at > com.esotericsoftware.kryo.serializers.FieldSerializer.write(FieldSerializer.java:213) > at com.esotericsoftware.kryo.Kryo.writeClassAndObject(Kryo.java:568) > at > com.esotericsoftware.kryo.serializers.DefaultArraySerializers$ObjectArraySerializer.write(DefaultArraySerializers.java:318) > at > com.esotericsoftware.kryo.serializers.DefaultArraySerializers$ObjectArraySerializer.write(DefaultArraySerializers.java:293) > at com.esotericsoftware.kryo.Kryo.writeClassAndObject(Kryo.java:568) > at com.twitter.chill.Tuple2Serializer.write(TupleSerializers.scala:37) > at com.twitter.chill.Tuple2Serializer.write(TupleSerializers.scala:33) > at com.esotericsoftware.kryo.Kryo.writeClassAndObject(Kryo.java:568) > at > org.apache.spark.serializer.KryoSerializationStream.writeObject(KryoSerializer.scala:194) > at > org.apache.spark.serializer.SerializationStream.writeAll(Serializer.scala:153) > at > org.apache.spark.storage.BlockManager.dataSerializeStream(BlockManager.scala:1252) > at > org.apache.spark.storage.BlockManager.dataSerialize(BlockManager.scala:1258) > at org.apache.spark.storage.MemoryStore.putArray(MemoryStore.scala:136) > at org.apache.spark.storage.BlockManager.doPut(BlockManager.scala:811) > at > org.apache.spark.storage.BlockManager.putArray(BlockManager.scala:687) > at >
[jira] [Commented] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001967#comment-16001967 ] Billy Liu commented on KYLIN-2595: -- The contribution is welcomed. I'm curious, why in your screenshot, the result title is the alias, not the column name. > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name to replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Summary: Result query should use alias name to replace dimension column name when used Keyword As (was: Result query should use alias name replace dimension column name when used Keyword As) > Result query should use alias name to replace dimension column name when used > Keyword As > - > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Request participants: Shaofeng SHI (was: ) > Result query should use alias name replace dimension column name when used > Keyword As > -- > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Description: when i check the result, the result found in the dimensions suggests that the title is column name rather than the alias name (was: when i query the result use sql contains the keyword as ， the result label is not alias name but column。) > Result query should use alias name replace dimension column name when used > Keyword As > -- > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i check the result, the result found in the dimensions suggests that > the title is column name rather than the alias name -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2595) Result query should use alias name replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001914#comment-16001914 ] wuyingjun commented on KYLIN-2595: -- Shaofeng SHI ，Please help me validating this bug. If it exsits , I want to submit a patch to kylin. > Result query should use alias name replace dimension column name when used > Keyword As > -- > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i query the result use sql contains the keyword as ， the result label is > not alias name but column。 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name replace dimension column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Summary: Result query should use alias name replace dimension column name when used Keyword As (was: Result query should use alias name replace column name when used Keyword As) > Result query should use alias name replace dimension column name when used > Keyword As > -- > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i query the result use sql contains the keyword as ， the result label is > not alias name but column。 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2595) Result query should use alias name replace column name when used Keyword As
[ https://issues.apache.org/jira/browse/KYLIN-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-2595: - Attachment: screenshot-1.png > Result query should use alias name replace column name when used Keyword As > > > Key: KYLIN-2595 > URL: https://issues.apache.org/jira/browse/KYLIN-2595 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: wuyingjun >Assignee: Zhong,Jason > Attachments: screenshot-1.png > > > when i query the result use sql contains the keyword as ， the result label is > not alias name but column。 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2595) Result query should use alias name replace column name when used Keyword As
wuyingjun created KYLIN-2595: Summary: Result query should use alias name replace column name when used Keyword As Key: KYLIN-2595 URL: https://issues.apache.org/jira/browse/KYLIN-2595 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v2.0.0, v1.6.0 Reporter: wuyingjun Assignee: Zhong,Jason when i query the result use sql contains the keyword as ， the result label is not alias name but column。 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-2587) "Convert Cuboid Data to HFile" failed on EMR 5.5
[
https://issues.apache.org/jira/browse/KYLIN-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI reassigned KYLIN-2587:
---
Assignee: (was: Dong Li)
Request participants: (was: )
> "Convert Cuboid Data to HFile" failed on EMR 5.5
>
>
> Key: KYLIN-2587
> URL: https://issues.apache.org/jira/browse/KYLIN-2587
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
> Environment: EMR 5.5, EMR 5.4
>Reporter: Shaofeng SHI
>
> Create a EMR 5.5 HBase cluser, download and start Kylin on the master node,
> and then create the sample cube. The cube build got many errors in the
> reducer of "Convert Cuboid Data to HFile" step. Error trace is:
> {code}
> 2017-05-05 08:02:13,057 WARN [main] org.apache.hadoop.hbase.zookeeper.ZKUtil:
> hconnection-0x4a67318f0x0, quorum=localhost:2181, baseZNode=/hbase Unable to
> set watcher on znode (/hbase/hbaseid)
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase/hbaseid
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1102)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:220)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:420)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:65)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:913)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:697)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at
> org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2$1.write(HFileOutputFormat2.java:213)
> at
> org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2$1.write(HFileOutputFormat2.java:167)
> at
> org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.write(ReduceTask.java:566)
> at
> org.apache.hadoop.mapreduce.task.TaskInputOutputContextImpl.write(TaskInputOutputContextImpl.java:89)
> at
> org.apache.hadoop.mapreduce.lib.reduce.WrappedReducer$Context.write(WrappedReducer.java:105)
> at
> org.apache.hadoop.hbase.mapreduce.KeyValueSortReducer.reduce(KeyValueSortReducer.java:53)
> at
> org.apache.hadoop.hbase.mapreduce.KeyValueSortReducer.reduce(KeyValueSortReducer.java:36)
> at org.apache.hadoop.mapreduce.Reducer.run(Reducer.java:171)
> at
> org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:635)
> at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:390)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1698)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> {code}
> I checked the environment, the hbase-site.xml is in /etc/hbase/conf folder,
> which appeared at the start position of "hbase classpath", looks good, but
> the reducer couldn't get zookeeper's info, so using the default value
> "localhost:2181".
> I bypassed this error by copy "hbase.zookeeper.quorum" from hbase-site.xml to
> $KYLIN_HOME/conf/kylin_job_conf.xml:
>
> hbase.zookeeper.quorum
> ip-nn-nn-nn-nn.ap-northeast-2.compute.internal
>
> It need a further investigation. Maybe is related with some change in hbase
> 1.3 (EMR 5.5)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2587) "Convert Cuboid Data to HFile" failed on EMR 5.5
[
https://issues.apache.org/jira/browse/KYLIN-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-2587:
Environment: EMR 5.5, EMR 5.4
Request participants: (was: )
> "Convert Cuboid Data to HFile" failed on EMR 5.5
>
>
> Key: KYLIN-2587
> URL: https://issues.apache.org/jira/browse/KYLIN-2587
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
> Environment: EMR 5.5, EMR 5.4
>Reporter: Shaofeng SHI
>Assignee: Dong Li
>
> Create a EMR 5.5 HBase cluser, download and start Kylin on the master node,
> and then create the sample cube. The cube build got many errors in the
> reducer of "Convert Cuboid Data to HFile" step. Error trace is:
> {code}
> 2017-05-05 08:02:13,057 WARN [main] org.apache.hadoop.hbase.zookeeper.ZKUtil:
> hconnection-0x4a67318f0x0, quorum=localhost:2181, baseZNode=/hbase Unable to
> set watcher on znode (/hbase/hbaseid)
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /hbase/hbaseid
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1102)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:220)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:420)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:65)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:913)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:697)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at
> org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2$1.write(HFileOutputFormat2.java:213)
> at
> org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2$1.write(HFileOutputFormat2.java:167)
> at
> org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.write(ReduceTask.java:566)
> at
> org.apache.hadoop.mapreduce.task.TaskInputOutputContextImpl.write(TaskInputOutputContextImpl.java:89)
> at
> org.apache.hadoop.mapreduce.lib.reduce.WrappedReducer$Context.write(WrappedReducer.java:105)
> at
> org.apache.hadoop.hbase.mapreduce.KeyValueSortReducer.reduce(KeyValueSortReducer.java:53)
> at
> org.apache.hadoop.hbase.mapreduce.KeyValueSortReducer.reduce(KeyValueSortReducer.java:36)
> at org.apache.hadoop.mapreduce.Reducer.run(Reducer.java:171)
> at
> org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:635)
> at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:390)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1698)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> {code}
> I checked the environment, the hbase-site.xml is in /etc/hbase/conf folder,
> which appeared at the start position of "hbase classpath", looks good, but
> the reducer couldn't get zookeeper's info, so using the default value
> "localhost:2181".
> I bypassed this error by copy "hbase.zookeeper.quorum" from hbase-site.xml to
> $KYLIN_HOME/conf/kylin_job_conf.xml:
>
> hbase.zookeeper.quorum
> ip-nn-nn-nn-nn.ap-northeast-2.compute.internal
>
> It need a further investigation. Maybe is related with some change in hbase
> 1.3 (EMR 5.5)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2594) After reloading metadata, the project list should refresh
[ https://issues.apache.org/jira/browse/KYLIN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001892#comment-16001892 ] pengjianlin commented on KYLIN-2594: Okey, my workmate is working on it. > After reloading metadata, the project list should refresh > - > > Key: KYLIN-2594 > URL: https://issues.apache.org/jira/browse/KYLIN-2594 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: pengjianlin >Assignee: pengjianlin > Labels: patch > > 1. excute sample.sh > 2. relead metadata > Thus, I want to see the 'learn_kylin' project in the project list, but it > not. When I refresh the page, the project appears. I think we should use ajax > to refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-2594) After reloading metadata, the project list should refresh
[ https://issues.apache.org/jira/browse/KYLIN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-2594: --- Assignee: pengjianlin (was: Zhong,Jason) > After reloading metadata, the project list should refresh > - > > Key: KYLIN-2594 > URL: https://issues.apache.org/jira/browse/KYLIN-2594 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: pengjianlin >Assignee: pengjianlin > Labels: patch > > 1. excute sample.sh > 2. relead metadata > Thus, I want to see the 'learn_kylin' project in the project list, but it > not. When I refresh the page, the project appears. I think we should use ajax > to refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2594) After reloading metadata, the project list should refresh
[ https://issues.apache.org/jira/browse/KYLIN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001888#comment-16001888 ] Shaofeng SHI commented on KYLIN-2594: - Yes, please go ahead to prepare a patch, thanks! > After reloading metadata, the project list should refresh > - > > Key: KYLIN-2594 > URL: https://issues.apache.org/jira/browse/KYLIN-2594 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: pengjianlin >Assignee: Zhong,Jason > Labels: patch > > 1. excute sample.sh > 2. relead metadata > Thus, I want to see the 'learn_kylin' project in the project list, but it > not. When I refresh the page, the project appears. I think we should use ajax > to refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2582) 'Server Config' should be refreshed automatically in web page 'System', after we update it successfully.
[ https://issues.apache.org/jira/browse/KYLIN-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-2582. --- Resolution: Fixed > 'Server Config' should be refreshed automatically in web page 'System', after > we update it successfully. > - > > Key: KYLIN-2582 > URL: https://issues.apache.org/jira/browse/KYLIN-2582 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2582-Server-Config-should-be-refreshed-automat.patch > > > When we update server config successfully, the web page still display the old > configuration. > We have to click the refresh button or refresh the page to see the modified > configuration items. > 'Reload Config' has the same problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2594) After reloading metadata, the project list should refresh
[ https://issues.apache.org/jira/browse/KYLIN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pengjianlin updated KYLIN-2594: --- Description: 1. excute sample.sh 2. relead metadata Thus, I want to see the 'learn_kylin' project in the project list, but it not. When I refresh the page, the project appears. I think we should use ajax to refresh the project list after releading metadata was: 1. excute sample.sh 2. relead metadata Thus, I want to see the 'learn_kylin' project in the project list, but it not. When I refresh the page, the project appears. I think we should use ajax the refresh the project list after releading metadata > After reloading metadata, the project list should refresh > - > > Key: KYLIN-2594 > URL: https://issues.apache.org/jira/browse/KYLIN-2594 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: pengjianlin >Assignee: Zhong,Jason > Labels: patch > > 1. excute sample.sh > 2. relead metadata > Thus, I want to see the 'learn_kylin' project in the project list, but it > not. When I refresh the page, the project appears. I think we should use ajax > to refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2594) After reloading metadata, the project list should refresh
[ https://issues.apache.org/jira/browse/KYLIN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000602#comment-16000602 ] pengjianlin commented on KYLIN-2594: Please help me validating this bug. If it exsits really, I want to submit a patch to kylin. > After reloading metadata, the project list should refresh > - > > Key: KYLIN-2594 > URL: https://issues.apache.org/jira/browse/KYLIN-2594 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v2.0.0 >Reporter: pengjianlin >Assignee: Zhong,Jason > Labels: patch > > 1. excute sample.sh > 2. relead metadata > Thus, I want to see the 'learn_kylin' project in the project list, but it > not. When I refresh the page, the project appears. I think we should use ajax > the refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2594) After reloading metadata, the project list should refresh
pengjianlin created KYLIN-2594: -- Summary: After reloading metadata, the project list should refresh Key: KYLIN-2594 URL: https://issues.apache.org/jira/browse/KYLIN-2594 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v2.0.0, v1.6.0 Reporter: pengjianlin Assignee: Zhong,Jason 1. excute sample.sh 2. relead metadata Thus, I want to see the 'learn_kylin' project in the project list, but it not. When I refresh the page, the project appears. I think we should use ajax the refresh the project list after releading metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2593) Query with Ton-N by count may fail
Dong Li created KYLIN-2593: -- Summary: Query with Ton-N by count may fail Key: KYLIN-2593 URL: https://issues.apache.org/jira/browse/KYLIN-2593 Project: Kylin Issue Type: Bug Components: Query Engine Reporter: Dong Li Assignee: liyang Stacktrace: ... at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.apache.kylin.metadata.tuple.TupleInfo.getFieldIndex(TupleInfo.java:64) at org.apache.kylin.measure.topn.TopNMeasureType.getAdvancedTupleFiller(TopNMeasureType.java:374) at org.apache.kylin.storage.gtrecord.CubeTupleConverter.(CubeTupleConverter.java:113) at org.apache.kylin.storage.gtrecord.GTCubeStorageQueryBase.newCubeTupleConverter(GTCubeStorageQueryBase.java:159) at org.apache.kylin.storage.gtrecord.SegmentCubeTupleIterator.(SegmentCubeTupleIterator.java:85) at org.apache.kylin.storage.gtrecord.SequentialCubeTupleIterator.(SequentialCubeTupleIterator.java:61) at org.apache.kylin.storage.gtrecord.GTCubeStorageQueryBase.search(GTCubeStorageQueryBase.java:93) at org.apache.kylin.query.enumerator.OLAPEnumerator.queryStorage(OLAPEnumerator.java:120) at org.apache.kylin.query.enumerator.OLAPEnumerator.moveNext(OLAPEnumerator.java:64) at Baz$1$1.moveNext(Unknown Source) at org.apache.calcite.linq4j.EnumerableDefaults.groupBy_(EnumerableDefaults.java:826) at org.apache.calcite.linq4j.EnumerableDefaults.groupBy(EnumerableDefaults.java:761) at org.apache.calcite.linq4j.DefaultEnumerable.groupBy(DefaultEnumerable.java:302) at Baz.bind(Unknown Source) at org.apache.calcite.jdbc.CalcitePrepare$CalciteSignature.enumerable(CalcitePrepare.java:331) at org.apache.calcite.jdbc.CalciteConnectionImpl.enumerable(CalciteConnectionImpl.java:294) at org.apache.calcite.jdbc.CalciteMetaImpl._createIterable(CalciteMetaImpl.java:553) at org.apache.calcite.jdbc.CalciteMetaImpl.createIterable(CalciteMetaImpl.java:544) at org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:193) at org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:67) at org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:44) at org.apache.calcite.avatica.AvaticaConnection$1.execute(AvaticaConnection.java:607) at org.apache.calcite.jdbc.CalciteMetaImpl.prepareAndExecute(CalciteMetaImpl.java:600) at org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:615) at org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:148) ... 77 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
