hi Chun’en Ni, hi Donald,Zheng,

thanks for your reminder.
I try to modified hbase.zookeeper.quorum setting without port 2181 in 
hbase-side.xml and it can running build now. 

--
Best regards,
Wang Ke

> 在 2017年3月7日,下午3:42,Donald,Zheng(vip.com) <[email protected]> 写道:
> 
> If your kylin job server restarted recently, it might due to the job lock, 
> please refer https://issues.apache.org/jira/browse/KYLIN-1998
> 
> -----邮件原件-----
> 发件人: Chunen Ni [mailto:[email protected]]
> 发送时间: 2017年3月7日 15:12
> 收件人: [email protected]
> 主题: Re: [kylin1.5.3]cube build PENDING
> 
> Hi Wang Ke,
> Please check your log, is there any Error or Exception?
> I can not check the root cause for the log you pasted.
> Best regards,
> 
> Chun’en Ni(倪春恩)
> Mail: [email protected] <mailto:[email protected]> Shanghai 
> Kyligence Information Technology Co., Ltd
> 上海市浦东新区亮秀路112号Y1座405室
> 
> 
> 在 2017/3/7 下午1:38,“wangke”<[email protected]> 写入:
> 
>    hi all,
> 
>    I try to use kylin1.5.3 build kylin_sales_cube, the status was stayed in 
> pending long time.
>    Is the following information sufficient to determine the cause.
> 
>    kylin.log
>    --------------------
>    2017-03-07 13:04:52,931 DEBUG [http-bio-7070-exec-10] 
> service.AclService:307 : ACL of 
> org.springframework.security.acls.domain.ObjectIdentityImpl[Type: 
> org.apache.kylin.job.JobInstance; Identifier: 
> 71f97214-38a1-430b-bcac-8ad4d6d7ff95] updated successfully.
>    2017-03-07 13:04:55,752 DEBUG [http-bio-7070-exec-10] 
> controller.UserController:64 : authentication.getPrincipal() is 
> org.springframework.security.core.userdetails.User@3b40b2f: Username: ADMIN; 
> Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; 
> credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: 
> ROLE_ADMIN,ROLE_ANALYST,ROLE_MODELER
>    2017-03-07 13:04:55,781 DEBUG [http-bio-7070-exec-9] 
> badquery.BadQueryHistoryManager:84 : Loaded 0 Bad Query(s)
>    2017-03-07 13:05:58,245 DEBUG [http-bio-7070-exec-6] 
> controller.UserController:64 : authentication.getPrincipal() is 
> org.springframework.security.core.userdetails.User@3b40b2f: Username: ADMIN; 
> Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; 
> credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: 
> ROLE_ADMIN,ROLE_ANALYST,ROLE_MODELER
>    2017-03-07 13:05:59,144 DEBUG [http-bio-7070-exec-9] 
> controller.UserController:64 : authentication.getPrincipal() is 
> org.springframework.security.core.userdetails.User@3b40b2f: Username: ADMIN; 
> Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; 
> credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: 
> ROLE_ADMIN,ROLE_ANALYST,ROLE_MODELER
>    2017-03-07 13:05:59,187 DEBUG [http-bio-7070-exec-4] 
> badquery.BadQueryHistoryManager:84 : Loaded 0 Bad Query(s)
>    ——————————
> 
>    kylin.properties
>    ----------
>    # kylin server's mode
>    kylin.server.mode=all
> 
>    # The metadata store in hbase
>    kylin.metadata.url=kylin_metadata1.5.3@hbase
> 
>    # The storage for final cube file in hbase
>    kylin.storage.url=hbase
> 
>    # Temp folder in hdfs, make sure user has the right access to the hdfs 
> directory
>    kylin.hdfs.working.dir=/kylin1.5.3
> 
>    # Used by test cases to prepare synthetic data for sample cube
>    kylin.job.remote.cli.working.dir=/tmp/kylin1.5.3
> 
>    saml.context.contextPath=/kylin1.5.3
>    ----------
> 
> 
>    --
>    Best regards,
>    Wang Ke.
> 
> 
> 本电子邮件可能为保密文件。如果阁下非电子邮件所指定之收件人,谨请立即通知本人。敬请阁下不要使用、保存、复印、打印、散布本电子邮件及其内容,或将其用于其他任何目的或向任何人披露。谢谢您的合作!
>  This communication is intended only for the addressee(s) and may contain 
> information that is privileged and confidential. You are hereby notified 
> that, if you are not an intended recipient listed above, or an authorized 
> employee or agent of an addressee of this communication responsible for 
> delivering e-mail messages to an intended recipient, any dissemination, 
> distribution or reproduction of this communication (including any attachments 
> hereto) is strictly prohibited. If you have received this communication in 
> error, please notify us immediately by a reply e-mail addressed to the sender 
> and permanently delete the original e-mail communication and any attachments 
> from all storage devices without making or otherwise retaining a copy.


Reply via email to