[
https://issues.apache.org/jira/browse/KYLIN-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916594#comment-16916594
]
ASF subversion and git services commented on KYLIN-4044:
--------------------------------------------------------
Commit 7b460d10c1e229508eedf87223fc97191bcf904b in kylin's branch
refs/heads/master from Chunen Ni
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=7b460d1 ]
Revert "#KYLIN-4044, upgrade curator dependency version"
This reverts commit 970899011211b285b78cfc3a63ac5025436ddb59.
> 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
> Fix For: v3.0.0-alpha2
>
>
> 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 it will 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
(v8.3.2#803003)
