[jira] [Created] (IOTDB-5725) Make internal report recording measurements asynchronous
Xinyu Tan created IOTDB-5725: Summary: Make internal report recording measurements asynchronous Key: IOTDB-5725 URL: https://issues.apache.org/jira/browse/IOTDB-5725 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan InternalReporter of the current metric module writes synchronously to the iotdb, which may cause a slow flush. In particular, when the system records flush points for the first time, the system needs to create related regions of root.__system, which takes a long time and may result in system reject errors. This issue adjusts the processes written to the iotdb to be asynchronous and ensures that all of the metric module's current operations will be memory operations only and will not involve time-consuming RPCS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5724) Implement parser
lichenyu created IOTDB-5724: --- Summary: Implement parser Key: IOTDB-5724 URL: https://issues.apache.org/jira/browse/IOTDB-5724 Project: Apache IoTDB Issue Type: Task Reporter: lichenyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5723) Pipe: Create Consensus Index
[ https://issues.apache.org/jira/browse/IOTDB-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yusicheng reassigned IOTDB-5723: Assignee: yusicheng > Pipe: Create Consensus Index > > > Key: IOTDB-5723 > URL: https://issues.apache.org/jira/browse/IOTDB-5723 > Project: Apache IoTDB > Issue Type: Task >Reporter: yusicheng >Assignee: yusicheng >Priority: Major > > create interface: > ConsensusIndex > ComparableConsensusRequest > they are used for pipe's fault tolerance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5723) Pipe: Create Consensus Index
yusicheng created IOTDB-5723: Summary: Pipe: Create Consensus Index Key: IOTDB-5723 URL: https://issues.apache.org/jira/browse/IOTDB-5723 Project: Apache IoTDB Issue Type: Task Reporter: yusicheng create interface: ConsensusIndex ComparableConsensusRequest they are used for pipe's fault tolerance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5722) Wrong default execution branch in PlanVisitor
Minghui Liu created IOTDB-5722: -- Summary: Wrong default execution branch in PlanVisitor Key: IOTDB-5722 URL: https://issues.apache.org/jira/browse/IOTDB-5722 Project: Apache IoTDB Issue Type: Bug Affects Versions: master branch, 1.1.0, 1.1.0-SNAPSHOT Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch, 1.1.0-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5721) Report too much timeslot when loading tsfile
yusicheng created IOTDB-5721: Summary: Report too much timeslot when loading tsfile Key: IOTDB-5721 URL: https://issues.apache.org/jira/browse/IOTDB-5721 Project: Apache IoTDB Issue Type: Bug Affects Versions: master branch Reporter: yusicheng Assignee: yusicheng Attachments: image-2023-03-23-20-58-49-257.png when the tsfiles to be loaded has smaller time precision, loading tsfile will create wrong timeslot because of wrong timePartitionInterval this will cause: !image-2023-03-23-20-58-49-257.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5718) Time order bug while using align by device
[ https://issues.apache.org/jira/browse/IOTDB-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704049#comment-17704049 ] 刘珍 commented on IOTDB-5718: --- master 0323 6ed0106 ,已解决。 !screenshot-1.png! > Time order bug while using align by device > -- > > Key: IOTDB-5718 > URL: https://issues.apache.org/jira/browse/IOTDB-5718 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query >Reporter: Yuan Tian >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > Attachments: image-2023-03-23-10-03-24-601.png, screenshot-1.png > > > 1C1D IoTDB > change the following two configuration in iotdb-common.properties > > data_region_group_extension_policy=CUSTOM > default_data_region_group_num_per_database=3 > > Then, execute the following sqls > > ``` > insert into root.db.d1(time,s1) values(2018-08-30T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-09-30T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-10-07T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-10-15T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-10-25T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-11-03T08:00:01.000+08:00, 10); > insert into root.db.d1(time,s1) values(2018-11-13T08:00:01.000+08:00, 10); > flush; > ``` > > After inserting the data, you can execute the align by device query and see > the wrong time ordering > > ``` > select s1 from root.db.d1 align by device; > ``` > while we don't add align by device, the result is right. > !image-2023-03-23-10-03-24-601.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5665) Drop Database while writing
[ https://issues.apache.org/jira/browse/IOTDB-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704001#comment-17704001 ] 刘珍 commented on IOTDB-5665: --- drop database root.** 会因为confignode重试而返回给客户端Msg: 508: Path [root.test.*] does not exist 这个问题需要解决，系统中是存在database的，返回这个报错信息不合适。 > Drop Database while writing > --- > > Key: IOTDB-5665 > URL: https://issues.apache.org/jira/browse/IOTDB-5665 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yongzao Dan >Assignee: Yongzao Dan >Priority: Major > Original Estimate: 8h > Remaining Estimate: 8h > > This is a special scenario. In this case, both the PartitionCache and > SchemaCache are too busy to be released, for which will eventually lead to a > failure of deleting Database. Thus, we should discuss the functional > definition of this scenario. > > For example, we can delete the database in force if the writeLock in > PartitionCache should at least use the fair lock or have a higher priority. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5720) Release processor fail to release memory due to writer-preferred starvation
[ https://issues.apache.org/jira/browse/IOTDB-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703949#comment-17703949 ] yanze chen commented on IOTDB-5720: --- https://github.com/apache/iotdb/pull/9422 > Release processor fail to release memory due to writer-preferred starvation > --- > > Key: IOTDB-5720 > URL: https://issues.apache.org/jira/browse/IOTDB-5720 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > Attachments: image-2023-03-23-15-26-27-207.png > > > !image-2023-03-23-15-26-27-207.png|width=488,height=155! > [https://apache-iotdb.feishu.cn/docx/WwdAd6SYLofsAHxEJeRcDuWBnPh] > > The current stampedLock uses a writer-preferred rule, which may lead to > extreme cases where a waiting write lock request blocks the subsequent > release thread from acquiring the read lock, resulting in memory not being > released. To solve this problem, a high priority read lock request interface > needs to be introduced. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5720) Release processor fail to release memory due to writer-preferred starvation
yanze chen created IOTDB-5720: - Summary: Release processor fail to release memory due to writer-preferred starvation Key: IOTDB-5720 URL: https://issues.apache.org/jira/browse/IOTDB-5720 Project: Apache IoTDB Issue Type: Bug Reporter: yanze chen Assignee: yanze chen Attachments: image-2023-03-23-15-26-27-207.png !image-2023-03-23-15-26-27-207.png|width=488,height=155! [https://apache-iotdb.feishu.cn/docx/WwdAd6SYLofsAHxEJeRcDuWBnPh] The current stampedLock uses a writer-preferred rule, which may lead to extreme cases where a waiting write lock request blocks the subsequent release thread from acquiring the read lock, resulting in memory not being released. To solve this problem, a high priority read lock request interface needs to be introduced. -- This message was sent by Atlassian Jira (v8.20.10#820010)
