You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Chao Wang (Jira)" <ji...@apache.org> on 2021/03/09 07:41:00 UTC
[jira] [Commented] (IOTDB-1186) Remove redundant sync meta leader
in query process for cluster module
[ https://issues.apache.org/jira/browse/IOTDB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297903#comment-17297903 ]
Chao Wang commented on IOTDB-1186:
----------------------------------
fixed , 0.12.0 version release...
> Remove redundant sync meta leader in query process for cluster module
> ---------------------------------------------------------------------
>
> Key: IOTDB-1186
> URL: https://issues.apache.org/jira/browse/IOTDB-1186
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Cluster
> Reporter: Xinyu Tan
> Assignee: Chao Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
>
> Currently, the coordinator will create one remoteSeriesReader for each timeseries if the timeseries belongs to other nodes, and the coordinator will try to perform a sync meta leader in each remoteSeriesReader's initManagedSeriesReader function, which cost a lot of network overhead.
> Actually, we can just sync meta leader once for one query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)