[jira] [Reopened] (IOTDB-1741) Compaction file stream clsoed Exception
[ https://issues.apache.org/jira/browse/IOTDB-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reopened IOTDB-1741: > Compaction file stream clsoed Exception > --- > > Key: IOTDB-1741 > URL: https://issues.apache.org/jira/browse/IOTDB-1741 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Liuxuxin >Assignee: Liuxuxin >Priority: Major > Labels: pull-request-available > Fix For: 0.12.3 > > Attachments: image-2021-09-26-15-30-39-569.png > > Original Estimate: 8h > Remaining Estimate: 8h > > !image-2021-09-26-15-30-39-569.png! > Compaction IOException in 0.12.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1868) Use RwLock to reduce the lock time for nodeRing
[ https://issues.apache.org/jira/browse/IOTDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DaweiLiu reassigned IOTDB-1868: --- Fix Version/s: 0.12.3 Assignee: DaweiLiu Resolution: Fixed > Use RwLock to reduce the lock time for nodeRing > --- > > Key: IOTDB-1868 > URL: https://issues.apache.org/jira/browse/IOTDB-1868 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Reporter: DaweiLiu >Assignee: DaweiLiu >Priority: Major > Labels: pull-request-available > Fix For: 0.12.3 > > > Synchronized is used in all operations of nodeRing in SlotPartitionTable > class. Normally, there is no write operation for nodeRing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1871) Perform machine resource-aware scheduling when writing or querying data
Houliang Qi created IOTDB-1871: -- Summary: Perform machine resource-aware scheduling when writing or querying data Key: IOTDB-1871 URL: https://issues.apache.org/jira/browse/IOTDB-1871 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Houliang Qi Now, when data is written, it is partitioned according to sg, and the number of sg on each node is evenly distributed, without considering the uneven node resources in a heterogeneous cluster. It is hoped that when doing data allocation and scheduling later, the situation of heterogeneous nodes can be considered, and resources can be uniformly managed. When data write scheduling is done, scheduling will be based on uniform resources. The same is true for queries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1870) Experiment of schema in TsFile
Jialin Qiao created IOTDB-1870: -- Summary: Experiment of schema in TsFile Key: IOTDB-1870 URL: https://issues.apache.org/jira/browse/IOTDB-1870 Project: Apache IoTDB Issue Type: Task Reporter: Jialin Qiao Assignee: Zesong Sun Test which schema perform better in different scenario: N device * 1 sensor Schema1: time, deviceId, value Schema2: time, d1.value, d2.value, ... Total 100,000,000 data points. Device number: 1,000,000, line: 100 Device number: 100,000, line: 1,000 Device number: 10,000, line: 10,000 Device number: 1,000, line: 100,000 Device number: 100, line: 1,000,000 Test the insertion speed, file size and query time(query all data of one device) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1817) support connect to multi node in go-client
[ https://issues.apache.org/jira/browse/IOTDB-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi reassigned IOTDB-1817: -- Assignee: jihang > support connect to multi node in go-client > -- > > Key: IOTDB-1817 > URL: https://issues.apache.org/jira/browse/IOTDB-1817 > Project: Apache IoTDB > Issue Type: New Feature > Components: Client/Others >Reporter: WangChao >Assignee: jihang >Priority: Major > Labels: features > > Now, java client could connect to multi nodes in iotdb cluster, we > couldmigrate the feature to go-client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1869) Auto create schema template
Jialin Qiao created IOTDB-1869: -- Summary: Auto create schema template Key: IOTDB-1869 URL: https://issues.apache.org/jira/browse/IOTDB-1869 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Users set which node is template node. We could auto create and extend the template when inserting. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1868) Use RwLock to reduce the lock time for nodeRing
DaweiLiu created IOTDB-1868: --- Summary: Use RwLock to reduce the lock time for nodeRing Key: IOTDB-1868 URL: https://issues.apache.org/jira/browse/IOTDB-1868 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: DaweiLiu Synchronized is used in all operations of nodeRing in SlotPartitionTable class. Normally, there is no write operation for nodeRing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1745) Metagroup snapshots support template
[ https://issues.apache.org/jira/browse/IOTDB-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyu Tan reassigned IOTDB-1745: Assignee: 张洪胤 (was: Xinyu Tan) > Metagroup snapshots support template > > > Key: IOTDB-1745 > URL: https://issues.apache.org/jira/browse/IOTDB-1745 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Reporter: Xinyu Tan >Assignee: 张洪胤 >Priority: Major > Original Estimate: 72h > Time Spent: 97h > Remaining Estimate: 32h > > Snapshots of the meta group in the current cluster module support storage > groups and TTL information, etc, but do not support templates. Templates need > to be supported so that newly added nodes can register templates during > cluster expansion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1867) [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x
[ https://issues.apache.org/jira/browse/IOTDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432160#comment-17432160 ] 张洪胤 commented on IOTDB-1867: I fix this bug in master > [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x > - > > Key: IOTDB-1867 > URL: https://issues.apache.org/jira/browse/IOTDB-1867 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Error happens when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x, benchmark > will only write and not query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1867) [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x
张洪胤 created IOTDB-1867: -- Summary: [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x Key: IOTDB-1867 URL: https://issues.apache.org/jira/browse/IOTDB-1867 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Error happens when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x, benchmark will only write and not query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1866) [Benchmark] Expanding read-write mixed scenarios
[ https://issues.apache.org/jira/browse/IOTDB-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432158#comment-17432158 ] 张洪胤 commented on IOTDB-1866: I support this feature in [https://github.com/thulab/iotdb-benchmark/pull/212.] Just use IS_RECENT_QUERY to open. > [Benchmark] Expanding read-write mixed scenarios > > > Key: IOTDB-1866 > URL: https://issues.apache.org/jira/browse/IOTDB-1866 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 3h > Remaining Estimate: 3h > > Because of the requirements, benchmark need to support query recent data in > read-write mixed scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1866) [Benchmark] Expanding read-write mixed scenarios
张洪胤 created IOTDB-1866: -- Summary: [Benchmark] Expanding read-write mixed scenarios Key: IOTDB-1866 URL: https://issues.apache.org/jira/browse/IOTDB-1866 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Because of the requirements, benchmark need to support query recent data in read-write mixed scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1864) Record the output result selection in CSV, but it does not take effect after serverMODE is started.
[ https://issues.apache.org/jira/browse/IOTDB-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432157#comment-17432157 ] 张洪胤 commented on IOTDB-1864: I fix this problems in https://github.com/thulab/iotdb-benchmark/pull/210 > Record the output result selection in CSV, but it does not take effect after > serverMODE is started. > --- > > Key: IOTDB-1864 > URL: https://issues.apache.org/jira/browse/IOTDB-1864 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > In ServerMode of IoTDB-Benchmark, it fails to record the result in csv. > How to recur this problem: > Step 1: > Modify config.properties of Benchmark: > `TEST_DATA_PERSISTENCE=CSV` > Step 2: > Start ser-benchmark.sh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1865) 【cluster】Compaction doesn't work correctly
FengQingxin created IOTDB-1865: -- Summary: 【cluster】Compaction doesn't work correctly Key: IOTDB-1865 URL: https://issues.apache.org/jira/browse/IOTDB-1865 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 0.12.2 Reporter: FengQingxin Attachments: image-2021-10-20-21-43-47-115.png Hi IoTDBers: When I using iotdb-cluster[3 nodes，default_replica_num=1] ,I saw compaction doesn't work correctly. We can see both 1-0-0.tsfile and 1-1-0.tsfile,and there will be no compaction after this. !image-2021-10-20-21-43-47-115.png! Please check this. Thanks. B.R. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1864) Record the output result selection in CSV, but it does not take effect after serverMODE is started.
[ https://issues.apache.org/jira/browse/IOTDB-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1864: -- Assignee: 张洪胤 > Record the output result selection in CSV, but it does not take effect after > serverMODE is started. > --- > > Key: IOTDB-1864 > URL: https://issues.apache.org/jira/browse/IOTDB-1864 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > In ServerMode of IoTDB-Benchmark, it fails to record the result in csv. > How to recur this problem: > Step 1: > Modify config.properties of Benchmark: > `TEST_DATA_PERSISTENCE=CSV` > Step 2: > Start ser-benchmark.sh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1864) Record the output result selection in CSV, it does not take effect after serverMODE is started.
xiaozhihong created IOTDB-1864: -- Summary: Record the output result selection in CSV, it does not take effect after serverMODE is started. Key: IOTDB-1864 URL: https://issues.apache.org/jira/browse/IOTDB-1864 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: xiaozhihong Step 1: Set config.properties about Benchmark TEST_DATA_PERSISTENCE=CSV Step 2: Start ser-benchmark.sh -- This message was sent by Atlassian Jira (v8.3.4#803005)
