You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "PENG Zhengshuai (JIRA)" <ji...@apache.org> on 2019/06/14 03:27:00 UTC
[jira] [Updated] (KYLIN-4044) CuratorScheduler may throw NPE when
init service Cache
[ https://issues.apache.org/jira/browse/KYLIN-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
PENG Zhengshuai updated KYLIN-4044:
-----------------------------------
Description:
Currently Kylin uses Curator 2.12.0 dependencies.
There is an issue of CURATOR-452 which may affect Kylin Server Discovery.
When kylin server starts, it will discover other kylin server nodes in ZK path, and then register itself to ZK path. Curator discovery and cache implementation will initialize the service cache and deserialize the ServiceInstance by * JsonInstanceSerializer* which implemented by Kylin.
But the CURATOR-452 hasn't been back-ported to curator-2.x branch.
This curator issue may pass a Null value in JsonInstanceSerializer#deserialize(byte[] bytes) and cause the NPE.
Kylin now uses the zookeeper version dependency with version 3.4.13, so according to the curator compatibility in https://curator.apache.org/zk-compatibility.html#, I think it's safe to upgrade the Curator version to 4.0+ in Kylin
was:
Currently Kylin uses Curator 2.12.0 dependencies.
There is an issue of CURATOR-452 which may affect Kylin Server Discovery.
The CURATOR-452 links here: https://issues.apache.org/jira/browse/CURATOR-452, but this fix hasn't been back-ported to curator-2.x branch.
When kylin server starts, it will discover other kylin server nodes in ZK path, and then register itself to ZK path. Curator discovery and cache implementation will initialize the service cache and deserialize the ServiceInstance by * JsonInstanceSerializer* which implemented by Kylin.
This curator issue may pass a Null value in JsonInstanceSerializer#deserialize(byte[] bytes) and cause the NPE.
Kylin now uses the zookeeper version dependency with version 3.4.13, so according to the curator compatibility in https://curator.apache.org/zk-compatibility.html#, I think it's safe to upgrade the Curator version to 4.0+ in Kylin
> CuratorScheduler may throw NPE when init service Cache
> ------------------------------------------------------
>
> Key: KYLIN-4044
> URL: https://issues.apache.org/jira/browse/KYLIN-4044
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v3.0.0
> Reporter: PENG Zhengshuai
> Assignee: PENG Zhengshuai
> Priority: Major
>
> Currently Kylin uses Curator 2.12.0 dependencies.
> There is an issue of CURATOR-452 which may affect Kylin Server Discovery.
> When kylin server starts, it will discover other kylin server nodes in ZK path, and then register itself to ZK path. Curator discovery and cache implementation will initialize the service cache and deserialize the ServiceInstance by * JsonInstanceSerializer* which implemented by Kylin.
> But the CURATOR-452 hasn't been back-ported to curator-2.x branch.
> This curator issue may pass a Null value in JsonInstanceSerializer#deserialize(byte[] bytes) and cause the NPE.
> Kylin now uses the zookeeper version dependency with version 3.4.13, so according to the curator compatibility in https://curator.apache.org/zk-compatibility.html#, I think it's safe to upgrade the Curator version to 4.0+ in Kylin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)