[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&focusedCommentId=17652409#comment-17652409
]
Jinrui Zhang commented on IOTDB-4986:
-
This issue is related to the ClientManager used in IoTDB cluster. [~LebronAl]
is fixing this issue
> 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.HandleSys
[jira] [Created] (IOTDB-5307) Failed to get TsFile input of file: NoSuchFileException
Pengfei Liu created IOTDB-5307: -- Summary: Failed to get TsFile input of file: NoSuchFileException Key: IOTDB-5307 URL: https://issues.apache.org/jira/browse/IOTDB-5307 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: Pengfei Liu Assignee: Pengfei Liu Attachments: image-2022-12-28-15-09-52-649.png 因TsFileResource状态修改存在并发问题，导致ttl删除文件和合并冲突，最终导致合并定时任务卡死，原因是未捕获到npe异常 问题现象如图: !image-2022-12-28-15-09-52-649.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5306) Change default port of ConfigNode and DataNode
Gaofei Cao created IOTDB-5306: - Summary: Change default port of ConfigNode and DataNode Key: IOTDB-5306 URL: https://issues.apache.org/jira/browse/IOTDB-5306 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-5305) The slow query log can not display the sql statement
Houliang Qi created IOTDB-5305: -- Summary: The slow query log can not display the sql statement Key: IOTDB-5305 URL: https://issues.apache.org/jira/browse/IOTDB-5305 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Houliang Qi Attachments: image-2022-12-28-13-00-50-738.png !image-2022-12-28-13-00-50-738.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5304) Adjust the column header's order of show cluster details
伊丹翔 created IOTDB-5304: -- Summary: Adjust the column header's order of show cluster details Key: IOTDB-5304 URL: https://issues.apache.org/jira/browse/IOTDB-5304 Project: Apache IoTDB Issue Type: Improvement Reporter: 伊丹翔 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5304) Adjust the column header's order of show cluster details
[ https://issues.apache.org/jira/browse/IOTDB-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 伊丹翔 reassigned IOTDB-5304: -- Sprint: 2022-12-ConfigNode Assignee: 伊丹翔 > Adjust the column header's order of show cluster details > > > Key: IOTDB-5304 > URL: https://issues.apache.org/jira/browse/IOTDB-5304 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: 伊丹翔 >Assignee: 伊丹翔 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5303) Support setting node number, consensus protocol and replica number from system properties
Eric Pai created IOTDB-5303: --- Summary: Support setting node number, consensus protocol and replica number from system properties Key: IOTDB-5303 URL: https://issues.apache.org/jira/browse/IOTDB-5303 Project: Apache IoTDB Issue Type: Test Components: Others Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch Currently, we have Simple and Cluster1 test modes, which consist 1C1D and 1C3D consistently. However, when we test in a cluster mode in private environments, we may need to change the default node nums, e.g. 3C3D. So the IT framework should leave the node num to be configurable. What's more, the consensus protocol and replica num needs to be relatived with the node num. So they should be exposed as system properties as well, and need to be checked before cluster setup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5302) Fix TsFiles being compacting cannot be queried
周沛辰 created IOTDB-5302: -- Summary: Fix TsFiles being compacting cannot be queried Key: IOTDB-5302 URL: https://issues.apache.org/jira/browse/IOTDB-5302 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.0, master branch, 1.0.0 Reporter: 周沛辰 Assignee: Jinrui Zhang When the status of the TsFile is Compacting or CompactionCandidate, the query will consider that these files are not closed according to the TsFileResource::isClosed() method, and the data in these TsFiles will not be found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5301) [confignode leader] The number of open file handles increases
刘珍 created IOTDB-5301: - Summary: [confignode leader] The number of open file handles increases Key: IOTDB-5301 URL: https://issues.apache.org/jira/browse/IOTDB-5301 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Affects Versions: master branch Reporter: 刘珍 Assignee: Gaofei Cao Attachments: image-2022-12-28-11-11-04-360.png master_1222_656d281 ConfigNode leader节点打开的文件句柄数有增多的现象，如下，1小时监控1次文件句柄数： !image-2022-12-28-11-11-04-360.png! 测试环境： 1. 192.168.10.62/66/68 72CPU256GB 3副本3C3D，BM 7*24小时写入测试。 2.集群配置参数 ConfigNode MAX_HEAP_SIZE="8G" DataNode MAX_HEAP_SIZE="192G" MAX_DIRECT_MEMORY_SIZE="32G" dn_max_connection_for_internal_service=300 Common配置 schema_replication_factor=3 data_replication_factor=3 iot_consensus_throttle_threshold_in_byte=536870912000 3.BM配置见附件 4.lsof -p confignode_pid 结果见附件 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5300) [MIGRATE REGION] Meets error in region migrate state
[ https://issues.apache.org/jira/browse/IOTDB-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaofei Cao reassigned IOTDB-5300: - Assignee: 陈哲涵 (was: Gaofei Cao) > [MIGRATE REGION] Meets error in region migrate state > > > Key: IOTDB-5300 > URL: https://issues.apache.org/jira/browse/IOTDB-5300 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: master branch >Reporter: 刘珍 >Assignee: 陈哲涵 >Priority: Major > Attachments: image-2022-12-28-10-39-02-695.png, > image-2022-12-28-10-40-59-938.png, image-2022-12-28-10-41-57-776.png, > image-2022-12-28-10-42-35-206.png, image-2022-12-28-10-45-20-688.png > > > master_1227_65fb480 > 1.查看region信息，RegionId=1 状态是ReadOnly > !image-2022-12-28-10-39-02-695.png! > 2.迁移region > ./sbin/start-cli.sh -h 172.16.2.5 -e "migrate region 1 from 3 to 13" > !image-2022-12-28-10-40-59-938.png! > 实际没有迁移成功 > !image-2022-12-28-10-41-57-776.png! > 再次迁移，提示目标节点已存在迁移region > !image-2022-12-28-10-42-35-206.png! > 3.ConfigNode日志 > !image-2022-12-28-10-45-20-688.png! > 测试环境 > 私有云1期 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5300) [MIGRATE REGION] Meets error in region migrate state
刘珍 created IOTDB-5300: - Summary: [MIGRATE REGION] Meets error in region migrate state Key: IOTDB-5300 URL: https://issues.apache.org/jira/browse/IOTDB-5300 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Reporter: 刘珍 Attachments: image-2022-12-28-10-39-02-695.png, image-2022-12-28-10-40-59-938.png, image-2022-12-28-10-41-57-776.png, image-2022-12-28-10-42-35-206.png, image-2022-12-28-10-45-20-688.png master_1227_65fb480 1.查看region信息，RegionId=1 状态是ReadOnly !image-2022-12-28-10-39-02-695.png! 2.迁移region ./sbin/start-cli.sh -h 172.16.2.5 -e "migrate region 1 from 3 to 13" !image-2022-12-28-10-40-59-938.png! 实际没有迁移成功 !image-2022-12-28-10-41-57-776.png! 再次迁移，提示目标节点已存在迁移region !image-2022-12-28-10-42-35-206.png! 3.ConfigNode日志 !image-2022-12-28-10-45-20-688.png! 测试环境 私有云1期 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5300) [MIGRATE REGION] Meets error in region migrate state
[ https://issues.apache.org/jira/browse/IOTDB-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 刘珍 reassigned IOTDB-5300: - Sprint: 2022-12-ConfigNode Affects Version/s: master branch Assignee: Gaofei Cao > [MIGRATE REGION] Meets error in region migrate state > > > Key: IOTDB-5300 > URL: https://issues.apache.org/jira/browse/IOTDB-5300 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: master branch >Reporter: 刘珍 >Assignee: Gaofei Cao >Priority: Major > Attachments: image-2022-12-28-10-39-02-695.png, > image-2022-12-28-10-40-59-938.png, image-2022-12-28-10-41-57-776.png, > image-2022-12-28-10-42-35-206.png, image-2022-12-28-10-45-20-688.png > > > master_1227_65fb480 > 1.查看region信息，RegionId=1 状态是ReadOnly > !image-2022-12-28-10-39-02-695.png! > 2.迁移region > ./sbin/start-cli.sh -h 172.16.2.5 -e "migrate region 1 from 3 to 13" > !image-2022-12-28-10-40-59-938.png! > 实际没有迁移成功 > !image-2022-12-28-10-41-57-776.png! > 再次迁移，提示目标节点已存在迁移region > !image-2022-12-28-10-42-35-206.png! > 3.ConfigNode日志 > !image-2022-12-28-10-45-20-688.png! > 测试环境 > 私有云1期 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5299) The metrics of the size of files is incorrect when the datanode restart
Houliang Qi created IOTDB-5299: -- Summary: The metrics of the size of files is incorrect when the datanode restart Key: IOTDB-5299 URL: https://issues.apache.org/jira/browse/IOTDB-5299 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Houliang Qi Attachments: image-2022-12-28-09-54-48-013.png The size of the file is incorrect when the datanode restart in the metrics dashbord. it will begin with zero. !image-2022-12-28-09-54-48-013.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5298) [confignode]Error in calling method getOrCreateSchemaPartitionTable, because: Fail to connect to any config node. Please check status of ConfigNodes
刘珍 created IOTDB-5298:
-
Summary: [confignode]Error in calling method
getOrCreateSchemaPartitionTable, because: Fail to connect to any config node.
Please check status of ConfigNodes
Key: IOTDB-5298
URL: https://issues.apache.org/jira/browse/IOTDB-5298
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: master branch
Reporter: 刘珍
Assignee: Gaofei Cao
master_1227_65fb480
创建元数据，报错（confignode一直在线，无故障操作）
2022-12-27 18:48:49,143 [pool-24-IoTDB-DataNodeInternalRPC-Processor-194]
{color:#DE350B}*ERROR o.a.i.d.m.e.e.RegionWriteExecutor:88 - An error occurred
when executing getOrCreateSchemaPartition():Error in calling method
getOrCreateSchemaPartitionTable, because: Fail to connect to any config node.
Please check status of ConfigNodes*{color}
org.apache.iotdb.db.exception.sql.StatementAnalyzeException: An error occurred
when executing getOrCreateSchemaPartition():Error in calling method
getOrCreateSchemaPartitionTable, because: Fail to connect to any config node.
Please check status of ConfigNodes
at
org.apache.iotdb.db.mpp.plan.analyze.ClusterPartitionFetcher.getOrCreateSchemaPartition(ClusterPartitionFetcher.java:155)
at
org.apache.iotdb.db.mpp.plan.analyze.AnalyzeVisitor.visitInternalCreateTimeseries(AnalyzeVisitor.java:1568)
at
org.apache.iotdb.db.mpp.plan.analyze.AnalyzeVisitor.visitInternalCreateTimeseries(AnalyzeVisitor.java:172)
at
org.apache.iotdb.db.mpp.plan.statement.internal.InternalCreateTimeSeriesStatement.accept(InternalCreateTimeSeriesStatement.java:94)
at
org.apache.iotdb.db.mpp.plan.statement.StatementVisitor.process(StatementVisitor.java:109)
at
org.apache.iotdb.db.mpp.plan.analyze.Analyzer.analyze(Analyzer.java:44)
at
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.analyze(QueryExecution.java:257)
at
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.(QueryExecution.java:141)
at
org.apache.iotdb.db.mpp.plan.Coordinator.createQueryExecution(Coordinator.java:104)
at
org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:137)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.ClusterSchemaFetcher.lambda$new$0(ClusterSchemaFetcher.java:64)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.AutoCreateSchemaExecutor.executeInternalCreateTimeseriesStatement(AutoCreateSchemaExecutor.java:191)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.AutoCreateSchemaExecutor.internalCreateTimeseries(AutoCreateSchemaExecutor.java:158)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.AutoCreateSchemaExecutor.autoCreateMissingMeasurements(AutoCreateSchemaExecutor.java:138)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.ClusterSchemaFetcher.checkAndAutoCreateMissingMeasurements(ClusterSchemaFetcher.java:320)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.ClusterSchemaFetcher.fetchSchemaWithAutoCreate(ClusterSchemaFetcher.java:186)
at
org.apache.iotdb.db.mpp.plan.analyze.schema.SchemaValidator.validate(SchemaValidator.java:52)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.executeDataInsert(RegionWriteExecutor.java:202)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:174)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitInsertTablet(RegionWriteExecutor.java:128)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.write.InsertTabletNode.accept(InsertTabletNode.java:1086)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:86)
at
org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.sendPlanNode(DataNodeInternalRPCServiceImpl.java:277)
at
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$sendPlanNode.getResult(IDataNodeRPCService.java:3607)
at
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$sendPlanNode.getResult(IDataNodeRPCService.java:3587)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
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)
此异常遇到3次。
本次测试场景
1. 启动3副本3C3D集群，启动1BM
10分钟后，再启动3DataNode，1BM。最终3C21D7BM
集群配置参数：
172.16.2.23~25 3ConfigNode
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE="6G"
172.16.2.2~22 21DataNode
MAX_HEAP_SIZE="20G
[jira] [Created] (IOTDB-5297) IoTDBClusterNodeErrorStartUpIT may be stucked by infinite retry
Eric Pai created IOTDB-5297: --- Summary: IoTDBClusterNodeErrorStartUpIT may be stucked by infinite retry Key: IOTDB-5297 URL: https://issues.apache.org/jira/browse/IOTDB-5297 Project: Apache IoTDB Issue Type: Test Components: Others Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch Attachments: image-2022-12-27-17-47-18-281.png See the codes in IoTDBClusterNodeErrorStartUpIT. If the cluster can't be ready forever, the test will be tracked in a dead loop and can't be finished. !image-2022-12-27-17-47-18-281.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5288) [Metric] Got a wrong number of files
[ https://issues.apache.org/jira/browse/IOTDB-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongyin Zhang reassigned IOTDB-5288: Assignee: Liuxuxin (was: Hongyin Zhang) > [Metric] Got a wrong number of files > > > Key: IOTDB-5288 > URL: https://issues.apache.org/jira/browse/IOTDB-5288 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Qingxin Feng >Assignee: Liuxuxin >Priority: Minor > Attachments: image-2022-12-27-08-39-27-765.png > > > commit version: version 1.0.1-SNAPSHOT (Build: 752d7cf) > Got a wrong number of files, like below picture. > !image-2022-12-27-08-39-27-765.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5296) fix close session npe when session is null
Pengfei Liu created IOTDB-5296: -- Summary: fix close session npe when session is null Key: IOTDB-5296 URL: https://issues.apache.org/jira/browse/IOTDB-5296 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: Pengfei Liu Assignee: Pengfei Liu 2022-12-10 00:00:25,353 [pool-16-IoTDB-RPC-Client-2074] ERROR o.a.t.ProcessFunction:47 - Internal error processing closeSession java.lang.NullPointerException: null at org.apache.iotdb.db.service.thrift.impl.TSServiceImpl.closeSession(TSServiceImpl.java:343) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$closeSession.getResult(TSIService.java:3076) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$closeSession.getResult(TSIService.java:3056) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at org.apache.iotdb.db.service.thrift.ProcessorWithMetrics.process(ProcessorWithMetrics.java:64) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 2022-12-10 00:00:25,353 [pool-16-IoTDB-RPC-Client-2074] ERROR o.a.t.s.TThreadPoolServer$WorkerProcess:258 - Thrift Error occurred during processing of message. org.apache.thrift.transport.TTransportException: Read a negative frame size (-2147418111)! at org.apache.iotdb.rpc.TElasticFramedTransport.readFrame(TElasticFramedTransport.java:117) at org.apache.iotdb.rpc.TElasticFramedTransport.read(TElasticFramedTransport.java:107) at org.apache.thrift.transport.TTransport.readAll(TTransport.java:109) at org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:416) at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:255) at org.apache.iotdb.db.service.thrift.ProcessorWithMetrics.process(ProcessorWithMetrics.java:50) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5295) iot-benchmark the query statements should be updated according to the latest IoTDB
changxue created IOTDB-5295: --- Summary: iot-benchmark the query statements should be updated according to the latest IoTDB Key: IOTDB-5295 URL: https://issues.apache.org/jira/browse/IOTDB-5295 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: changxue Assignee: Jialin Qiao iot-benchmark the query statements should be updated according to the latest IoTDB the Q1 ~ Q10 query statements are too old to IoTDB, should be updated. e.g. the last query, in benchmark it is like "select ? from ? where time=max(time)" But now , we have" select last ? from ? " It's better if giving the detail info of what kind of query statements have been executed and the cost time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
