[jira] [Created] (IOTDB-5573) loadTsFile occurs OOM when the time partition span is very large and contains too many files
李伟豪 created IOTDB-5573: -- Summary: loadTsFile occurs OOM when the time partition span is very large and contains too many files Key: IOTDB-5573 URL: https://issues.apache.org/jira/browse/IOTDB-5573 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Reporter: 李伟豪 Attachments: image-2023-02-23-15-01-38-425.png, image-2023-02-23-15-01-40-436.png, image-2023-02-23-15-02-16-188.png, image-2023-02-23-15-10-32-138.png support message: https://timechor.feishu.cn/docx/MeQjd50ABoEZm8xNwmHccjGdnLb !image-2023-02-23-15-02-16-188.png! !image-2023-02-23-15-10-32-138.png! !image-2023-02-23-15-01-40-436.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5512) Fixed IoTConsensus may repeatedly send some log when restarting
[ https://issues.apache.org/jira/browse/IOTDB-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692468#comment-17692468 ] 刘珍 commented on IOTDB-5512: --- master_2023-02-22_16c1c9e ,dn_metric_internal_reporter_type=MEMORY 集群重启前后，无乱序tsfile，全部成功。 如果不设置dn_metric_internal_reporter_type=MEMORY，默认会采集写入point，集群不重启，也有部分乱序tsfile，还有system reject。 > Fixed IoTConsensus may repeatedly send some log when restarting > --- > > Key: IOTDB-5512 > URL: https://issues.apache.org/jira/browse/IOTDB-5512 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: huxiangpeng >Priority: Major > Labels: pull-request-available > Attachments: image-2023-02-09-15-45-05-253.png, > image-2023-02-09-15-52-51-085.png, insert_no_overflow.config.properties > > > 测试版本：rc/1.0.1 20230202 63b16f2 > 问题描述： > 3副本3节点集群，benchmark写入顺序数据，重启前检查data 为全顺序，重启集群后，会生成部分乱序tsfile。 > 重启集群前查看所有dataregion的log同步情况，已同步完成： > !image-2023-02-09-15-45-05-253.png! > consensus 文件记录的已同步的log index是10 > !image-2023-02-09-15-52-51-085.png! > 重启集群后，这90条log会重发，导致有乱序tsfile生成，可以优化一下，解决这个问题。 > 测试流程： > 1. 私有云3期 > 1ConfigNode 172.20.70.5 > 3DataNode 172.20.70.2/4/14 > benchmark 在172.20.70.13 （配置见附件） > 集群配置参数 > ConfigNode > MAX_HEAP_SIZE="20G" > MAX_DIRECT_MEMORY_SIZE="6G" > DataNode > MAX_HEAP_SIZE="20G" > MAX_DIRECT_MEMORY_SIZE="6G" > dn_max_connection_for_internal_service=300 > common文件 > schema_replication_factor=3 > data_replication_factor=3 > enable_seq_space_compaction=false > enable_unseq_space_compaction=false > enable_cross_space_compaction=false > config_node_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus > schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus > data_region_consensus_protocol_class=org.apache.iotdb.consensus.iot.IoTConsensus > 2. 运行benchmark > 3. 写入完成，检查data ，无乱序tsfile，log同步完成，重启集群。 > 预期结果，重启后，无乱序tsfile。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5572) Typo in GroupBy-UserGuide
yang caiyin created IOTDB-5572: -- Summary: Typo in GroupBy-UserGuide Key: IOTDB-5572 URL: https://issues.apache.org/jira/browse/IOTDB-5572 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin https://iotdb.apache.org/zh/UserGuide/Master/Query-Data/Group-By.html#%E6%97%B6%E9%97%B4%E5%8C%BA%E9%97%B4%E5%88%86%E6%AE%B5%E8%81%9A%E5%90%88 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5473) [Atmos]The throughput went down since 2fc195c[02/02]
[ https://issues.apache.org/jira/browse/IOTDB-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17692423#comment-17692423 ] Qingxin Feng commented on IOTDB-5473: - 虽然是在优化RRECORDS写入性能，但是对于某些场景（下图测试场景）是负增益的。请关注。 !image-2023-02-23-08-23-04-417.png|width=1300,height=433! > [Atmos]The throughput went down since 2fc195c[02/02] > > > Key: IOTDB-5473 > URL: https://issues.apache.org/jira/browse/IOTDB-5473 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Qingxin Feng >Assignee: Jinrui Zhang >Priority: Minor > Attachments: image-2023-02-06-10-17-01-663.png, > image-2023-02-23-08-23-04-417.png > > > [Atmos]The throughput went down since 2fc195c[02/02] > Please refer to below picture. > !image-2023-02-06-10-17-01-663.png|width=974,height=324! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5571) [trigger]trigger does not work properly when run with other testcases
changxue created IOTDB-5571:
---
Summary: [trigger]trigger does not work properly when run with
other testcases
Key: IOTDB-5571
URL: https://issues.apache.org/jira/browse/IOTDB-5571
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: changxue
Assignee: Yuan Tian
[trigger]trigger does not work properly when run with other testcases
env:
2023-2-21 master source codes
version 1.1.0-SNAPSHOT (Build: d6e015e-dev)
bug description:
data_types.run line 236
{code:java}
select count(*) from root.target.alerting; {code}
expect: 17
actual: 16
missing this value:
{code:java}
[1]this statement is too long to p|root.triggertest.nonaligned_dev1.s_5
{code}
reproduction:
1. start IoTDB with the config of attachment conf-ext-logs.tar.gz
2. run testcases of testcase-run.tar.gz (ask me about how to run)
3. check data_types.out
ps:
1. It's all right when running data_types.run alone, but it fails when running
with other test cases of testcase-run.tar.gz.
2. The Trigger Class using in tests are synchronized
3. It is not a trigger problem maybe but a problem related to cleanup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
