You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "kangkaisen (JIRA)" <ji...@apache.org> on 2017/06/29 13:23:00 UTC
[jira] [Resolved] (KYLIN-2652) Make KylinConfig threadsafe in
CubeVisitService
[ https://issues.apache.org/jira/browse/KYLIN-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kangkaisen resolved KYLIN-2652.
-------------------------------
Resolution: Fixed
> Make KylinConfig threadsafe in CubeVisitService
> -----------------------------------------------
>
> Key: KYLIN-2652
> URL: https://issues.apache.org/jira/browse/KYLIN-2652
> Project: Kylin
> Issue Type: Bug
> Components: Storage - HBase
> Affects Versions: v2.0.0
> Reporter: kangkaisen
> Assignee: kangkaisen
> Attachments: KYLIN-2652.patch
>
>
> Currently, the KylinConfig in CubeVisitService is not threadsafe. This bug didn't expose until KYLIN-2195 updated the naming convention for kylin properties.
> When user upgrade to Kylin 2.0, If user set kylin.query.endpoint.compression.result=false and user only upgrade one QueryServer to 2.0 firstly. The config kylin.query.endpoint.compression.result will change to kylin.storage.hbase.endpoint-compress-result, So the CubeVisitService in HBase will get {{kylinConfig.getCompressionResult()}} true and is not consistent with the QueryServer config, which will make the query failed.
> The KylinConfig in CubeVisitService is not threadsafe, which will not only make the one QueryServer updated query failed, but also all JobServer and all QueryServer query failed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)