[jira] [Created] (IOTDB-6095) Tsfiles in sequence space may be overlap with each other due to LastFlushTime bug

Jinrui Zhang created IOTDB-6095: --- Summary: Tsfiles in sequence space may be overlap with each other due to LastFlushTime bug Key: IOTDB-6095 URL: https://issues.apache.org/jira/browse/IOTDB-6095

[jira] [Assigned] (IOTDB-5964) Add correctness check for target file of compaction

[ https://issues.apache.org/jira/browse/IOTDB-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5964: --- Sprint: 2023-3-Storage Assignee: 周沛辰 Description: # Add correctness check

[jira] [Created] (IOTDB-5964) Add

Jinrui Zhang created IOTDB-5964: --- Summary: Add Key: IOTDB-5964 URL: https://issues.apache.org/jira/browse/IOTDB-5964 Project: Apache IoTDB Issue Type: Improvement Reporter: Jinrui

[jira] [Created] (IOTDB-5928) DeadLock between TTL and Compaction

Jinrui Zhang created IOTDB-5928: --- Summary: DeadLock between TTL and Compaction Key: IOTDB-5928 URL: https://issues.apache.org/jira/browse/IOTDB-5928 Project: Apache IoTDB Issue Type:

[jira] [Created] (IOTDB-5859) Compaction error when using Version as first sort dimension

Jinrui Zhang created IOTDB-5859: --- Summary: Compaction error when using Version as first sort dimension Key: IOTDB-5859 URL: https://issues.apache.org/jira/browse/IOTDB-5859 Project: Apache IoTDB

[jira] [Assigned] (IOTDB-5843) Write operation won't be rejected even if the NodeStatus is ReadOnly

[ https://issues.apache.org/jira/browse/IOTDB-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5843: --- Assignee: Song Ziyang > Write operation won't be rejected even if the NodeStatus is

[jira] [Created] (IOTDB-5843) Write operation won't be rejected even if the NodeStatus

Jinrui Zhang created IOTDB-5843: --- Summary: Write operation won't be rejected even if the NodeStatus Key: IOTDB-5843 URL: https://issues.apache.org/jira/browse/IOTDB-5843 Project: Apache IoTDB

[jira] [Created] (IOTDB-5827) Change default multi_dir_strategy to SequenceStrategy and fix original bug

Jinrui Zhang created IOTDB-5827: --- Summary: Change default multi_dir_strategy to SequenceStrategy and fix original bug Key: IOTDB-5827 URL: https://issues.apache.org/jira/browse/IOTDB-5827 Project:

[jira] [Commented] (IOTDB-4593) [Remove-DataNode] Removing nodes writes data

[ https://issues.apache.org/jira/browse/IOTDB-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714495#comment-17714495 ] Jinrui Zhang commented on IOTDB-4593: - Not a blocking issue > [Remove-DataNode] Removing nodes

[jira] [Commented] (IOTDB-5063) [ start datanode ] Failed to start Grpc server

[ https://issues.apache.org/jira/browse/IOTDB-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714494#comment-17714494 ] Jinrui Zhang commented on IOTDB-5063: - Suggest to re-test the scenario > [ start datanode ] Failed

[jira] [Commented] (IOTDB-5557) [ metadata ] The metadata query results are inconsistent

[ https://issues.apache.org/jira/browse/IOTDB-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714493#comment-17714493 ] Jinrui Zhang commented on IOTDB-5557: - DataNode should be ready (visible to client) until all the

[jira] [Commented] (IOTDB-5781) Change the default strategy to SequenceStrategy

[ https://issues.apache.org/jira/browse/IOTDB-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713918#comment-17713918 ] Jinrui Zhang commented on IOTDB-5781: - In other words, only all the data_dirs' space is less than 5%,

[jira] [Commented] (IOTDB-5703) Memtable won't be flushed for a long while even if the time_partition is inactive

[ https://issues.apache.org/jira/browse/IOTDB-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17702430#comment-17702430 ] Jinrui Zhang commented on IOTDB-5703: - Checked with [~HeimingZ] , current timed_flush mechanism works

[jira] [Created] (IOTDB-5704) Optimize default parameters in iotdb-common for WAL part

Jinrui Zhang created IOTDB-5704: --- Summary: Optimize default parameters in iotdb-common for WAL part Key: IOTDB-5704 URL: https://issues.apache.org/jira/browse/IOTDB-5704 Project: Apache IoTDB

[jira] [Created] (IOTDB-5703) Memtable won't be flushed for a long while even if the time_partition is inactive

Jinrui Zhang created IOTDB-5703: --- Summary: Memtable won't be flushed for a long while even if the time_partition is inactive Key: IOTDB-5703 URL: https://issues.apache.org/jira/browse/IOTDB-5703

[jira] [Assigned] (IOTDB-5667) Compaction scheduler strategy issue

[ https://issues.apache.org/jira/browse/IOTDB-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5667: --- Assignee: 周沛辰 (was: Jinrui Zhang) > Compaction scheduler strategy issue >

[jira] [Created] (IOTDB-5667) Compaction scheduler strategy issue

Jinrui Zhang created IOTDB-5667: --- Summary: Compaction scheduler strategy issue Key: IOTDB-5667 URL: https://issues.apache.org/jira/browse/IOTDB-5667 Project: Apache IoTDB Issue Type:

[jira] [Created] (IOTDB-5628) SchemaRegion with 1 replica occurs error when restarting IoTDB server

Jinrui Zhang created IOTDB-5628: --- Summary: SchemaRegion with 1 replica occurs error when restarting IoTDB server Key: IOTDB-5628 URL: https://issues.apache.org/jira/browse/IOTDB-5628 Project: Apache

[jira] [Created] (IOTDB-5626) SchemaRegion with 1 replica occurs error when restarting IoTDB server

Jinrui Zhang created IOTDB-5626: --- Summary: SchemaRegion with 1 replica occurs error when restarting IoTDB server Key: IOTDB-5626 URL: https://issues.apache.org/jira/browse/IOTDB-5626 Project: Apache

[jira] [Created] (IOTDB-5625) SchemaRegion with 1 replica occurs error when restarting IoTDB server

Jinrui Zhang created IOTDB-5625: --- Summary: SchemaRegion with 1 replica occurs error when restarting IoTDB server Key: IOTDB-5625 URL: https://issues.apache.org/jira/browse/IOTDB-5625 Project: Apache

[jira] [Created] (IOTDB-5614) Error when restarting cluster and write client in GeelyCarTest

Jinrui Zhang created IOTDB-5614: --- Summary: Error when restarting cluster and write client in GeelyCarTest Key: IOTDB-5614 URL: https://issues.apache.org/jira/browse/IOTDB-5614 Project: Apache IoTDB

[jira] [Assigned] (IOTDB-5472) [Atmos]The number of tsfiles went up between db6f17e 【02/01】and 5602d0e【02/05】

[ https://issues.apache.org/jira/browse/IOTDB-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5472: --- Assignee: Haiming Zhu > [Atmos]The number of tsfiles went up between db6f17e 【02/01】and

[jira] [Created] (IOTDB-5511) Metrics of running compaction task is not accurate

Jinrui Zhang created IOTDB-5511: --- Summary: Metrics of running compaction task is not accurate Key: IOTDB-5511 URL: https://issues.apache.org/jira/browse/IOTDB-5511 Project: Apache IoTDB Issue

[jira] [Created] (IOTDB-5509) Limit the level of unseq file in cross compaction

Jinrui Zhang created IOTDB-5509: --- Summary: Limit the level of unseq file in cross compaction Key: IOTDB-5509 URL: https://issues.apache.org/jira/browse/IOTDB-5509 Project: Apache IoTDB Issue

[jira] [Created] (IOTDB-5508) System backup Tools

Jinrui Zhang created IOTDB-5508: --- Summary: System backup Tools Key: IOTDB-5508 URL: https://issues.apache.org/jira/browse/IOTDB-5508 Project: Apache IoTDB Issue Type: Improvement

[jira] [Commented] (IOTDB-5140) Add metrics for compaction deserializing pages or writing chunks

[ https://issues.apache.org/jira/browse/IOTDB-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681995#comment-17681995 ] Jinrui Zhang commented on IOTDB-5140: - PR towards rel/1.0 is not merged  > Add metrics for

[jira] [Commented] (IOTDB-5206) Fix when target file is deleted in Compaction exception handler and recover

[ https://issues.apache.org/jira/browse/IOTDB-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681993#comment-17681993 ] Jinrui Zhang commented on IOTDB-5206: - The fix is approved but not merged because of IT failures >

[jira] [Commented] (IOTDB-5140) Add metrics for compaction deserializing pages or writing chunks

[ https://issues.apache.org/jira/browse/IOTDB-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681841#comment-17681841 ] Jinrui Zhang commented on IOTDB-5140: - Need to put another PR to rel/1.0 > Add metrics for

[jira] [Reopened] (IOTDB-5140) Add metrics for compaction deserializing pages or writing chunks

[ https://issues.apache.org/jira/browse/IOTDB-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reopened IOTDB-5140: - > Add metrics for compaction deserializing pages or writing chunks >

[jira] [Commented] (IOTDB-5164) [disk]datanode takes too much disk space, should improve

[ https://issues.apache.org/jira/browse/IOTDB-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681832#comment-17681832 ] Jinrui Zhang commented on IOTDB-5164: - 这个issue 可以关闭了吗？ > [disk]datanode takes too much disk space,

[jira] [Assigned] (IOTDB-4001) Only unseq files reach a certain number can they be selected in cross compaction

[ https://issues.apache.org/jira/browse/IOTDB-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4001: --- Sprint: 2023-1-Storage (was: StorageEngine-Backlog) Assignee: Wenwei Shu (was: 周沛辰)

[jira] [Commented] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655937#comment-17655937 ] Jinrui Zhang commented on IOTDB-5319: - we have reverted this PR for release 1.0.1. Let's keep

[jira] [Created] (IOTDB-5385) Optimize the DataRegion leader calculation policy when ConfigNode leader changes

Jinrui Zhang created IOTDB-5385: --- Summary: Optimize the DataRegion leader calculation policy when ConfigNode leader changes Key: IOTDB-5385 URL: https://issues.apache.org/jira/browse/IOTDB-5385

[jira] [Created] (IOTDB-5363) Try to construct InsertTablet from InsertRowsNode to speed up write operation

Jinrui Zhang created IOTDB-5363: --- Summary: Try to construct InsertTablet from InsertRowsNode to speed up write operation Key: IOTDB-5363 URL: https://issues.apache.org/jira/browse/IOTDB-5363 Project:

[jira] [Commented] (IOTDB-5206) Fix when target file is deleted in Compaction exception handler and recover

[ https://issues.apache.org/jira/browse/IOTDB-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654819#comment-17654819 ] Jinrui Zhang commented on IOTDB-5206: - 执行时策略：

[jira] [Created] (IOTDB-5338) WAL buffer flush threshold optimaztion

Jinrui Zhang created IOTDB-5338: --- Summary: WAL buffer flush threshold optimaztion Key: IOTDB-5338 URL: https://issues.apache.org/jira/browse/IOTDB-5338 Project: Apache IoTDB Issue Type:

[jira] [Assigned] (IOTDB-5337) Parallelization of write operation in FragmentInstanceDispatcher

[ https://issues.apache.org/jira/browse/IOTDB-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5337: --- Sprint: 2023-1-Storage Assignee: Haiming Zhu Remaining

[jira] [Created] (IOTDB-5337) Parallelization of write operation in FragmentInstanceDispatcher

Jinrui Zhang created IOTDB-5337: --- Summary: Parallelization of write operation in FragmentInstanceDispatcher Key: IOTDB-5337 URL: https://issues.apache.org/jira/browse/IOTDB-5337 Project: Apache IoTDB

[jira] [Created] (IOTDB-5336) Investigation regarding write interface used by TSBS in IoTDB

Jinrui Zhang created IOTDB-5336: --- Summary: Investigation regarding write interface used by TSBS in IoTDB Key: IOTDB-5336 URL: https://issues.apache.org/jira/browse/IOTDB-5336 Project: Apache IoTDB

[jira] [Created] (IOTDB-5335) InsertRecords performance optimization

Jinrui Zhang created IOTDB-5335: --- Summary: InsertRecords performance optimization Key: IOTDB-5335 URL: https://issues.apache.org/jira/browse/IOTDB-5335 Project: Apache IoTDB Issue Type:

[jira] [Assigned] (IOTDB-5273) [fast compaction]The performance is slow ，there are out-of-order tsfiles after compaction

[ https://issues.apache.org/jira/browse/IOTDB-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5273: --- Sprint: 2023-1-Storage (was: 2022-12-Storage) Assignee: Wenwei Shu (was: 周沛辰) >

[jira] [Assigned] (IOTDB-5156) The backup data is twice the size of the source data

[ https://issues.apache.org/jira/browse/IOTDB-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5156: --- Assignee: Liuxuxin > The backup data is twice the size of the source data >

[jira] [Assigned] (IOTDB-4665) "tsfile" (all data deleted) lack a periodic deletion policy

[ https://issues.apache.org/jira/browse/IOTDB-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4665: --- Assignee: Jinrui Zhang > "tsfile" (all data deleted) lack a periodic deletion policy >

[jira] [Assigned] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5319: --- Assignee: Liuxuxin (was: Jinrui Zhang) > The write speed in atoms testing declined after

[jira] [Assigned] (IOTDB-5289) [Metric]Only the leader confignode can show the number of datanode and confignode

[ https://issues.apache.org/jira/browse/IOTDB-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5289: --- Assignee: Hongyin Zhang (was: Gaofei Cao) > [Metric]Only the leader confignode can show

[jira] [Assigned] (IOTDB-5289) [Metric]Only the leader confignode can show the number of datanode and confignode

[ https://issues.apache.org/jira/browse/IOTDB-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5289: --- Assignee: Gaofei Cao (was: Hongyin Zhang) > [Metric]Only the leader confignode can show

[jira] [Commented] (IOTDB-4986) Too many IoTDB-DataNodeInternalRPC-Processor threads are open

[ https://issues.apache.org/jira/browse/IOTDB-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653755#comment-17653755 ] Jinrui Zhang commented on IOTDB-4986: - Let's confirmed with [~tanxinyu]  whether this issue is fixed

[jira] [Commented] (IOTDB-4164) [ wal_mode=SYNC ] Performance needs to be optimized

[ https://issues.apache.org/jira/browse/IOTDB-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653754#comment-17653754 ] Jinrui Zhang commented on IOTDB-4164: - The priority of this feature is not high. Let's move it to

[jira] [Commented] (IOTDB-5275) [compaction][aligned ts] compaction is slow

[ https://issues.apache.org/jira/browse/IOTDB-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653735#comment-17653735 ] Jinrui Zhang commented on IOTDB-5275: - What's the problem > [compaction][aligned ts] compaction is

[jira] [Commented] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653053#comment-17653053 ] Jinrui Zhang commented on IOTDB-5319: - We have found the commit which leader to the decline.  The

[jira] [Assigned] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5319: --- Assignee: Jinrui Zhang > The write speed in atoms testing declined after merging commit

[jira] [Assigned] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5319: --- Assignee: (was: Jinrui Zhang) > The write speed in atoms testing declined after merging

[jira] [Commented] (IOTDB-5279) [Metric] Got a wrong number after restart the cluster

[ https://issues.apache.org/jira/browse/IOTDB-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653047#comment-17653047 ] Jinrui Zhang commented on IOTDB-5279: - Let's paste the PR if it is completed > [Metric] Got a wrong

[jira] [Assigned] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

[ https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5319: --- Assignee: Jinrui Zhang > The write speed in atoms testing declined after merging commit

[jira] [Created] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

Jinrui Zhang created IOTDB-5319: --- Summary: The write speed in atoms testing declined after merging commit 5126711d Key: IOTDB-5319 URL: https://issues.apache.org/jira/browse/IOTDB-5319 Project: Apache

[jira] [Commented] (IOTDB-4684) Devices with the same name but different alignment properties are compacted into the wrong alignment property

[ https://issues.apache.org/jira/browse/IOTDB-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652719#comment-17652719 ] Jinrui Zhang commented on IOTDB-4684: - The schema process in compaction task execution stage is not

[jira] [Commented] (IOTDB-5147) Optimize compaction schedule when priority is BALANCE

[ https://issues.apache.org/jira/browse/IOTDB-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652718#comment-17652718 ] Jinrui Zhang commented on IOTDB-5147: - Still in talk stage,  won't complete in 1.0.1 > Optimize

[jira] [Commented] (IOTDB-5189) Optimize the memory usage of fast compaction

[ https://issues.apache.org/jira/browse/IOTDB-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652717#comment-17652717 ] Jinrui Zhang commented on IOTDB-5189: - Still in progress. Won't merged into 1.0.1 > Optimize the

[jira] [Commented] (IOTDB-4986) Too many IoTDB-DataNodeInternalRPC-Processor threads are open

[ https://issues.apache.org/jira/browse/IOTDB-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652409#comment-17652409 ] Jinrui Zhang commented on IOTDB-4986: - This issue is related to the ClientManager used in IoTDB

[jira] [Created] (IOTDB-5285) TimePartition may be error when restarting with different time partition configuration

Jinrui Zhang created IOTDB-5285: --- Summary: TimePartition may be error when restarting with different time partition configuration Key: IOTDB-5285 URL: https://issues.apache.org/jira/browse/IOTDB-5285

[jira] [Created] (IOTDB-5266) Seq file may be lost when selecting cross compaction task

Jinrui Zhang created IOTDB-5266: --- Summary: Seq file may be lost when selecting cross compaction task Key: IOTDB-5266 URL: https://issues.apache.org/jira/browse/IOTDB-5266 Project: Apache IoTDB

[jira] [Commented] (IOTDB-5263) Optimize the cross compaction file selection and execution

[ https://issues.apache.org/jira/browse/IOTDB-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17650798#comment-17650798 ] Jinrui Zhang commented on IOTDB-5263: - We will do this optimization after bug fix in current

[jira] [Created] (IOTDB-5263) Optimize the cross compaction file selection and execution

Jinrui Zhang created IOTDB-5263: --- Summary: Optimize the cross compaction file selection and execution Key: IOTDB-5263 URL: https://issues.apache.org/jira/browse/IOTDB-5263 Project: Apache IoTDB

[jira] [Assigned] (IOTDB-4674) Reimplement settle by compaction

[ https://issues.apache.org/jira/browse/IOTDB-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4674: --- Assignee: Wenwei Shu (was: 周沛辰) > Reimplement settle by compaction >

[jira] [Assigned] (IOTDB-4986) Too many IoTDB-DataNodeInternalRPC-Processor threads are open

[ https://issues.apache.org/jira/browse/IOTDB-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4986: --- Assignee: Haiming Zhu (was: Jinrui Zhang) > Too many IoTDB-DataNodeInternalRPC-Processor

[jira] [Commented] (IOTDB-5035) After the datanode is removed successfully, the snapshot can be deleted

[ https://issues.apache.org/jira/browse/IOTDB-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645745#comment-17645745 ] Jinrui Zhang commented on IOTDB-5035: - https://github.com/apache/iotdb/pull/8383 > After the

[jira] [Commented] (IOTDB-5165) [ compaction ]

[ https://issues.apache.org/jira/browse/IOTDB-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645744#comment-17645744 ] Jinrui Zhang commented on IOTDB-5165: - Need to take a look in priority > [ compaction ] >

[jira] [Commented] (IOTDB-5139) [benchmark]1device over 3w sensors, insert nothing

[ https://issues.apache.org/jira/browse/IOTDB-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645743#comment-17645743 ] Jinrui Zhang commented on IOTDB-5139: - It seems that this issue is easy to repro. Let's repro it and

[jira] [Commented] (IOTDB-4400) [new stand-alone]enableMetric, the write performance does not meet expectations

[ https://issues.apache.org/jira/browse/IOTDB-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645740#comment-17645740 ] Jinrui Zhang commented on IOTDB-4400: - Need to do the test again with latest code  > [new

[jira] [Assigned] (IOTDB-5030) [Schema-Read-Performance] java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5030: --- Sprint: 2022-12-Schema (was: 2022-11-Cluster) Assignee: Yukun Zhou (was: Jinrui

[jira] [Commented] (IOTDB-4971) dispatch write failed. status: TSStatus(code:506, subStatus:[]), message: null

[ https://issues.apache.org/jira/browse/IOTDB-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645737#comment-17645737 ] Jinrui Zhang commented on IOTDB-4971: - Need to confirm what the problem is behind the logs >

[jira] [Commented] (IOTDB-4805) [Performance] Compare performance of 1C1D with "start-server.sh” and ”start-new-server.sh”

[ https://issues.apache.org/jira/browse/IOTDB-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645736#comment-17645736 ] Jinrui Zhang commented on IOTDB-4805: - This issue intended to compare the performance between 1c1d

[jira] [Created] (IOTDB-5103) LastFlushTime may be set incorrectly when DataRegion recovering

Jinrui Zhang created IOTDB-5103: --- Summary: LastFlushTime may be set incorrectly when DataRegion recovering Key: IOTDB-5103 URL: https://issues.apache.org/jira/browse/IOTDB-5103 Project: Apache IoTDB

[jira] [Assigned] (IOTDB-5035) After the datanode is removed successfully, the snapshot can be deleted

[ https://issues.apache.org/jira/browse/IOTDB-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5035: --- Assignee: Haiming Zhu (was: Jinrui Zhang) > After the datanode is removed successfully,

[jira] [Commented] (IOTDB-5045) [delete] After running "drop database root.**", wal and tsfile still left

[ https://issues.apache.org/jira/browse/IOTDB-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639889#comment-17639889 ] Jinrui Zhang commented on IOTDB-5045: - According to current investigation with [~Marcoss] , we found

[jira] [Assigned] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5030: --- Assignee: Jinrui Zhang (was: Yukun Zhou) > java.lang.IllegalArgumentException: all

[jira] [Assigned] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-5030: --- Assignee: Yukun Zhou (was: Jinrui Zhang) > java.lang.IllegalArgumentException: all

[jira] [Commented] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638667#comment-17638667 ] Jinrui Zhang commented on IOTDB-5030: - [~HeimingZ] tried to reproduce this issue in fit16-20 with

[jira] [Commented] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638525#comment-17638525 ] Jinrui Zhang commented on IOTDB-5030: - Please try to reproduce this issue with latest code >

[jira] [Commented] (IOTDB-4507) [SystemResourceIssue] Insert failed can't connect to node TEndPoint

[ https://issues.apache.org/jira/browse/IOTDB-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638467#comment-17638467 ] Jinrui Zhang commented on IOTDB-4507: - We gave more optimization and bug fix to MultiLeaderCosnensus,

[jira] [Created] (IOTDB-5036) Take snapshot in parallel when IoTDB shutdown

Jinrui Zhang created IOTDB-5036: --- Summary: Take snapshot in parallel when IoTDB shutdown Key: IOTDB-5036 URL: https://issues.apache.org/jira/browse/IOTDB-5036 Project: Apache IoTDB Issue Type:

[jira] [Commented] (IOTDB-4971) dispatch write failed. status: TSStatus(code:506, subStatus:[]), message: null

[ https://issues.apache.org/jira/browse/IOTDB-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638102#comment-17638102 ] Jinrui Zhang commented on IOTDB-4971: - 可以考虑打印明确的code 内容 > dispatch write failed. status:

[jira] [Commented] (IOTDB-4986) Too many IoTDB-DataNodeInternalRPC-Processor threads are open

[ https://issues.apache.org/jira/browse/IOTDB-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638099#comment-17638099 ] Jinrui Zhang commented on IOTDB-4986: - It is not a functionality issue. Let's mark it as a

[jira] [Commented] (IOTDB-5015) [write]when writing for about 6 hours to only 1 sensor, the writing stopped with error: too many requests need to process

[ https://issues.apache.org/jira/browse/IOTDB-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638098#comment-17638098 ] Jinrui Zhang commented on IOTDB-5015: - This issue may caused by the same reason in this issue

[jira] [Commented] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638092#comment-17638092 ] Jinrui Zhang commented on IOTDB-5030: - We need to confirm whether the cluster is ok or not >

[jira] [Commented] (IOTDB-5030) java.lang.IllegalArgumentException: all replicas for region[TConsensusGroupId(type:SchemaRegion, id:6)] are not available in these DataNodes

[ https://issues.apache.org/jira/browse/IOTDB-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638091#comment-17638091 ] Jinrui Zhang commented on IOTDB-5030: - The issue is caused by the schemaFetching failure during

[jira] [Commented] (IOTDB-4972) [DispatchFailed] NPE at org.apache.iotdb.db.mpp.plan.planner.plan.node.write.InsertNode.selfCheckDataTypes(InsertNode.java:251)

[ https://issues.apache.org/jira/browse/IOTDB-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637554#comment-17637554 ] Jinrui Zhang commented on IOTDB-4972: - SENSOR_NUM is 10, which is too large.  Let's investigate

[jira] [Commented] (IOTDB-4400) [new stand-alone]enableMetric, the write performance does not meet expectations

[ https://issues.apache.org/jira/browse/IOTDB-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635622#comment-17635622 ] Jinrui Zhang commented on IOTDB-4400: - Let's test this issue again with the latest MultiLeader code

[jira] [Commented] (IOTDB-4505) [SystemResourceIssue] Why is the 60 client test better than the 300 client test

[ https://issues.apache.org/jira/browse/IOTDB-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635620#comment-17635620 ] Jinrui Zhang commented on IOTDB-4505: - It should be related to the memory usage. That is, 300 clients

[jira] [Commented] (IOTDB-4506) [cluster]The data amount of the three nodes is quite different

[ https://issues.apache.org/jira/browse/IOTDB-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635617#comment-17635617 ] Jinrui Zhang commented on IOTDB-4506: - We gave more optimization on MultiLeader module, let's keep

[jira] [Commented] (IOTDB-4825) [ multiLeader ] ERROR o.a.i.d.m.p.s.FixedRateFragInsStateTracker:114 - error happened while fetching query state

[ https://issues.apache.org/jira/browse/IOTDB-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635614#comment-17635614 ] Jinrui Zhang commented on IOTDB-4825: - According to the log and write operation result, this issue

[jira] [Created] (IOTDB-4969) Distribution plan is not correct for Aggregation query with AlignByDevice

Jinrui Zhang created IOTDB-4969: --- Summary: Distribution plan is not correct for Aggregation query with AlignByDevice Key: IOTDB-4969 URL: https://issues.apache.org/jira/browse/IOTDB-4969 Project:

[jira] [Commented] (IOTDB-4873) Multi-user concurrent write and query + [ select into ] : ERROR o.a.i.c.m.t.MultiLeaderConsensusIService$AsyncProcessor$syncLog$1:903 - Exception inside handler

[ https://issues.apache.org/jira/browse/IOTDB-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17633427#comment-17633427 ] Jinrui Zhang commented on IOTDB-4873: - It seems that some requests are fetched both from Queue and

[jira] [Assigned] (IOTDB-4873) Multi-user concurrent write and query + [ select into ] : ERROR o.a.i.c.m.t.MultiLeaderConsensusIService$AsyncProcessor$syncLog$1:903 - Exception inside handler

[ https://issues.apache.org/jira/browse/IOTDB-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4873: --- Assignee: Haiming Zhu (was: Jinrui Zhang) Please track this issue according to our

[jira] [Commented] (IOTDB-4556) [Remove-DataNode] ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:287 - The consensus group DataRegion[24] doesn't exist

[ https://issues.apache.org/jira/browse/IOTDB-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632232#comment-17632232 ] Jinrui Zhang commented on IOTDB-4556: - Talked with [~HeimingZ] for this issue, we found the behavior

[jira] [Assigned] (IOTDB-4556) [Remove-DataNode] ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:287 - The consensus group DataRegion[24] doesn't exist

[ https://issues.apache.org/jira/browse/IOTDB-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4556: --- Assignee: Haiming Zhu (was: Jinrui Zhang) > [Remove-DataNode] ERROR

[jira] [Assigned] (IOTDB-4752) some data is lost after the read-only node returns to normal

[ https://issues.apache.org/jira/browse/IOTDB-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4752: --- Assignee: Yongzao Dan (was: Haiming Zhu) > some data is lost after the read-only node

[jira] [Created] (IOTDB-4874) NPE error when migrating MultiLeader Peer with 1 replica

Jinrui Zhang created IOTDB-4874: --- Summary: NPE error when migrating MultiLeader Peer with 1 replica Key: IOTDB-4874 URL: https://issues.apache.org/jira/browse/IOTDB-4874 Project: Apache IoTDB

[jira] [Assigned] (IOTDB-4731) [Remove-DataNode] Data is inconsistent （ remove datanode before the synchronization is complete ）

[ https://issues.apache.org/jira/browse/IOTDB-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4731: --- Assignee: Haiming Zhu (was: Jinrui Zhang) > [Remove-DataNode] Data is inconsistent （

[jira] [Assigned] (IOTDB-4752) some data is lost after the read-only node returns to normal

[ https://issues.apache.org/jira/browse/IOTDB-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinrui Zhang reassigned IOTDB-4752: --- Assignee: Haiming Zhu (was: 张洪胤) > some data is lost after the read-only node returns to

  1   2   3   >