[
https://issues.apache.org/jira/browse/IOTDB-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577813#comment-17577813
]
Jinrui Zhang commented on IOTDB-3708:
-------------------------------------
For the NPE issue. It is because the `writeResponse` contains null variable
TSStatus in some scenarios. See this PR.
https://github.com/apache/iotdb/pull/6945
> ERROR o.a.i.d.u.ErrorHandlingUtils:60 - Status code:
> EXECUTE_STATEMENT_ERROR(400), operation: insertTablet failed NPE
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: IOTDB-3708
> URL: https://issues.apache.org/jira/browse/IOTDB-3708
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
> Affects Versions: 0.14.0-SNAPSHOT
> Reporter: 刘珍
> Assignee: Jinrui Zhang
> Priority: Blocker
> Attachments: config.properties, log-all-20220630.33.log.gz
>
>
> iotdb : master_0630_243a6da ，RatisConsensus，3副本 3C3D
> benchmark : bm_0527_e7b23aa
> 2022-06-30 17:39:03,781 [pool-20-IoTDB-RPC-Client-53] ERROR
> o.a.i.d.u.ErrorHandlingUtils:60 - Status code: EXECUTE_STATEMENT_ERROR(400),
> operation: insertTablet failed
> java.lang.NullPointerException: null
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchLocally(FragmentInstanceDispatcherImpl.java:246)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchOneInstance(FragmentInstanceDispatcherImpl.java:161)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatchWriteSync(FragmentInstanceDispatcherImpl.java:144)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.FragmentInstanceDispatcherImpl.dispatch(FragmentInstanceDispatcherImpl.java:93)
> at
> org.apache.iotdb.db.mpp.plan.scheduler.ClusterScheduler.start(ClusterScheduler.java:95)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.schedule(QueryExecution.java:215)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:169)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:131)
> at
> org.apache.iotdb.db.service.thrift.impl.DataNodeTSServiceImpl.insertTablet(DataNodeTSServiceImpl.java:911)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:3328)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$insertTablet.getResult(IClientRPCService.java:3308)
> 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.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. 私有云 172.20.70.13/14/16 客户端在ip2
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_replication_factor=3
> schema_replication_factor=3
> wal_buffer_size_in_byte=1048576
> benchmark配置见附件，连ip14 执行读写操作。
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
