[jira] [Created] (IOTDB-5425) Consolidate all ConfigNodeClient to be managed by clientManager
Xinyu Tan created IOTDB-5425: Summary: Consolidate all ConfigNodeClient to be managed by clientManager Key: IOTDB-5425 URL: https://issues.apache.org/jira/browse/IOTDB-5425 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan On the one hand, it makes the code logical, and on the other hand, it may resolve ConfigNodeClient leaks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5423) Unit test failures of WALManager
[ https://issues.apache.org/jira/browse/IOTDB-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pai reassigned IOTDB-5423: --- Assignee: Eric Pai (was: Haiming Zhu) > Unit test failures of WALManager > > > Key: IOTDB-5423 > URL: https://issues.apache.org/jira/browse/IOTDB-5423 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/WAL >Reporter: Eric Pai >Assignee: Eric Pai >Priority: Major > > This is the only error outout > (14:42:03) [ERROR] Failures: > (14:42:03) [ERROR] WALManagerTest.testDeleteOutdatedWALFiles:84 > expected: but > was: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5423) Unit test failures of WALManager
[ https://issues.apache.org/jira/browse/IOTDB-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677624#comment-17677624 ] Eric Pai commented on IOTDB-5423: - I have debugged out this issue. As WALManger will init the NodeAllocationStrategy in the constructor, which is only called in a singleton mode. If a previous test inits this with FiristCreateStrategy, the test wil be failed, as it tests as depending on ElasticStrategy. The issue may be happened in other test cases, as long as they depend on the same singleton instance in one JVM. Two solution: # Disable reuseForks in surefie plugin. Each test class will use a new JVM process, so the singleton instance will be a new one. # Enable running test cases in a random order, so we can reproduce the failures casued by test order. > Unit test failures of WALManager > > > Key: IOTDB-5423 > URL: https://issues.apache.org/jira/browse/IOTDB-5423 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/WAL >Reporter: Eric Pai >Assignee: Haiming Zhu >Priority: Major > > This is the only error outout > (14:42:03) [ERROR] Failures: > (14:42:03) [ERROR] WALManagerTest.testDeleteOutdatedWALFiles:84 > expected: but > was: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5418) [Metric] Add mods file metrics
[ https://issues.apache.org/jira/browse/IOTDB-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongyin Zhang reassigned IOTDB-5418: Assignee: Liuxuxin (was: Hongyin Zhang) > [Metric] Add mods file metrics > -- > > Key: IOTDB-5418 > URL: https://issues.apache.org/jira/browse/IOTDB-5418 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Hongyin Zhang >Assignee: Liuxuxin >Priority: Major > Original Estimate: 12h > Remaining Estimate: 12h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5424) query_thread_count doesn't influence FI memory limit
Eric Pai created IOTDB-5424: --- Summary: query_thread_count doesn't influence FI memory limit Key: IOTDB-5424 URL: https://issues.apache.org/jira/browse/IOTDB-5424 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch The maxBytesPerFragmentInstance is computed only once when the class is loaded, and can never be changed even if the query_thread_count is set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
