[jira] [Created] (IOTDB-6184) Merge Sort finish one iterator too late.
yang caiyin created IOTDB-6184: -- Summary: Merge Sort finish one iterator too late. Key: IOTDB-6184 URL: https://issues.apache.org/jira/browse/IOTDB-6184 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-10-10-18-22-07-777.png There is a wrong implementationo in MergeSortOperator !image-2023-10-10-18-22-07-777.png! If the code break too late, the smaller value behind tsBlock won't be filled in time, resulting in a wrong order. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6185) Fix show cluster NPE bug
Yongzao Dan created IOTDB-6185: -- Summary: Fix show cluster NPE bug Key: IOTDB-6185 URL: https://issues.apache.org/jira/browse/IOTDB-6185 Project: Apache IoTDB Issue Type: Improvement Reporter: Yongzao Dan Assignee: Yongzao Dan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6184) Merge Sort finish one iterator too late.
[ https://issues.apache.org/jira/browse/IOTDB-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6184: Assignee: yang caiyin > Merge Sort finish one iterator too late. > > > Key: IOTDB-6184 > URL: https://issues.apache.org/jira/browse/IOTDB-6184 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > Attachments: image-2023-10-10-18-22-07-777.png > > > There is a wrong implementationo in MergeSortOperator > !image-2023-10-10-18-22-07-777.png! > If the code break too late, the smaller value behind tsBlock won't be filled > in time, resulting in a wrong order. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6181) [mlnode] Logging module and test framework
Haoran Zhang created IOTDB-6181: --- Summary: [mlnode] Logging module and test framework Key: IOTDB-6181 URL: https://issues.apache.org/jira/browse/IOTDB-6181 Project: Apache IoTDB Issue Type: New Feature Reporter: Haoran Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6181) [mlnode] Logging module and test framework
[ https://issues.apache.org/jira/browse/IOTDB-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haoran Zhang reassigned IOTDB-6181: --- Assignee: Haoran Zhang > [mlnode] Logging module and test framework > -- > > Key: IOTDB-6181 > URL: https://issues.apache.org/jira/browse/IOTDB-6181 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Haoran Zhang >Assignee: Haoran Zhang >Priority: Major > Original Estimate: 336h > Remaining Estimate: 336h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6182) Add fsync in ConfigNode persistence modules
Yongzao Dan created IOTDB-6182: -- Summary: Add fsync in ConfigNode persistence modules Key: IOTDB-6182 URL: https://issues.apache.org/jira/browse/IOTDB-6182 Project: Apache IoTDB Issue Type: Improvement Reporter: Yongzao Dan Assignee: Yongzao Dan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6183) Optimize the timeout retry logic of IoTConsensus sending RPCS
Xinyu Tan created IOTDB-6183: Summary: Optimize the timeout retry logic of IoTConsensus sending RPCS Key: IOTDB-6183 URL: https://issues.apache.org/jira/browse/IOTDB-6183 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan We should never let it time out, because the logic behind a timeout is also to retry, which might actually worsen the situation. For example, resulting in a significant increase in the number of file handles -- This message was sent by Atlassian Jira (v8.20.10#820010)
