[jira] [Created] (IOTDB-5551) stop-datanode.sh should improve to add stopping stage to make sure the datanode process exit safely
changxue created IOTDB-5551: --- Summary: stop-datanode.sh should improve to add stopping stage to make sure the datanode process exit safely Key: IOTDB-5551 URL: https://issues.apache.org/jira/browse/IOTDB-5551 Project: Apache IoTDB Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: changxue Assignee: Xinyu Tan stop-datanode.sh should improve to add stopping stage to make sure the datanode process exit safely actual result: stop-datanode.sh would end immediately through the datanode process was still existed. expect result: As a user, I'd like to see the datanode process was ended when the stop-datanode.sh ended successfully. I prefer to waiting several seconds to make sure the datanode service is ended, rather than get a unknown result immediately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5523) Definition of IdentiySinkNode and ShuffleSinkNode
[ https://issues.apache.org/jira/browse/IOTDB-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690184#comment-17690184 ] liaolanyu commented on IOTDB-5523: -- https://apache-iotdb.feishu.cn/docx/QOsOdydlBo0cBVxZLeycVulgnAb > Definition of IdentiySinkNode and ShuffleSinkNode > - > > Key: IOTDB-5523 > URL: https://issues.apache.org/jira/browse/IOTDB-5523 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: liaolanyu >Assignee: liaolanyu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5523) Definition of IdentiySinkNode and ShuffleSinkNode
[ https://issues.apache.org/jira/browse/IOTDB-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690185#comment-17690185 ] liaolanyu commented on IOTDB-5523: -- Above is the related design doc. > Definition of IdentiySinkNode and ShuffleSinkNode > - > > Key: IOTDB-5523 > URL: https://issues.apache.org/jira/browse/IOTDB-5523 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: liaolanyu >Assignee: liaolanyu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5550) [memory]OOM occurs when insert less than 1M data with benchmark and default configurations of IoTDB
[
https://issues.apache.org/jira/browse/IOTDB-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690175#comment-17690175
]
changxue commented on IOTDB-5550:
-
datanode日志中有很多OOM，写入数据量并不大：10设备400sensor 1客户端 1次写入100行，落磁盘不到1M。
metric监控显示memory 并未使用多少，gc统计为0，OOM的thread并未结束（监控的数量未变）写入时间十几分钟，然后使用cli连接不上。
> [memory]OOM occurs when insert less than 1M data with benchmark and default
> configurations of IoTDB
> ---
>
> Key: IOTDB-5550
> URL: https://issues.apache.org/jira/browse/IOTDB-5550
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Engine
>Reporter: changxue
>Assignee: Jinrui Zhang
>Priority: Major
> Attachments: IOTDB-5550.tar.gz, image-2023-02-17-14-28-57-874.png
>
>
> [memory]OOM occurs when insert less than 1M data with benchmark and default
> configurations of IoTDB
> build:
> master 1a69b40 1.1.0-SNAPSHOT
> reproduction:
> 1. start 1C1D with the configurations of attachment
> 2. run benchmarks to insert data into IoTDB
> datanode log:
> {code}
> 2023-02-17 10:56:32,311 [pool-24-IoTDB-DataNodeInternalRPC-Processor-1] ERROR
> o.a.i.c.c.t.WrappedThreadPoolExecutor:108 - Exception in thread pool
> org.apache.iotdb.threadpool:type=DataNodeInternalRPC-Processor
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2023-02-17 10:56:21,422 [pool-19-IoTDB-ratis-bg-disk-guardian-1] ERROR
> o.a.i.c.c.t.ScheduledExecutorUtil:191 - Run thread failed
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2023-02-17 10:56:50,734 [pool-23-IoTDB-MPPCoordinatorScheduled-9] WARN
> o.a.i.d.m.p.s.SimpleQueryTerminator:108 - cancel query
> 20230217_025125_00644_1 on node TEndPoint(ip:iotdb-44, port:10730) failed.
> org.apache.thrift.TException: Error in calling method cancelQuery, because:
> GC overhead limit exceeded
> at
> org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:57)
> at
> org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$c055cf81.cancelQuery()
> at
> org.apache.iotdb.db.mpp.plan.scheduler.SimpleQueryTerminator.syncTerminate(SimpleQueryTerminator.java:102)
> at
> org.apache.iotdb.commons.concurrent.WrappedCallable$1.callMayThrow(WrappedCallable.java:46)
> at
> org.apache.iotdb.commons.concurrent.WrappedCallable.call(WrappedCallable.java:31)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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)
> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
> {code}
> disk taken:
> {code}
> 4.1M ./datanode/consensus
> 28K ./datanode/data
> 40M ./datanode/wal
> 64K ./datanode/system
> 45M ./datanode
> 4.1M ./confignode/consensus
> 24K ./confignode/system
> 4.1M ./confignode
> 49M .
> {code}
> metric monitor:
> !image-2023-02-17-14-28-57-874.png|thumbnail|width=800!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5550) [memory]OOM occurs when insert less than 1M data with benchmark and default configurations of IoTDB
changxue created IOTDB-5550:
---
Summary: [memory]OOM occurs when insert less than 1M data with
benchmark and default configurations of IoTDB
Key: IOTDB-5550
URL: https://issues.apache.org/jira/browse/IOTDB-5550
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Reporter: changxue
Assignee: Jinrui Zhang
Attachments: image-2023-02-17-14-28-57-874.png
[memory]OOM occurs when insert less than 1M data with benchmark and default
configurations of IoTDB
build:
master 1a69b40 1.1.0-SNAPSHOT
reproduction:
1. start 1C1D with the configurations of attachment
2. run benchmarks to insert data into IoTDB
datanode log:
{code}
2023-02-17 10:56:32,311 [pool-24-IoTDB-DataNodeInternalRPC-Processor-1] ERROR
o.a.i.c.c.t.WrappedThreadPoolExecutor:108 - Exception in thread pool
org.apache.iotdb.threadpool:type=DataNodeInternalRPC-Processor
java.lang.OutOfMemoryError: GC overhead limit exceeded
2023-02-17 10:56:21,422 [pool-19-IoTDB-ratis-bg-disk-guardian-1] ERROR
o.a.i.c.c.t.ScheduledExecutorUtil:191 - Run thread failed
java.lang.OutOfMemoryError: GC overhead limit exceeded
2023-02-17 10:56:50,734 [pool-23-IoTDB-MPPCoordinatorScheduled-9] WARN
o.a.i.d.m.p.s.SimpleQueryTerminator:108 - cancel query 20230217_025125_00644_1
on node TEndPoint(ip:iotdb-44, port:10730) failed.
org.apache.thrift.TException: Error in calling method cancelQuery, because: GC
overhead limit exceeded
at
org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:57)
at
org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$c055cf81.cancelQuery()
at
org.apache.iotdb.db.mpp.plan.scheduler.SimpleQueryTerminator.syncTerminate(SimpleQueryTerminator.java:102)
at
org.apache.iotdb.commons.concurrent.WrappedCallable$1.callMayThrow(WrappedCallable.java:46)
at
org.apache.iotdb.commons.concurrent.WrappedCallable.call(WrappedCallable.java:31)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
{code}
disk taken:
{code}
4.1M./datanode/consensus
28K ./datanode/data
40M ./datanode/wal
64K ./datanode/system
45M ./datanode
4.1M./confignode/consensus
24K ./confignode/system
4.1M./confignode
49M .
{code}
metric monitor:
!image-2023-02-17-14-28-57-874.png|thumbnail|width=800!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5549) [Schema_File] Ensure concurrently memory release
yanze chen created IOTDB-5549: - Summary: [Schema_File] Ensure concurrently memory release Key: IOTDB-5549 URL: https://issues.apache.org/jira/browse/IOTDB-5549 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5547) [ query ] executeStatement failed : Caused by: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException: null
[
https://issues.apache.org/jira/browse/IOTDB-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuan Tian reassigned IOTDB-5547:
Assignee: Alima777 (was: Yuan Tian)
> [ query ] executeStatement failed : Caused by:
> org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException:
> null
>
>
> Key: IOTDB-5547
> URL: https://issues.apache.org/jira/browse/IOTDB-5547
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query, mpp-cluster
>Affects Versions: 1.1.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Alima777
>Priority: Minor
> Attachments: iotdb_4350.conf
>
>
> master 0215_077704e
> Query execution occasionally fails ，
> select min_time(s_0),max_time(s_0),count(s_0) from root.** align by device
> （1000dev * 2000 ts)：
> 2023-02-16 17:59:07,908 [pool-25-IoTDB-ClientRPC-Processor-121] INFO
> o.a.i.d.q.c.SessionManager:116 - IoTDB: Login status: Login successfully.
> User : root, opens Session-304-root:192.168.10.72:54342
> 2023-02-16 17:59:07,982 [pool-25-IoTDB-ClientRPC-Processor-121] INFO
> o.a.i.d.s.t.i.ClientRPCServiceImpl:624 - IoTDB server version: 1.1.0-SNAPSHOT
> (Build: 077704e)
> 2023-02-16 17:59:09,829
> [Query-Worker-Thread-40$20230216_095908_30548_3.9.0.1] INFO
> o.a.i.d.e.c.TimeSeriesMetadataCache:86 - TimeseriesMetadataCache size =
> 16476198218
> 2023-02-16 17:59:09,834
> [Query-Worker-Thread-30$20230216_095908_30548_3.6.0.1] INFO
> o.a.i.d.e.c.BloomFilterCache:56 - BloomFilterCache size = 82380991
> 2023-02-16 17:59:10,061
> [Query-Worker-Thread-2$20230216_095908_30548_3.27.0.1] INFO
> o.a.i.d.e.c.ChunkCache:67 - ChunkCache size = 8238099109
> {color:red}2023-02-16 17:59:13,827 [pool-25-IoTDB-ClientRPC-Processor-121]
> WARN o.a.i.d.u.ErrorHandlingUtils:89 - Status code: 301, Query Statement:
> "select min_time(s_0),max_time(s_0),count(s_0) from root.** align by device".
> executeStatement failed
> org.apache.iotdb.commons.exception.IoTDBException:
> org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException{color}
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.dealWithException(QueryExecution.java:467)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getResult(QueryExecution.java:450)
> at
> org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getByteBufferBatchResult(QueryExecution.java:485)
> at
> org.apache.iotdb.db.utils.QueryDataSetUtils.convertQueryResultByFetchSize(QueryDataSetUtils.java:254)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.lambda$static$0(ClientRPCServiceImpl.java:165)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:239)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:476)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3629)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3609)
> 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(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)
> {color:red}Caused by:
> org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException:
> null{color}
> at
> java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1043)
> at java.base/java.util.ArrayList$Itr.remove(ArrayList.java:1011)
> at
> org.apache.iotdb.db.mpp.execution.driver.DataDriver.addUsedFilesForQuery(DataDriver.java:168)
> at
> org.apache.iotdb.db.mpp.execution.driver.DataDriver.addUsedFilesForQuery(DataDriver.java:148)
> at
> org.apache.iotdb.db.mpp.execution.driver.DataDriver.initQueryDataSource(DataDriver.java:135)
> at
> org.apache.iotdb.db.mpp.execution.driver.DataDriver.initialize(DataDriver.java:101)
> at
> org.apache.iotdb.db.mpp.execution.driver.DataDriver.init(DataDriver.java:63)
> at
> org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:139)
> at
>
[jira] [Reopened] (IOTDB-5469) [template]create template with backquote characters successfully but get schema info failed
[
https://issues.apache.org/jira/browse/IOTDB-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
changxue reopened IOTDB-5469:
-
master 1a69b40
!image-2023-02-17-10-29-34-459.png|width=800!
> [template]create template with backquote characters successfully but get
> schema info failed
> ---
>
> Key: IOTDB-5469
> URL: https://issues.apache.org/jira/browse/IOTDB-5469
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Schema Manager
>Affects Versions: 1.1.0-SNAPSHOT
>Reporter: changxue
>Assignee: liaolanyu
>Priority: Major
> Labels: pull-request-available
> Attachments: names-error.csv
>
>
> [template]create template with backquote characters successfully but get
> schema info failed
> reproduction
> 1. create a template named `123`
> {code}
> String[] names = new String[]{"c", "_start", "_Start", "`123`"};
> boolean isAligned = true;
> Map structureInfo = new LinkedHashMap<>(6);
> structureInfo.put("s_boolean", new Object[]{TSDataType.BOOLEAN,
> TSEncoding.RLE, CompressionType.SNAPPY});
> structureInfo.put("s_int", new Object[]{TSDataType.INT32,
> TSEncoding.RLE, CompressionType.SNAPPY});
> structureInfo.put("s_long", new Object[]{TSDataType.INT64,
> TSEncoding.RLE, CompressionType.SNAPPY});
> structureInfo.put("s_float", new Object[]{TSDataType.FLOAT,
> TSEncoding.GORILLA, CompressionType.SNAPPY});
> structureInfo.put("s_double", new Object[]{TSDataType.DOUBLE,
> TSEncoding.GORILLA, CompressionType.SNAPPY});
> structureInfo.put("s_text", new Object[]{TSDataType.TEXT,
> TSEncoding.DICTIONARY, CompressionType.SNAPPY});
> for (String templateName: names ) {
> String loadNode = "root.template.aligned."+templateName;
> Template template = new Template(templateName, isAligned);
> structureInfo.forEach((key, value) -> {
> MeasurementNode mNode =
> new MeasurementNode(key, (TSDataType) value[0],
> (TSEncoding) value[1], (CompressionType) value[2]);
> try {
> template.addToTemplate(mNode);
> } catch (StatementExecutionException e) {
> throw new RuntimeException(e);
> }
> });
> session.createSchemaTemplate(template);
> // IOTDB-5437 StatementExecutionException: 300:
> COUNT_MEASUREMENTShas not been supported.
> //assert 6 == session.countMeasurementsInTemplate(templateName) :
> "查看模版中sensor数目";
> session.setSchemaTemplate(templateName, loadNode);
> {code}
> 2. start-cli.sh
> {code}
> IoTDB> show schema templates
> ++
> |TemplateName|
> ++
> | `123`|
> | c|
> | _start|
> | _Start|
> ++
> Total line number = 4
> It costs 0.018s
> IoTDB> show nodes in schema template `123`
> Msg: 305: org.apache.iotdb.commons.exception.IoTDBException: get template
> info error.
> {code}
> datanode logs:
> {code}
> 2023-02-03 17:08:08,488 [pool-21-IoTDB-MPPCoordinator-12] WARN
> o.a.i.d.m.p.e.c.ConfigExecution:131 - Failures happened during running
> ConfigExecution.
> java.lang.RuntimeException:
> org.apache.iotdb.commons.exception.IoTDBException: get template info error.
> at
> org.apache.iotdb.db.metadata.template.ClusterTemplateManager.getTemplate(ClusterTemplateManager.java:173)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.executor.ClusterConfigTaskExecutor.showNodesInSchemaTemplate(ClusterConfigTaskExecutor.java:997)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.metadata.template.ShowNodesInSchemaTemplateTask.execute(ShowNodesInSchemaTemplateTask.java:56)
> at
> org.apache.iotdb.db.mpp.plan.execution.config.ConfigExecution.start(ConfigExecution.java:106)
> at
> org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:153)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:218)
> at
> org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:476)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3629)
> at
> org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3609)
> 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
>
[jira] [Created] (IOTDB-5548) [template]fail to drop template of `123`
changxue created IOTDB-5548:
---
Summary: [template]fail to drop template of `123`
Key: IOTDB-5548
URL: https://issues.apache.org/jira/browse/IOTDB-5548
Project: Apache IoTDB
Issue Type: Bug
Reporter: changxue
Assignee: liaolanyu
build: 1.1.0-SNAPSHOT master 1a69b40
reproduction:
run these commands in cli:
{code}
create schema template `123` aligned (lat FLOAT encoding=Gorilla, lon FLOAT
encoding=Gorilla);
show schema templates;
drop schema template `123`
{code}
{code}
IoTDB> show schema templates
++
|TemplateName|
++
| `123`|
++
Total line number = 1
It costs 0.121s
IoTDB> drop schema template `123`
Msg: 507: Template 123 does not exist
{code}
datanode log:
{code}
2023-02-17 10:06:40,203
[pool-25-IoTDB-ClientRPC-Processor-1$20230217_020640_00770_1] WARN
o.a.i.d.m.p.e.c.e.ClusterConfigTaskExecutor:1163 - Failed to execute drop
schema template 123 in config node, status is TSStatus(code:507,
message:Template 123 does not exist).
2023-02-17 10:06:40,203 [pool-21-IoTDB-MPPCoordinator-11] WARN
o.a.i.d.m.p.e.c.ConfigExecution:131 - Failures happened during running
ConfigExecution.
org.apache.iotdb.commons.exception.IoTDBException: Template 123 does not exist
at
org.apache.iotdb.db.mpp.plan.execution.config.executor.ClusterConfigTaskExecutor.dropSchemaTemplate(ClusterConfigTaskExecutor.java:1167)
at
org.apache.iotdb.db.mpp.plan.execution.config.metadata.template.DropSchemaTemplateTask.execute(DropSchemaTemplateTask.java:40)
at
org.apache.iotdb.db.mpp.plan.execution.config.ConfigExecution.start(ConfigExecution.java:106)
at
org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:161)
at
org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:218)
at
org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:476)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3629)
at
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3609)
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.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)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5545) Heterogeneous schema_engine_mode among DataNodes
[ https://issues.apache.org/jira/browse/IOTDB-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanze chen reassigned IOTDB-5545: - Assignee: Yukun Zhou (was: yanze chen) > Heterogeneous schema_engine_mode among DataNodes > > > Key: IOTDB-5545 > URL: https://issues.apache.org/jira/browse/IOTDB-5545 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: Yukun Zhou >Priority: Major > > > The snapshot file formats for SchemaRegion in Memory mode and Schema_File > mode are incompatible with each other. If some nodes of the cluster are in > Memory mode and some nodes are in Schema_File mode, errors may occur when > loading snapshots. > There are two kinds of solution: > # Add a DataNode registration check to ensure that the schema_engine_mode > configuration of all DataNodes is consistent. > # Ensure compatibility when SchemaRegion loading snapshot, support for > datanode heterogeneous configurations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] iotopo commented on pull request #75: Rel/0.13
iotopo commented on PR #75: URL: https://github.com/apache/iotdb-client-go/pull/75#issuecomment-1433966926 @fuliwen @HTHou 代码里 ConstructSession 没有提供集群支持吗？ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-5547) [ query ] executeStatement failed : Caused by: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException: null
刘珍 created IOTDB-5547: - Summary: [ query ] executeStatement failed : Caused by: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException: null Key: IOTDB-5547 URL: https://issues.apache.org/jira/browse/IOTDB-5547 Project: Apache IoTDB Issue Type: Bug Components: Core/Query, mpp-cluster Affects Versions: 1.1.0-SNAPSHOT Reporter: 刘珍 Assignee: Yuan Tian Attachments: iotdb_4350.conf master 0215_077704e Query execution occasionally fails ， select min_time(s_0),max_time(s_0),count(s_0) from root.** align by device （1000dev * 2000 ts)： 2023-02-16 17:59:07,908 [pool-25-IoTDB-ClientRPC-Processor-121] INFO o.a.i.d.q.c.SessionManager:116 - IoTDB: Login status: Login successfully. User : root, opens Session-304-root:192.168.10.72:54342 2023-02-16 17:59:07,982 [pool-25-IoTDB-ClientRPC-Processor-121] INFO o.a.i.d.s.t.i.ClientRPCServiceImpl:624 - IoTDB server version: 1.1.0-SNAPSHOT (Build: 077704e) 2023-02-16 17:59:09,829 [Query-Worker-Thread-40$20230216_095908_30548_3.9.0.1] INFO o.a.i.d.e.c.TimeSeriesMetadataCache:86 - TimeseriesMetadataCache size = 16476198218 2023-02-16 17:59:09,834 [Query-Worker-Thread-30$20230216_095908_30548_3.6.0.1] INFO o.a.i.d.e.c.BloomFilterCache:56 - BloomFilterCache size = 82380991 2023-02-16 17:59:10,061 [Query-Worker-Thread-2$20230216_095908_30548_3.27.0.1] INFO o.a.i.d.e.c.ChunkCache:67 - ChunkCache size = 8238099109 2023-02-16 17:59:13,827 [pool-25-IoTDB-ClientRPC-Processor-121] WARN o.a.i.d.u.ErrorHandlingUtils:89 - Status code: 301, Query Statement: "select min_time(s_0),max_time(s_0),count(s_0) from root.** align by device". executeStatement failed org.apache.iotdb.commons.exception.IoTDBException: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.dealWithException(QueryExecution.java:467) at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getResult(QueryExecution.java:450) at org.apache.iotdb.db.mpp.plan.execution.QueryExecution.getByteBufferBatchResult(QueryExecution.java:485) at org.apache.iotdb.db.utils.QueryDataSetUtils.convertQueryResultByFetchSize(QueryDataSetUtils.java:254) at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.lambda$static$0(ClientRPCServiceImpl.java:165) at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:239) at org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:476) at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3629) at org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3609) 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(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) Caused by: org.apache.iotdb.db.mpp.execution.fragment.FragmentInstanceFailureInfo$FailureException: null at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1043) at java.base/java.util.ArrayList$Itr.remove(ArrayList.java:1011) at org.apache.iotdb.db.mpp.execution.driver.DataDriver.addUsedFilesForQuery(DataDriver.java:168) at org.apache.iotdb.db.mpp.execution.driver.DataDriver.addUsedFilesForQuery(DataDriver.java:148) at org.apache.iotdb.db.mpp.execution.driver.DataDriver.initQueryDataSource(DataDriver.java:135) at org.apache.iotdb.db.mpp.execution.driver.DataDriver.initialize(DataDriver.java:101) at org.apache.iotdb.db.mpp.execution.driver.DataDriver.init(DataDriver.java:63) at org.apache.iotdb.db.mpp.execution.driver.Driver.lambda$processFor$1(Driver.java:139) at org.apache.iotdb.db.mpp.execution.driver.Driver.tryWithLock(Driver.java:299) at org.apache.iotdb.db.mpp.execution.driver.Driver.processFor(Driver.java:125) at org.apache.iotdb.db.mpp.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:69) at org.apache.iotdb.db.mpp.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73) 2023-02-16 17:59:13,827 [pool-25-IoTDB-ClientRPC-Processor-121$20230216_095908_30548_3] INFO o.a.i.d.m.p.Coordinator:221 - Cost: 5833 ms, sql is select
[GitHub] [iotdb-client-go] iotopo closed issue #74: 连续执行 2 次查询后报错
iotopo closed issue #74: 连续执行 2 次查询后报错 URL: https://github.com/apache/iotdb-client-go/issues/74 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-client-go] iotopo commented on issue #74: 连续执行 2 次查询后报错
iotopo commented on issue #74: URL: https://github.com/apache/iotdb-client-go/issues/74#issuecomment-1433951439 > #75 有开源贡献者正在贡献session pool 的相关代码，可以等待一下新版本发布。 好的，感谢回复 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-5546) Allow consumeAllOperator to run when only some of children is blocked
Alima777 created IOTDB-5546: --- Summary: Allow consumeAllOperator to run when only some of children is blocked Key: IOTDB-5546 URL: https://issues.apache.org/jira/browse/IOTDB-5546 Project: Apache IoTDB Issue Type: Improvement Reporter: Alima777 Assignee: Alima777 For example, TimeJoinOperator - [SeriesScanOperator, ExchangeOperator], TimeJoinOperator can't run until there is data ready in ExchangeOperator. But acutally, it can run SeriesScanOperator once, and store the result. When ExchangeOperator is ready, it can do the join logic without waiting SeriesScanOperator. Therefore, I suggest to allow consumeAllOperator to run when only some of children is blocked. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5545) DataNode registration check for schema_engine_mode
yanze chen created IOTDB-5545: - Summary: DataNode registration check for schema_engine_mode Key: IOTDB-5545 URL: https://issues.apache.org/jira/browse/IOTDB-5545 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen The snapshot file formats for SchemaRegion in Memory mode and Schema_File mode are incompatible with each other. If some nodes of the cluster are in Memory mode and some nodes are in Schema_File mode, errors may occur when loading snapshots. Therefore, it is necessary to add a DataNode registration check to ensure that the schema_engine_mode configuration of all DataNodes is consistent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] HTHou commented on issue #74: 连续执行 2 次查询后报错
HTHou commented on issue #74: URL: https://github.com/apache/iotdb-client-go/issues/74#issuecomment-1432849270 https://github.com/apache/iotdb-client-go/pull/75 有开源贡献者正在贡献session pool 的相关代码，可以等待一下新版本发布。 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-client-go] iotopo commented on issue #74: 连续执行 2 次查询后报错
iotopo commented on issue #74: URL: https://github.com/apache/iotdb-client-go/issues/74#issuecomment-1432844741 驱动包里没有考虑提供一个可以使用的 session pool 吗？需要业务侧自己实现一个是吧？ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-client-go] HTHou commented on issue #74: 连续执行 2 次查询后报错
HTHou commented on issue #74:
URL: https://github.com/apache/iotdb-client-go/issues/74#issuecomment-1432840371
> 我写了一个最小复现的代码，现在来看应该是 session 不支持并发。
>
> ```go
> func main() {
>session := client.NewSession({
>Host: "127.0.0.1",
>Port: "6667",
>UserName: "root",
>Password: "root",
>})
>
>if err := session.Open(false, 0); err != nil {
>panic(err)
>}
>
>timeout := int64(2)
>go func() {
>_, err := session.ExecuteQueryStatement("select last v1 as
value from root.ln.wf02.wt02", )
>if err != nil {
>panic(err)
>}
>}()
>
>go func() {
>_, err := session.ExecuteQueryStatement("select last hardware
as value from root.ln.wf02.wt02", )
>if err != nil {
>panic(err)
>}
>}()
>time.Sleep(time.Second * 200)
> }
> ```
是的 单个session不能并发使用，如果有并发，需要使用多个session。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [iotdb-client-go] fuliwen commented on pull request #75: Rel/0.13
fuliwen commented on PR #75: URL: https://github.com/apache/iotdb-client-go/pull/75#issuecomment-1432723753 jira: https://issues.apache.org/jira/browse/IOTDB-5503 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-client-go] fuliwen opened a new pull request, #75: Rel/0.13
fuliwen opened a new pull request, #75: URL: https://github.com/apache/iotdb-client-go/pull/75 added session pool and example -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-bin-resources] liuminghui233 merged pull request #52: SessionGroup concept in group by session
liuminghui233 merged PR #52: URL: https://github.com/apache/iotdb-bin-resources/pull/52 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
