[jira] [Commented] (IOTDB-5272) benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be 201 and no text TS
[ https://issues.apache.org/jira/browse/IOTDB-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653845#comment-17653845 ] Hongyin Zhang commented on IOTDB-5272: -- Fixed on https://github.com/thulab/iot-benchmark/pull/321 > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > - > > Key: IOTDB-5272 > URL: https://issues.apache.org/jira/browse/IOTDB-5272 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: changxue >Assignee: Hongyin Zhang >Priority: Major > Attachments: screenshot-1.png > > > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > iot-benchmark: 1.0.0, Dec. 9th source codes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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: 周沛辰) > [fast compaction]The performance is slow ，there are out-of-order tsfiles > after compaction > - > > Key: IOTDB-5273 > URL: https://issues.apache.org/jira/browse/IOTDB-5273 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: master branch >Reporter: 刘珍 >Assignee: Wenwei Shu >Priority: Major > Attachments: 1_luanxu.conf, 2_luanxu.conf, 3_luanxu.conf, > 4_luanxu.conf, image-2022-12-23-18-10-25-061.png > > Original Estimate: 96h > Remaining Estimate: 96h > > master 1222_656d281 > 问题描述： > 私有云1期，周测乱序配置，fast合并性能慢，且合并完成依然有乱序tsfile。 > !image-2022-12-23-18-10-25-061.png|width=979,height=481! > 测试环境 > 1. 私有云1期 > 关合并，生成数据。 > 配置文件见附件 > 2.对比合并性能，无其他读写操作。 > ConfigNode配置 > MAX_HEAP_SIZE="2G" > DataNode配置 > MAX_HEAP_SIZE="18G" > MAX_DIRECT_MEMORY_SIZE="6G" > Common配置 > time_partition_interval=6048000 > compaction_io_rate_per_sec=1000 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5111) [ ratis ] Data is distributed across disks ，after the cluster is restarted, all data is lost
[
https://issues.apache.org/jira/browse/IOTDB-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653841#comment-17653841
]
Houliang Qi commented on IOTDB-5111:
Hi, data loss is *BIG* issue in the product environment, so when does the issue
happen? if the user specifies multi dn_data_dirs which across many disks, will
this happen?
> [ ratis ] Data is distributed across disks ，after the cluster is restarted,
> all data is lost
>
>
> Key: IOTDB-5111
> URL: https://issues.apache.org/jira/browse/IOTDB-5111
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 1.0.0
>Reporter: 刘珍
>Assignee: Song Ziyang
>Priority: Major
> Attachments: image-2022-12-02-17-58-45-096.png,
> image-2022-12-02-17-59-05-010.png
>
>
> rel/1.0
> config/schema/data 3个协议均是ratis，
> dn_data_dirs=data/datanode/data,/data1/iotdb/datanode/data
> 跨盘存储，
> 写入数据，重启集群，{color:#DE350B}*数据全部丢失*{color}。
> 还有1个问题，{color:#DE350B}snapshot目录下依然有.tmp.文件夹名称{color}：
> !image-2022-12-02-17-59-05-010.png!
> 测试环境-私有云1期 8C32GB
> 1. 3副本3C7D
> Common
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> schema_replication_factor=3
> data_replication_factor=3
> wal_buffer_size_in_byte=1048576
> max_waiting_time_when_insert_blocked=360
> query_timeout_threshold=3600
> ConfigNode
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> DataNode
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> dn_data_dirs=data/datanode/data,/data1/iotdb/datanode/data
> 2. 启动BM 写入数据
> GROUP_NUMBER=1
> DEVICE_NUMBER=1000
> REAL_INSERT_RATE=1.0
> SENSOR_NUMBER=1000
> IS_SENSOR_TS_ALIGNMENT=true
> IS_OUT_OF_ORDER=false
> OUT_OF_ORDER_RATIO=0.5
> OPERATION_PROPORTION=1:0:0:0:0:0:0:0:0:0:0
> CLIENT_NUMBER=50
> LOOP=1
> BATCH_SIZE_PER_WRITE=10
> START_TIME=2018-8-30T00:00:00+08:00
> POINT_STEP=200
> OP_MIN_INTERVAL=0
> OP_MIN_INTERVAL_RANDOM=false
> INSERT_DATATYPE_PROPORTION=1:1:1:1:1:1
> ENCODINGS=PLAIN/PLAIN/PLAIN/PLAIN/PLAIN/PLAIN
> COMPRESSOR=SNAPPY
> IS_DELETE_DATA=false
> CREATE_SCHEMA=true
> BENCHMARK_CLUSTER=false
> !image-2022-12-02-17-58-45-096.png!
> 3. 重启集群
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5334) [Benchmark] Fix the aligned way to insert and Support ns precision
Hongyin Zhang created IOTDB-5334: Summary: [Benchmark] Fix the aligned way to insert and Support ns precision Key: IOTDB-5334 URL: https://issues.apache.org/jira/browse/IOTDB-5334 Project: Apache IoTDB Issue Type: Bug Reporter: Hongyin Zhang Assignee: Hongyin Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5272) benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be 201 and no text TS
[ https://issues.apache.org/jira/browse/IOTDB-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653820#comment-17653820 ] changxue commented on IOTDB-5272: - !screenshot-1.png! 配置：INSERT_DATATYPE_PROPORTION=0:0:0:0:999:1 text类型为2个，double类型为998个 > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > - > > Key: IOTDB-5272 > URL: https://issues.apache.org/jira/browse/IOTDB-5272 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: changxue >Assignee: Hongyin Zhang >Priority: Major > Attachments: screenshot-1.png > > > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > iot-benchmark: 1.0.0, Dec. 9th source codes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5272) benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be 201 and no text TS
[ https://issues.apache.org/jira/browse/IOTDB-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] changxue reopened IOTDB-5272: - > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > - > > Key: IOTDB-5272 > URL: https://issues.apache.org/jira/browse/IOTDB-5272 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: changxue >Assignee: Hongyin Zhang >Priority: Major > Attachments: screenshot-1.png > > > benchmark INSERT_DATATYPE_PROPORTION=3:200:200:396:200:1, double would be > 201 and no text TS > iot-benchmark: 1.0.0, Dec. 9th source codes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5231) [monitor]datanode could not start when binding 9091 error
[
https://issues.apache.org/jira/browse/IOTDB-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653801#comment-17653801
]
changxue commented on IOTDB-5231:
-
The log level should be warning, rather than error.
> [monitor]datanode could not start when binding 9091 error
> --
>
> Key: IOTDB-5231
> URL: https://issues.apache.org/jira/browse/IOTDB-5231
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: changxue
>Assignee: Hongyin Zhang
>Priority: Major
> Labels: pull-request-available
> Attachments: config.tar.gz, monitor_error_log.tar.gz
>
>
> [monitor]datanode could not start when binding 9091 error
> environment:
> 3C3D cluster, rel/1.0 branch
> 1. enable prometheus monitor
> 2. the prometheus service has not been started
> problem:
> 1. 监控是附加功能，打开它并且它工作不正常（可以warning），但不应该出现error，不应该影响rpc service等的启动。
> 2. 这种情况下，stop-datanode.sh 是不能成功停止成功的，需要kill
> 3. confignode启动成功，且成功绑定了9091, datanode再绑定9091，结果失败。需要使之成功。
> {code}
> 2022-12-19 10:26:23,574 [main] INFO o.a.i.m.AbstractMetricService:130 -
> Detect more than one MetricManager, will use
> org.apache.iotdb.metrics.micrometer.MicrometerMetricManager
> 2022-12-19 10:26:23,574 [main] INFO o.a.i.m.AbstractMetricService:137 - Load
> metric reporters, type: [PROMETHEUS]
> 2022-12-19 10:26:23,939 [main] ERROR o.a.i.c.s.m.MetricService:52 - Failed to
> start Metrics ServerService because:
> reactor.netty.ChannelBindException: Failed to bind on [0.0.0.0:9091]
> Suppressed: java.lang.Exception: #block terminated with an error
> at
> reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:139)
> at reactor.core.publisher.Mono.block(Mono.java:1731)
> at
> reactor.netty.transport.ServerTransport.bindNow(ServerTransport.java:145)
> at
> reactor.netty.transport.ServerTransport.bindNow(ServerTransport.java:130)
> at
> org.apache.iotdb.metrics.reporter.prometheus.PrometheusReporter.start(PrometheusReporter.java:81)
> at
> org.apache.iotdb.metrics.CompositeReporter.startAll(CompositeReporter.java:38)
> at
> org.apache.iotdb.metrics.AbstractMetricService.startAllReporter(AbstractMetricService.java:193)
> at
> org.apache.iotdb.metrics.AbstractMetricService.startCoreModule(AbstractMetricService.java:98)
> at
> org.apache.iotdb.metrics.AbstractMetricService.startService(AbstractMetricService.java:76)
> at
> org.apache.iotdb.commons.service.metric.MetricService.start(MetricService.java:49)
> at
> org.apache.iotdb.commons.service.RegisterManager.register(RegisterManager.java:51)
> at
> org.apache.iotdb.db.service.DataNode.doAddNode(DataNode.java:162)
> at
> org.apache.iotdb.db.service.DataNodeServerCommandLine.run(DataNodeServerCommandLine.java:95)
> at
> org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
> at
> org.apache.iotdb.db.service.DataNode.main(DataNode.java:131)
> 2022-12-19 10:26:23,940 [main] ERROR o.a.i.db.service.DataNode:178 - Fail to
> start server
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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=17653767#comment-17653767
]
Xinyu Tan commented on IOTDB-4986:
--
Not yet. This issue requires continuous optimization of the Thrift Threading
model over time, and I've broken it down a few issues that might take a sprint
or two to complete
> Too many IoTDB-DataNodeInternalRPC-Processor threads are open
> -
>
> Key: IOTDB-4986
> URL: https://issues.apache.org/jira/browse/IOTDB-4986
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Haiming Zhu
>Priority: Critical
>
> m_1118_3d5eeae
> 1. 启动3副本3C21D 集群
> 2. 顺序启动7Benchmark
> 3. 某个节点的datanode IoTDB-DataNodeInternalRPC-Processor 线程会开的很多，2k+
> （慢慢会降下来），但是会偶现OOM
> 2022-11-18 14:26:48,320
> [pool-22-IoTDB-DataNodeInternalRPC-Processor-374$20221118_062422_29227_16.1.0]
> ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:234 - write locally
> failed. TSStatus: TSStatus(code:506, subStatus:[]), message: null
> 2022-11-18 14:29:44,568 [DataNodeInternalRPC-Service]{color:red}* ERROR
> o.a.i.c.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
> DataNodeInternalRPC-Service-40
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached*{color}
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> org.apache.thrift.server.TThreadPoolServer.execute(TThreadPoolServer.java:155)
> at
> org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:139)
> at
> org.apache.iotdb.commons.service.AbstractThriftServiceThread.run(AbstractThriftServiceThread.java:258)
> 2022-11-18 14:29:53,751 [ClientRPC-Service] ERROR
> o.a.i.c.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
> ClientRPC-Service-42
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> org.apache.thrift.server.TThreadPoolServer.execute(TThreadPoolServer.java:155)
> at
> org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:139)
> at
> org.apache.iotdb.commons.service.AbstractThriftServiceThread.run(AbstractThriftServiceThread.java:258)
> 2022-11-18 14:30:11,736 [pool-6-IoTDB-Flush-4] ERROR
> o.a.i.d.e.s.TsFileProcessor:1095 - root.test.g_0-6:
> /data/iotdb/m_1118_3d5eeae/sbin/../data/datanode/data/unsequence/root.test.g_0/6/2538/1668752675355-5-0-0.tsfile
> meet error when flushing a memtable, change system mode to error
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
> at
> org.apache.iotdb.db.rescon.AbstractPoolManager.submit(AbstractPoolManager.java:56)
> at
> org.apache.iotdb.db.engine.flush.MemTableFlushTask.(MemTableFlushTask.java:88)
> at
> org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.flushOneMemTable(TsFileProcessor.java:1082)
> at
> org.apache.iotdb.db.engine.flush.FlushManager$FlushThread.runMayThrow(FlushManager.java:108)
> at
> org.apache.iotdb.commons.concurrent.WrappedRunnable.run(WrappedRunnable.java:29)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 2022-11-18
[jira] [Reopened] (IOTDB-5060) Control the ratis log size
[ https://issues.apache.org/jira/browse/IOTDB-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyu Tan reopened IOTDB-5060: -- > Control the ratis log size > -- > > Key: IOTDB-5060 > URL: https://issues.apache.org/jira/browse/IOTDB-5060 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Assignee: Song Ziyang >Priority: Major > > Currently, we have the operation number limit, but when meet big operation, > the log will occupy too much disk. > Need control the total raft log sie. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 > > > Key: IOTDB-5156 > URL: https://issues.apache.org/jira/browse/IOTDB-5156 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: Liuxuxin >Priority: Major > Attachments: image-2022-12-08-21-08-54-494.png > > > master > 问题描述： > 备份iotdb的data，大小是源data 的2倍。 > cp -rp m_1207_a0b2c8c_fast2/data m_1208_7f2218b_fast2/ > 备份出来的数据大小是源data的2倍： > 源snapshot 中的文件是硬链接，备份snapshot的文件会是普通文件： > !image-2022-12-08-21-08-54-494.png! > 测试流程 > 1.启动1副本1C1D（sbin/start-standalone.sh） > config , schema ,data 是ratis ，ratis ，IoT 协议 > 2. 写入数据 > 3. 正常停止datanode（会take snapshot） > 4. 备份数据 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 > > > Key: IOTDB-4665 > URL: https://issues.apache.org/jira/browse/IOTDB-4665 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: Jinrui Zhang >Priority: Major > Attachments: image-2022-10-17-14-37-00-495.png, > image-2022-10-17-14-38-08-095.png > > > 已执行delete timeseries root.** > 全部数据和元数据已删除。 > 但是tsfile没有定期清理（删除）策略。 > !image-2022-10-17-14-37-00-495.png! > !image-2022-10-17-14-38-08-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5333) max_tsblock_line_number is bad spelled in iotdb-common.properties
Eric Pai created IOTDB-5333: --- Summary: max_tsblock_line_number is bad spelled in iotdb-common.properties Key: IOTDB-5333 URL: https://issues.apache.org/jira/browse/IOTDB-5333 Project: Apache IoTDB Issue Type: Bug Affects Versions: master branch, 1.0.0 Reporter: Eric Pai Assignee: Eric Pai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 merging commit 5126711d > --- > > Key: IOTDB-5319 > URL: https://issues.apache.org/jira/browse/IOTDB-5319 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jinrui Zhang >Assignee: Liuxuxin >Priority: Major > Attachments: image-2022-12-29-18-37-25-693.png, > image-2022-12-29-18-38-45-394.png > > > !image-2022-12-29-18-37-25-693.png|width=701,height=156! > > After merging this commit, the write speed in atoms testing declined. > > We inferred that this change lead to compaction grabs more CPU/IO resources, > which decrease available resources of write/read. > > After we change the parameter `iops_per_min` from 50 to 30, the scenario > still exists. > See this snapshot, > !image-2022-12-29-18-38-45-394.png|width=541,height=346! > > Let's investigate the details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5332) [Compaction] Got a stuck when running a longrun test
Qingxin Feng created IOTDB-5332: --- Summary: [Compaction] Got a stuck when running a longrun test Key: IOTDB-5332 URL: https://issues.apache.org/jira/browse/IOTDB-5332 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 1.0.0 Reporter: Qingxin Feng Assignee: Liuxuxin Attachments: image-2023-01-03-11-43-23-519.png, image-2023-01-03-11-45-02-813.png version 1.0.1-SNAPSHOT (Build: f73b73f) We found the number of files grew rapidly, and the task number of inner and cross are reach the peak 1024. !image-2023-01-03-11-43-23-519.png! !image-2023-01-03-11-45-02-813.png! 分布式长测环境 27号更新master代码启动后运行到29凌晨发现文件数突然增长速度加快（多的文件是乱序文件，同时看到inner合并任务堆积） -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17653758#comment-17653758 ] Hongyin Zhang commented on IOTDB-5289: -- This problem mainly because only leader has the related information locally. If we want to get these informations in follower, we need to get through query which is costly. So, I think maybe we just need to modify grafana dashboard. > [Metric]Only the leader confignode can show the number of datanode and > confignode > - > > Key: IOTDB-5289 > URL: https://issues.apache.org/jira/browse/IOTDB-5289 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Hongyin Zhang >Priority: Minor > Attachments: image-2022-12-27-10-14-27-396.png, > image-2022-12-27-10-14-39-563.png > > > Only the leader confignode can show the number of datanode and confignode. > Please refer to below pictures: > Can we change it to "can be show on both leader and follower"? > !image-2022-12-27-10-14-39-563.png|width=638,height=388! > !image-2022-12-27-10-14-27-396.png|width=637,height=335! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 the number of datanode and > confignode > - > > Key: IOTDB-5289 > URL: https://issues.apache.org/jira/browse/IOTDB-5289 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Hongyin Zhang >Priority: Minor > Attachments: image-2022-12-27-10-14-27-396.png, > image-2022-12-27-10-14-39-563.png > > > Only the leader confignode can show the number of datanode and confignode. > Please refer to below pictures: > Can we change it to "can be show on both leader and follower"? > !image-2022-12-27-10-14-39-563.png|width=638,height=388! > !image-2022-12-27-10-14-27-396.png|width=637,height=335! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 the number of datanode and > confignode > - > > Key: IOTDB-5289 > URL: https://issues.apache.org/jira/browse/IOTDB-5289 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Gaofei Cao >Priority: Minor > Attachments: image-2022-12-27-10-14-27-396.png, > image-2022-12-27-10-14-39-563.png > > > Only the leader confignode can show the number of datanode and confignode. > Please refer to below pictures: > Can we change it to "can be show on both leader and follower"? > !image-2022-12-27-10-14-39-563.png|width=638,height=388! > !image-2022-12-27-10-14-27-396.png|width=637,height=335! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 or not
> Too many IoTDB-DataNodeInternalRPC-Processor threads are open
> -
>
> Key: IOTDB-4986
> URL: https://issues.apache.org/jira/browse/IOTDB-4986
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Haiming Zhu
>Priority: Critical
>
> m_1118_3d5eeae
> 1. 启动3副本3C21D 集群
> 2. 顺序启动7Benchmark
> 3. 某个节点的datanode IoTDB-DataNodeInternalRPC-Processor 线程会开的很多，2k+
> （慢慢会降下来），但是会偶现OOM
> 2022-11-18 14:26:48,320
> [pool-22-IoTDB-DataNodeInternalRPC-Processor-374$20221118_062422_29227_16.1.0]
> ERROR o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:234 - write locally
> failed. TSStatus: TSStatus(code:506, subStatus:[]), message: null
> 2022-11-18 14:29:44,568 [DataNodeInternalRPC-Service]{color:red}* ERROR
> o.a.i.c.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
> DataNodeInternalRPC-Service-40
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached*{color}
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> org.apache.thrift.server.TThreadPoolServer.execute(TThreadPoolServer.java:155)
> at
> org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:139)
> at
> org.apache.iotdb.commons.service.AbstractThriftServiceThread.run(AbstractThriftServiceThread.java:258)
> 2022-11-18 14:29:53,751 [ClientRPC-Service] ERROR
> o.a.i.c.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
> ClientRPC-Service-42
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> org.apache.thrift.server.TThreadPoolServer.execute(TThreadPoolServer.java:155)
> at
> org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:139)
> at
> org.apache.iotdb.commons.service.AbstractThriftServiceThread.run(AbstractThriftServiceThread.java:258)
> 2022-11-18 14:30:11,736 [pool-6-IoTDB-Flush-4] ERROR
> o.a.i.d.e.s.TsFileProcessor:1095 - root.test.g_0-6:
> /data/iotdb/m_1118_3d5eeae/sbin/../data/datanode/data/unsequence/root.test.g_0/6/2538/1668752675355-5-0-0.tsfile
> meet error when flushing a memtable, change system mode to error
> java.lang.OutOfMemoryError: unable to create native thread: possibly out of
> memory or process/resource limits reached
> at java.base/java.lang.Thread.start0(Native Method)
> at java.base/java.lang.Thread.start(Thread.java:803)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1354)
> at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
> at
> org.apache.iotdb.db.rescon.AbstractPoolManager.submit(AbstractPoolManager.java:56)
> at
> org.apache.iotdb.db.engine.flush.MemTableFlushTask.(MemTableFlushTask.java:88)
> at
> org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.flushOneMemTable(TsFileProcessor.java:1082)
> at
> org.apache.iotdb.db.engine.flush.FlushManager$FlushThread.runMayThrow(FlushManager.java:108)
> at
> org.apache.iotdb.commons.concurrent.WrappedRunnable.run(WrappedRunnable.java:29)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 2022-11-18 14:30:11,736 [pool-6-IoTDB-Flush-4] ERROR
> o.a.i.c.e.HandleSystemErrorStrategy:37 - Unrecoverable error
[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 Backlog > [ wal_mode=SYNC ] Performance needs to be optimized > --- > > Key: IOTDB-4164 > URL: https://issues.apache.org/jira/browse/IOTDB-4164 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/WAL, mpp-cluster >Reporter: 刘珍 >Assignee: Haiming Zhu >Priority: Major > Attachments: image-2022-08-17-11-38-15-849.png, > image-2022-10-10-09-59-07-692.png > > > wal_mode=SYNC的性能需优化 : 同样（bm）配置，SYNC耗时/ASYNC=2.77 > !image-2022-08-17-11-38-15-849.png! > 复现流程见 > https://issues.apache.org/jira/browse/IOTDB-4161?filter=-2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5331) [Pipeline] PipelineBreaker for AggregationOperator
liaolanyu created IOTDB-5331: Summary: [Pipeline] PipelineBreaker for AggregationOperator Key: IOTDB-5331 URL: https://issues.apache.org/jira/browse/IOTDB-5331 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu https://apache-iotdb.feishu.cn/docx/FzhhddukiosAxexUbdAchf78nFh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-2649) [Compaction]How do I know if the compaction thread is stuck or if there are no compaction tasks?
[ https://issues.apache.org/jira/browse/IOTDB-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qingxin Feng reassigned IOTDB-2649: --- Assignee: Liuxuxin (was: Jialin Qiao) > [Compaction]How do I know if the compaction thread is stuck or if there are > no compaction tasks? > - > > Key: IOTDB-2649 > URL: https://issues.apache.org/jira/browse/IOTDB-2649 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Compaction >Reporter: FengQingxin >Assignee: Liuxuxin >Priority: Major > Attachments: log_all.log > > > Hi IoTDBers > How do I know if the compaction thread is stuck or if there are no > compaction tasks? > From the log file I can't find that information. > In v0.12,I can see the log as "2022-02-26 08:18:35,625 > [pool-18-IoTDB-Compaction_Schedule-root.ip5.ip55-0-1] INFO > o.a.i.d.e.c.c.r.s.RewriteCompactionFileSelector:115 - No merge candidates are > found" > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5077) [SHOW REGION]New command formats need to be supported
[ https://issues.apache.org/jira/browse/IOTDB-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qingxin Feng reassigned IOTDB-5077: --- Assignee: Gaofei Cao (was: Jialin Qiao) > [SHOW REGION]New command formats need to be supported > - > > Key: IOTDB-5077 > URL: https://issues.apache.org/jira/browse/IOTDB-5077 > Project: Apache IoTDB > Issue Type: New Feature > Components: Core/Cluster >Reporter: FengQingxin >Assignee: Gaofei Cao >Priority: Major > > Hi, > As a DBA,when I using SHOW REGION to maintan the cluster which has more > than 20 Regions,I want to show the region on one datanode. > It looks like : show regions on 172.20.70.22 or show regions on > NodeID1,NodeID2 > > Thanks, > B.R. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 slow
> ---
>
> Key: IOTDB-5275
> URL: https://issues.apache.org/jira/browse/IOTDB-5275
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: master branch
>Reporter: 刘珍
>Assignee: 周沛辰
>Priority: Major
> Attachments: 1_shunxu.conf, 2_shunxu.conf, 3_shunxu.conf,
> 4_shunxu.conf, image-2022-12-23-22-27-49-731.png
>
>
> m_1222_656d281
> 问题描述：
> 对齐序列，全部是顺序数据，无其他读写操作，
> 默认配置（cross_performer=read_point
> inner_seq_performer=read_chunk
> inner_unseq_performer=read_point
> ）
> {color:#de350b}合并慢{color}
> !image-2022-12-23-22-27-49-731.png|width=987,height=390!
> 测试环境
> 1. 私有云1期
> 关合并，生成数据。
> 配置文件见附件
> 2.对比合并性能，无其他读写操作。
> ConfigNode配置
> MAX_HEAP_SIZE="2G"
> DataNode配置
> MAX_HEAP_SIZE="18G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> Common配置
> {color:#de350b}*time_partition_interval=6048000
> compaction_io_rate_per_sec=1000*{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (IOTDB-5111) [ ratis ] Data is distributed across disks ，after the cluster is restarted, all data is lost
[
https://issues.apache.org/jira/browse/IOTDB-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyu Tan reopened IOTDB-5111:
--
> [ ratis ] Data is distributed across disks ，after the cluster is restarted,
> all data is lost
>
>
> Key: IOTDB-5111
> URL: https://issues.apache.org/jira/browse/IOTDB-5111
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 1.0.0
>Reporter: 刘珍
>Assignee: Song Ziyang
>Priority: Major
> Attachments: image-2022-12-02-17-58-45-096.png,
> image-2022-12-02-17-59-05-010.png
>
>
> rel/1.0
> config/schema/data 3个协议均是ratis，
> dn_data_dirs=data/datanode/data,/data1/iotdb/datanode/data
> 跨盘存储，
> 写入数据，重启集群，{color:#DE350B}*数据全部丢失*{color}。
> 还有1个问题，{color:#DE350B}snapshot目录下依然有.tmp.文件夹名称{color}：
> !image-2022-12-02-17-59-05-010.png!
> 测试环境-私有云1期 8C32GB
> 1. 3副本3C7D
> Common
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> schema_replication_factor=3
> data_replication_factor=3
> wal_buffer_size_in_byte=1048576
> max_waiting_time_when_insert_blocked=360
> query_timeout_threshold=3600
> ConfigNode
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> DataNode
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> dn_data_dirs=data/datanode/data,/data1/iotdb/datanode/data
> 2. 启动BM 写入数据
> GROUP_NUMBER=1
> DEVICE_NUMBER=1000
> REAL_INSERT_RATE=1.0
> SENSOR_NUMBER=1000
> IS_SENSOR_TS_ALIGNMENT=true
> IS_OUT_OF_ORDER=false
> OUT_OF_ORDER_RATIO=0.5
> OPERATION_PROPORTION=1:0:0:0:0:0:0:0:0:0:0
> CLIENT_NUMBER=50
> LOOP=1
> BATCH_SIZE_PER_WRITE=10
> START_TIME=2018-8-30T00:00:00+08:00
> POINT_STEP=200
> OP_MIN_INTERVAL=0
> OP_MIN_INTERVAL_RANDOM=false
> INSERT_DATATYPE_PROPORTION=1:1:1:1:1:1
> ENCODINGS=PLAIN/PLAIN/PLAIN/PLAIN/PLAIN/PLAIN
> COMPRESSOR=SNAPPY
> IS_DELETE_DATA=false
> CREATE_SCHEMA=true
> BENCHMARK_CLUSTER=false
> !image-2022-12-02-17-58-45-096.png!
> 3. 重启集群
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-5245) [last query]The last query data is incomplete
[
https://issues.apache.org/jira/browse/IOTDB-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653720#comment-17653720
]
liaolanyu commented on IOTDB-5245:
--
验证： !image-2023-01-03-09-27-12-679.png!
> [last query]The last query data is incomplete
> -
>
> Key: IOTDB-5245
> URL: https://issues.apache.org/jira/browse/IOTDB-5245
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query, mpp-cluster
>Affects Versions: 1.0.1
>Reporter: xiaozhihong
>Assignee: liaolanyu
>Priority: Major
>
> Start 1C1D, default conf.
> Enter CLi, then execute last quey.
> {code:java}
> It costs 0.134s
> IoTDB> select ** from root;
> +-+-++
> |
> Time|root.ln.wf01.wt01.temperature|root.ln.wf01.wt01.status|
> +-+-++
> |2017-11-01T00:00:00.000+08:00| 25.99|
> true|
> |2017-11-01T02:00:00.000+08:00| 25.99|
> true|
> |2017-11-01T03:00:00.000+08:00| 25.99|
> true|
> |2017-11-02T00:00:00.000+08:00| 26.92|
> false|
> |2017-11-02T02:00:00.000+08:00| 26.92|
> false|
> |2017-11-03T00:00:00.000+08:00| 26.0|
> true|
> |2017-11-04T00:00:00.000+08:00| 23.29|
> true|
> |2017-11-05T00:00:00.000+08:00| 24.19|
> true|
> |2017-11-06T00:00:00.000+08:00| 20.19|
> false|
> |2017-11-06T03:00:00.000+08:00| 20.19|
> false|
> |2017-11-07T00:00:00.000+08:00| 22.12|
> false|
> |2017-11-07T23:50:00.000+08:00| 20.12|
> false|
> |2017-11-07T23:52:00.000+08:00| 21.22|
> false|
> |2017-11-07T23:55:00.000+08:00| 21.22|
> true|
> |2017-11-07T23:59:30.000+08:00| 28.12|
> true|
> |2017-11-08T00:00:00.000+08:00| 23.99|
> true|
> |2018-11-03T00:00:00.000+08:00| 20.99|
> false|
> |2018-11-06T00:00:00.000+08:00| 25.99|
> true|
> |2019-11-05T00:00:00.000+08:00| 19.99|
> true|
> |2019-11-07T00:00:00.000+08:00| 24.19|
> true|
> +-+-++
> Total line number = 20
> It costs 0.065s
> IoTDB> select last * from root.ln.**;
> +-++-++
> | Time| Timeseries|Value|DataType|
> +-++-++
> |2019-11-07T00:00:00.000+08:00|root.ln.wf01.wt01.status| true| BOOLEAN|
> +-++-++
> Total line number = 1
> It costs 0.015s
> {code}
> Only one sequence of results was queried.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-5245) [last query]The last query data is incomplete
[
https://issues.apache.org/jira/browse/IOTDB-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653719#comment-17653719
]
liaolanyu commented on IOTDB-5245:
--
https://github.com/apache/iotdb/pull/8683
> [last query]The last query data is incomplete
> -
>
> Key: IOTDB-5245
> URL: https://issues.apache.org/jira/browse/IOTDB-5245
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query, mpp-cluster
>Affects Versions: 1.0.1
>Reporter: xiaozhihong
>Assignee: liaolanyu
>Priority: Major
>
> Start 1C1D, default conf.
> Enter CLi, then execute last quey.
> {code:java}
> It costs 0.134s
> IoTDB> select ** from root;
> +-+-++
> |
> Time|root.ln.wf01.wt01.temperature|root.ln.wf01.wt01.status|
> +-+-++
> |2017-11-01T00:00:00.000+08:00| 25.99|
> true|
> |2017-11-01T02:00:00.000+08:00| 25.99|
> true|
> |2017-11-01T03:00:00.000+08:00| 25.99|
> true|
> |2017-11-02T00:00:00.000+08:00| 26.92|
> false|
> |2017-11-02T02:00:00.000+08:00| 26.92|
> false|
> |2017-11-03T00:00:00.000+08:00| 26.0|
> true|
> |2017-11-04T00:00:00.000+08:00| 23.29|
> true|
> |2017-11-05T00:00:00.000+08:00| 24.19|
> true|
> |2017-11-06T00:00:00.000+08:00| 20.19|
> false|
> |2017-11-06T03:00:00.000+08:00| 20.19|
> false|
> |2017-11-07T00:00:00.000+08:00| 22.12|
> false|
> |2017-11-07T23:50:00.000+08:00| 20.12|
> false|
> |2017-11-07T23:52:00.000+08:00| 21.22|
> false|
> |2017-11-07T23:55:00.000+08:00| 21.22|
> true|
> |2017-11-07T23:59:30.000+08:00| 28.12|
> true|
> |2017-11-08T00:00:00.000+08:00| 23.99|
> true|
> |2018-11-03T00:00:00.000+08:00| 20.99|
> false|
> |2018-11-06T00:00:00.000+08:00| 25.99|
> true|
> |2019-11-05T00:00:00.000+08:00| 19.99|
> true|
> |2019-11-07T00:00:00.000+08:00| 24.19|
> true|
> +-+-++
> Total line number = 20
> It costs 0.065s
> IoTDB> select last * from root.ln.**;
> +-++-++
> | Time| Timeseries|Value|DataType|
> +-++-++
> |2019-11-07T00:00:00.000+08:00|root.ln.wf01.wt01.status| true| BOOLEAN|
> +-++-++
> Total line number = 1
> It costs 0.015s
> {code}
> Only one sequence of results was queried.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5078) [Performance]The performance of insert with out of order data is too low
[ https://issues.apache.org/jira/browse/IOTDB-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qingxin Feng reassigned IOTDB-5078: --- Assignee: Jinrui Zhang (was: Haonan Hou) > [Performance]The performance of insert with out of order data is too low > > > Key: IOTDB-5078 > URL: https://issues.apache.org/jira/browse/IOTDB-5078 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: FengQingxin >Assignee: Jinrui Zhang >Priority: Major > Attachments: common, image-2022-11-29-14-13-27-459.png > > > Hi, > When we using a server(8C32G) to test iotdb with 1C1D.But the performance of > insert with out of order data id lower than the performance of insert without > out of order data. > refer to below picture: > !image-2022-11-29-14-13-27-459.png|width=963,height=316! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4686) SchemaReader for schema query operator-refactor traverser
[ https://issues.apache.org/jira/browse/IOTDB-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yukun Zhou reassigned IOTDB-4686: - Assignee: Yukun Zhou (was: xieqijun) > SchemaReader for schema query operator-refactor traverser > - > > Key: IOTDB-4686 > URL: https://issues.apache.org/jira/browse/IOTDB-4686 > Project: Apache IoTDB > Issue Type: Sub-task >Reporter: xieqijun >Assignee: Yukun Zhou >Priority: Major > Labels: pull-request-available > > Refactor traverser in MTree to support iteratable schema read -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5268) [export-csv]export csv failed when multiple export working
[
https://issues.apache.org/jira/browse/IOTDB-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haonan Hou reassigned IOTDB-5268:
-
Assignee: Zhijia Cao (was: Haonan Hou)
> [export-csv]export csv failed when multiple export working
> --
>
> Key: IOTDB-5268
> URL: https://issues.apache.org/jira/browse/IOTDB-5268
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: changxue
>Assignee: Zhijia Cao
>Priority: Major
> Attachments: screenshot-1.png
>
>
> [export-csv]export csv failed when multiple export working
> command:
> {code}
> export-csv.sh -h iotdb-44 -p 6667 -u root -pw root -f s_${cols} -tf
> -MM-dd\ HH:mm:ss -linesPerFile 1 -td ${target} -q "select
> ${query_str} from root.test.g_0.d_$d"
> {code}
> {code}
> -td /data/csv/root.test.g_0/d_0 -f s_0 -q "select
> s_0,s_1,s_2,s_3,s_4,s_5,s_6,s_7,s_8,s_9 from root.test.g_0.d_0"
> --
> Starting IoTDB Client Export Script
> --
> Cannot dump result because: 301: FragmentInstance 20221222_082109_00011_1.1.0
> is aborted by timeout
> {code}
> 问题：
> 单独执行会成功，但是在另一台机器上也执行一个export-csv.sh，那么先执行的会失败。然后若干个之后，后执行的也失败了。
> 也就是说，不稳定。同样的语句，随着执行的export增加，会失败。
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5330) [Metric] Update Zh Metric Doc
Hongyin Zhang created IOTDB-5330: Summary: [Metric] Update Zh Metric Doc Key: IOTDB-5330 URL: https://issues.apache.org/jira/browse/IOTDB-5330 Project: Apache IoTDB Issue Type: Improvement Reporter: Hongyin Zhang Assignee: Hongyin Zhang Update Normal Level metrics details of Metric Doc in zh. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5329) Exception handler for AbstractTreeVisitor
yanze chen created IOTDB-5329: - Summary: Exception handler for AbstractTreeVisitor Key: IOTDB-5329 URL: https://issues.apache.org/jira/browse/IOTDB-5329 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen Add exception handler for AbstractTreeVisitor -- This message was sent by Atlassian Jira (v8.20.10#820010)
