You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Yongzao Dan (Jira)" <ji...@apache.org> on 2023/01/01 09:05:00 UTC
[jira] [Assigned] (IOTDB-5298) [confignode]Error in calling method getOrCreateSchemaPartitionTable, because: Fail to connect to any config node. Please check status of ConfigNodes
[ https://issues.apache.org/jira/browse/IOTDB-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yongzao Dan reassigned IOTDB-5298:
----------------------------------
Assignee: Yongzao Dan (was: Gaofei Cao)
> [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: Yongzao Dan
> Priority: Major
> Attachments: iotdb_5298.sh, ip26_config.properties, ip27_config.properties, ip28_config.properties, ip29_config.properties, ip30_config.properties, ip31_config.properties, ip32_config.properties
>
>
> 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.<init>(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"
> MAX_DIRECT_MEMORY_SIZE="6G"
> COMMON配置
> schema_replication_factor=3
> data_replication_factor=3
> 路径
> /data/iotdb/master_1227_65fb480
> 172.16.2.26~32 7BM
> 2. 测试脚本见附件
> 3.BM配置见附件
--
This message was sent by Atlassian Jira
(v8.20.10#820010)