[jira] [Created] (IOTDB-6156) Fixed TConfiguration invalidly in Thrift AsyncServer For IoTConsensus
Xinyu Tan created IOTDB-6156:
Summary: Fixed TConfiguration invalidly in Thrift AsyncServer For
IoTConsensus
Key: IOTDB-6156
URL: https://issues.apache.org/jira/browse/IOTDB-6156
Project: Apache IoTDB
Issue Type: Bug
Reporter: Xinyu Tan
Assignee: Xinyu Tan
In a user scenario, the machine configuration is as follows:
3c3d 3 replicas,
1 database
1 device
2 measurement
1 client
insertAlignTablet interface
batchSize 1000
time_partition_interval=314496000
The IoTConsensus data synchronization error occurs after writing to the cluster.
{code:java}
2023-09-14 12:11:50,888 [pool-19-IoTDB-IoTConsensusRPC-Processor-5] WARN
o.a.t.s.AbstractNonblockingServer$AsyncFrameBuffer:606 - Exception while
invoking!
org.apache.thrift.transport.TTransportException: MaxMessageSize reached
at
org.apache.thrift.transport.TEndpointTransport.countConsumedMessageBytes(TEndpointTransport.java:96)
at
org.apache.thrift.transport.TMemoryInputTransport.read(TMemoryInputTransport.java:97)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:109)
at
org.apache.iotdb.rpc.AutoScalingBufferReadTransport.fill(AutoScalingBufferReadTransport.java:38)
at
org.apache.iotdb.rpc.TElasticFramedTransport.readFrame(TElasticFramedTransport.java:128)
at
org.apache.iotdb.rpc.TElasticFramedTransport.read(TElasticFramedTransport.java:108)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:109)
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:463)
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:361)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:244)
at org.apache.thrift.TBaseAsyncProcessor.process(TBaseAsyncProcessor.java:52)
at
org.apache.thrift.server.AbstractNonblockingServer$AsyncFrameBuffer.invoke(AbstractNonblockingServer.java:603)
at org.apache.thrift.server.Invocation.run(Invocation.java:18)
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 is mainly due to the use of AsyncServer in IoTConsensus. At present, the
default maximum size of message is 100M instead of 512M, so it needs to be
updated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-6150) Remove datanode/system/compression_ratio
[ https://issues.apache.org/jira/browse/IOTDB-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-6150: --- Assignee: LiYuheng > Remove datanode/system/compression_ratio > > > Key: IOTDB-6150 > URL: https://issues.apache.org/jira/browse/IOTDB-6150 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: LiYuheng >Assignee: LiYuheng >Priority: Minor > > Now we check compression_ratio from metric, so this file > (datanode/system/compression_ratio) is not necessary now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6150) Remove datanode/system/compression_ratio
[ https://issues.apache.org/jira/browse/IOTDB-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-6150: --- Assignee: (was: LiYuheng) > Remove datanode/system/compression_ratio > > > Key: IOTDB-6150 > URL: https://issues.apache.org/jira/browse/IOTDB-6150 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: LiYuheng >Priority: Minor > > Now we check compression_ratio from metric, so this file > (datanode/system/compression_ratio) is not necessary now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6155) fix bugs of flink-sql-iotdb-connector for rc2
Xuan Ronaldo created IOTDB-6155: --- Summary: fix bugs of flink-sql-iotdb-connector for rc2 Key: IOTDB-6155 URL: https://issues.apache.org/jira/browse/IOTDB-6155 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Flink Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6154) Pipe: Hybrid mode switching timing issue
伊丹翔 created IOTDB-6154: -- Summary: Pipe: Hybrid mode switching timing issue Key: IOTDB-6154 URL: https://issues.apache.org/jira/browse/IOTDB-6154 Project: Apache IoTDB Issue Type: Improvement Reporter: 伊丹翔 Assignee: 伊丹翔 Pipe extractor in hybrid mode will first try to do log mode to extract data and then decide whether to use log or tsfile mode. However, when the number of leader data regions * Wal size on a DataNode is larger than maximum size of wal buffer (default 50G), it will cause OOM problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[BUILD-FAILURE]: Job 'IoTDB/IoTDB-pip-new/master [master] [347]'
BUILD-FAILURE: Job 'IoTDB/IoTDB-pip-new/master [master] [347]': Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-pip-new/job/master/347/";>IoTDB/IoTDB-pip-new/master [master] [347]"
[jira] [Created] (IOTDB-6153) Added multi-line support in cli
陈哲涵 created IOTDB-6153: -- Summary: Added multi-line support in cli Key: IOTDB-6153 URL: https://issues.apache.org/jira/browse/IOTDB-6153 Project: Apache IoTDB Issue Type: New Feature Reporter: 陈哲涵 Now the cli will cache the message if the message does not end with ";". -- This message was sent by Atlassian Jira (v8.20.10#820010)
