[jira] [Created] (IOTDB-6119) Add ConfigNode leader service check
Yongzao Dan created IOTDB-6119: -- Summary: Add ConfigNode leader service check Key: IOTDB-6119 URL: https://issues.apache.org/jira/browse/IOTDB-6119 Project: Apache IoTDB Issue Type: Improvement Reporter: Yongzao Dan Assignee: Yongzao Dan The ConfigNode-leader can't provide services until all of its leader services are ready. Therefore there should add another AtomicBoolean to mark the leader services' status. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6118) Support transfer data through air gap
陈哲涵 created IOTDB-6118: -- Summary: Support transfer data through air gap Key: IOTDB-6118 URL: https://issues.apache.org/jira/browse/IOTDB-6118 Project: Apache IoTDB Issue Type: Bug Reporter: 陈哲涵 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6118) Support transfer data through air gap
[ https://issues.apache.org/jira/browse/IOTDB-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 陈哲涵 reassigned IOTDB-6118: -- Assignee: 陈哲涵 > Support transfer data through air gap > - > > Key: IOTDB-6118 > URL: https://issues.apache.org/jira/browse/IOTDB-6118 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 陈哲涵 >Assignee: 陈哲涵 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6117) Pipe: Optimize RPC requests from cn to dn
马子坤 created IOTDB-6117: -- Summary: Pipe: Optimize RPC requests from cn to dn Key: IOTDB-6117 URL: https://issues.apache.org/jira/browse/IOTDB-6117 Project: Apache IoTDB Issue Type: Improvement Reporter: 马子坤 Currently, cn sends pipeMeta of all existing pipes to each dn upon create/start/stop/drop pipe, which may be time-comsuming. In this PR, cn will send exactly one pipeMeta to each dn upon create/start/stop/drop pipe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6116) Disassociate the IoTConsensus retry logic from the forkjoinPool
Xinyu Tan created IOTDB-6116: Summary: Disassociate the IoTConsensus retry logic from the forkjoinPool Key: IOTDB-6116 URL: https://issues.apache.org/jira/browse/IOTDB-6116 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan The current IoTConsensus Batch retry logic relies on the forkjoinPool and takes the thread to sleep synchronously, This may lead to frequent timeouts in the follower "waiting target request timeout. current index", So we use a ScheduledExecutorService to unbind the restart logic from the forkjoinPool -- This message was sent by Atlassian Jira (v8.20.10#820010)
