[
https://issues.apache.org/jira/browse/IOTDB-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270009#comment-17270009
]
Tian Jiang commented on IOTDB-1118:
-----------------------------------
Thanks for your opinion, but
1. It may not be able to connect to the leader since the synchronization has
failed, but it may be useful in other cases.
2. That is already done by heart beat. Any lag will trigger catch-up.
> [Distributed] Limit query log lag in mid consistency level
> ----------------------------------------------------------
>
> Key: IOTDB-1118
> URL: https://issues.apache.org/jira/browse/IOTDB-1118
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Cluster
> Reporter: Tian Jiang
> Priority: Major
>
> We provide a middle level of read consistency, which is a best-effort
> strategy, and will try to synchronize with the leader and uses the local data
> when the synchronization times out. However, the maximum log lag is
> undefined, which means the node can be arbitrarily far from the leader
> (missing arbitrarily length of logs) and incurs inconvenience when the user
> wants to control the data freshness.
> To resolve this, a configuration should be provided like `max_read_log_lag`,
> which only takes effect when the consistency level is set to mid, and queries
> will fail if the log lag exceeds this configuration after a time out.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
