[jira] [Assigned] (IOTDB-5284) [Sonar]Fix some code smells and bugs given by SonarLint
[ https://issues.apache.org/jira/browse/IOTDB-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxiangpeng reassigned IOTDB-5284: -- Assignee: huxiangpeng > [Sonar]Fix some code smells and bugs given by SonarLint > --- > > Key: IOTDB-5284 > URL: https://issues.apache.org/jira/browse/IOTDB-5284 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: huxiangpeng >Assignee: huxiangpeng >Priority: Major > Fix For: master branch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 Project: Apache IoTDB Issue Type: Bug Reporter: Jinrui Zhang Assignee: Haiming Zhu Reproduce steps: # generate data files using time partition configuration A (eg. 1 week) # backup data files # stop system and change time partition configuration to B (eg. 1 day) # restart system and see the time partition in memory ## we can check the time partition using Arthas, the cmd is such as `ognl "@org.apache.iotdb.db.engine.StorageEngine@getInstance().dataRegionMap.get(new org.apache.iotdb.commons.consensus.DataRegionId(6)).tsfileManager.unsequenceFiles"` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5284) [Sonar]Fix some code smells and bugs given by SonarLint
[ https://issues.apache.org/jira/browse/IOTDB-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651948#comment-17651948 ] huxiangpeng commented on IOTDB-5284: I'm doing this > [Sonar]Fix some code smells and bugs given by SonarLint > --- > > Key: IOTDB-5284 > URL: https://issues.apache.org/jira/browse/IOTDB-5284 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: huxiangpeng >Priority: Major > Fix For: master branch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5284) [Sonar]Fix some code smells and bugs given by SonarLint
huxiangpeng created IOTDB-5284: -- Summary: [Sonar]Fix some code smells and bugs given by SonarLint Key: IOTDB-5284 URL: https://issues.apache.org/jira/browse/IOTDB-5284 Project: Apache IoTDB Issue Type: Improvement Reporter: huxiangpeng Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5283) The error logs are not specific when remove datanode which is down when data replicat factor equals 1
Gaofei Cao created IOTDB-5283: - Summary: The error logs are not specific when remove datanode which is down when data replicat factor equals 1 Key: IOTDB-5283 URL: https://issues.apache.org/jira/browse/IOTDB-5283 Project: Apache IoTDB Issue Type: Improvement Reporter: Gaofei Cao Assignee: Gaofei Cao -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5282) Add show clusterName SQL
Gaofei Cao created IOTDB-5282: - Summary: Add show clusterName SQL Key: IOTDB-5282 URL: https://issues.apache.org/jira/browse/IOTDB-5282 Project: Apache IoTDB Issue Type: New Feature Reporter: Gaofei Cao Assignee: Yongzao Dan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5244) [ratis][remove datanode]installSnapshot failed
[ https://issues.apache.org/jira/browse/IOTDB-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651923#comment-17651923 ] Song Ziyang commented on IOTDB-5244: Corrupted MD5 是运行时可能出现的小概率事件。出现这个问题之后，系统会进行snapshot传输重试。因此，这个问题并不会影响系统的正常使用。这一条错误日志是可以忽略的。 > [ratis][remove datanode]installSnapshot failed > -- > > Key: IOTDB-5244 > URL: https://issues.apache.org/jira/browse/IOTDB-5244 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: master branch, 1.0.0 >Reporter: 刘珍 >Assignee: Song Ziyang >Priority: Major > Attachments: iotdb_5244.conf > > > rel/1.0 1216_c92440f > 1. 启动3副本3C5D集群，config/schema/data 均是ratis协议。 > 2. BM写入数据，完成。 > 配置见附件。 > 3.缩容节点（ip73）调用stop-datanode.sh，再start， > 再stop-datanode.sh，再start。 > 执行缩容。 > 4.ip68 datanode 报错 > 2022-12-19 20:25:22,705 [grpc-default-executor-4936] ERROR > o.a.r.s.i.SnapshotInstallationHandler:96 - 5@group-0001001E: > installSnapshot failed > org.apache.ratis.io.CorruptedFileException: File > /data/liuzhen_test/master_1216_d426f7a/data/datanode/data/snapshot/.tmp.group-0001001E/snapshot-c01d9ca8-3f9a-4b02-9fb4-fa680eae89e0/66_158230/sequence/root.test.g_3/30/2538/1671443330163-38-0-0.tsfile.resource > (exist? false, length=0) is corrupted: MD5 mismatch for snapshot-158230 > installation. Renamed temporary snapshot file > /data/liuzhen_test/master_1216_d426f7a/data/datanode/data/snapshot/.tmp.group-0001001E/snapshot-c01d9ca8-3f9a-4b02-9fb4-fa680eae89e0/66_158230/sequence/root.test.g_3/30/2538/1671443330163-38-0-0.tsfile.resource > to > /data/liuzhen_test/master_1216_d426f7a/data/datanode/data/snapshot/.tmp.group-0001001E/snapshot-c01d9ca8-3f9a-4b02-9fb4-fa680eae89e0/66_158230/sequence/root.test.g_3/30/2538/1671443330163-38-0-0.tsfile.resource.corrupt20221219-202522_690 > at > org.apache.ratis.server.storage.SnapshotManager.installSnapshot(SnapshotManager.java:155) > at > org.apache.ratis.server.impl.ServerState.installSnapshot(ServerState.java:480) > at > org.apache.ratis.server.impl.SnapshotInstallationHandler.checkAndInstallSnapshot(SnapshotInstallationHandler.java:181) > at > org.apache.ratis.server.impl.SnapshotInstallationHandler.installSnapshotImpl(SnapshotInstallationHandler.java:120) > at > org.apache.ratis.server.impl.SnapshotInstallationHandler.installSnapshot(SnapshotInstallationHandler.java:94) > at > org.apache.ratis.server.impl.RaftServerImpl.installSnapshot(RaftServerImpl.java:1517) > at > org.apache.ratis.server.impl.RaftServerProxy.installSnapshot(RaftServerProxy.java:640) > at > org.apache.ratis.grpc.server.GrpcServerProtocolService$2.process(GrpcServerProtocolService.java:242) > at > org.apache.ratis.grpc.server.GrpcServerProtocolService$2.process(GrpcServerProtocolService.java:239) > at > org.apache.ratis.grpc.server.GrpcServerProtocolService$ServerRequestStreamObserver.onNext(GrpcServerProtocolService.java:124) > at > org.apache.ratis.thirdparty.io.grpc.stub.ServerCalls$StreamingServerCallHandler$StreamingServerCallListener.onMessage(ServerCalls.java:262) > at > org.apache.ratis.thirdparty.io.grpc.ForwardingServerCallListener.onMessage(ForwardingServerCallListener.java:33) > at > org.apache.ratis.thirdparty.io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailableInternal(ServerCallImpl.java:332) > at > org.apache.ratis.thirdparty.io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailable(ServerCallImpl.java:315) > at > org.apache.ratis.thirdparty.io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1MessagesAvailable.runInContext(ServerImpl.java:834) > at > org.apache.ratis.thirdparty.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) > at > org.apache.ratis.thirdparty.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 测试环境 > 1. 192.168.10.62/66/68 3ConfigNode72cpu 256GB > 192.168.10.62/66/68/64/73 5DataNode > 73机器：48CPU 384GB > 2.数据库配置参数 > COMMON配置 > schema_replication_factor=3 > data_replication_factor=3 > data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus > query_timeout_threshold=360 > ConfigNode配置 > cn_connection_timeout_ms=12 > MAX_HEAP_SIZE="8G" > DataNode配置 > MAX_HEAP_SIZE="192G" > MAX_DIRECT_MEMORY_SIZE="32G" > dn_max_connection_for_internal_service=300 > 3.BM配置见附件 > 写入完成 > 4.ip73 > stop-datanode.sh > 清缓存，启动datanode > stop-datanode.sh >
[jira] [Created] (IOTDB-5281) Fix selecting deleted files in 0.13
周沛辰 created IOTDB-5281: -- Summary: Fix selecting deleted files in 0.13 Key: IOTDB-5281 URL: https://issues.apache.org/jira/browse/IOTDB-5281 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.0 Reporter: 周沛辰 Assignee: 周沛辰 Fix For: 0.13.4 Attachments: 20221226-120518.jpeg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5280) [Metric] Got a wrong timeseries number after restart the cluster
[ https://issues.apache.org/jira/browse/IOTDB-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] FengQingxin reassigned IOTDB-5280: -- Assignee: Yukun Zhou (was: Liuxuxin) > [Metric] Got a wrong timeseries number after restart the cluster > > > Key: IOTDB-5280 > URL: https://issues.apache.org/jira/browse/IOTDB-5280 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 1.0.0 >Reporter: FengQingxin >Assignee: Yukun Zhou >Priority: Minor > Attachments: image-2022-12-26-11-40-57-593.png > > > Reproduce: > commit version: 1.0.1-SNAPSHOT (Build: a7908ab-dev) > Steps: > 1. setup cluster (3C3D 3副本） > 2. using BM to insert data > 3. after all test finished,try to restart the cluster > 4. Check the result in iotdb-metric,like below picture > !image-2022-12-26-11-40-57-593.png! > [http://111.202.73.147:13000/d/TbEVYRw7A/apache-iotdb-datanode-dashboard?orgId=1=1672013871154=1672024516629=datanode=172.20.70.22:9091] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5280) CLONE - [Metric] Got a wrong number after restart the cluster
FengQingxin created IOTDB-5280: -- Summary: CLONE - [Metric] Got a wrong number after restart the cluster Key: IOTDB-5280 URL: https://issues.apache.org/jira/browse/IOTDB-5280 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 1.0.0 Reporter: FengQingxin Assignee: Liuxuxin Reproduce: commit version: 1.0.1-SNAPSHOT (Build: a7908ab-dev) Steps: 1. setup cluster (3C3D 3副本） 2. using BM to insert data 3. after all test finished,try to restart the cluster 4. Check the result in iotdb-metric,like below picture http://111.202.73.147:13000/d/TbEVYRw7A/apache-iotdb-datanode-dashboard?orgId=1=1672013871154=1672024516629=datanode=172.20.70.22:9091 !image-2022-12-26-11-30-04-470.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (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:all-tabpanel ] FengQingxin reassigned IOTDB-5279: -- Assignee: Liuxuxin > [Metric] Got a wrong number after restart the cluster > - > > Key: IOTDB-5279 > URL: https://issues.apache.org/jira/browse/IOTDB-5279 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Liuxuxin >Priority: Minor > Attachments: image-2022-12-26-11-30-04-470.png > > > Reproduce: > commit version: 1.0.1-SNAPSHOT (Build: a7908ab-dev) > Steps: > 1. setup cluster (3C3D 3副本） > 2. using BM to insert data > 3. after all test finished,try to restart the cluster > 4. Check the result in iotdb-metric,like below picture > http://111.202.73.147:13000/d/TbEVYRw7A/apache-iotdb-datanode-dashboard?orgId=1=1672013871154=1672024516629=datanode=172.20.70.22:9091 > !image-2022-12-26-11-30-04-470.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5279) [Metric] Got a wrong number after restart the cluster
Qingxin Feng created IOTDB-5279: --- Summary: [Metric] Got a wrong number after restart the cluster Key: IOTDB-5279 URL: https://issues.apache.org/jira/browse/IOTDB-5279 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 1.0.0 Reporter: Qingxin Feng Attachments: image-2022-12-26-11-30-04-470.png Reproduce: commit version: 1.0.1-SNAPSHOT (Build: a7908ab-dev) Steps: 1. setup cluster (3C3D 3副本） 2. using BM to insert data 3. after all test finished,try to restart the cluster 4. Check the result in iotdb-metric,like below picture http://111.202.73.147:13000/d/TbEVYRw7A/apache-iotdb-datanode-dashboard?orgId=1=1672013871154=1672024516629=datanode=172.20.70.22:9091 !image-2022-12-26-11-30-04-470.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5278) JDBC Driver cannot connect to the dbeaver
yang caiyin created IOTDB-5278: -- Summary: JDBC Driver cannot connect to the dbeaver Key: IOTDB-5278 URL: https://issues.apache.org/jira/browse/IOTDB-5278 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin Fix For: master branch, 1.0.1 In the metaDataset of jdbc, the incorrect use of tsblockbuilder to generate result tsblock without timecolumn causes an error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
