[IOTDB-1609] Print the actual size of plan when it exceeds the wal_buffer_size

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Core/Engine
• Labels: easy-fix pull-request-available
• Sprint: 2021-10-Tian
• Assignee: yanze chen
• Reporter: Jialin Qiao
• Created: 02/Sep/21 11:08
• Updated: 03/Nov/21 01:18
• Resolved: 03/Nov/21 01:18

Description

When a plan can not fit into the wal buffer, we throw an exception. However, users do not know how to set the wal_buffer_size.

 

client： 

 

server：

Caused by: java.io.IOException: Log cannot fit into the buffer, please increase wal_buffer_sizeCaused by: java.io.IOException: Log cannot fit into the buffer, please increase wal_buffer_size at org.apache.iotdb.db.writelog.node.ExclusiveWriteLogNode.write(ExclusiveWriteLogNode.java:116) at org.apache.iotdb.db.engine.storagegroup.TsFileProcessor.insert(TsFileProcessor.java:197) ... 16 common frames omitted

Caused by: java.nio.BufferOverflowException: null at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:363) at java.nio.ByteBuffer.put(ByteBuffer.java:859) at org.apache.iotdb.tsfile.utils.ReadWriteIOUtils.write(ReadWriteIOUtils.java:232) at org.apache.iotdb.db.qp.physical.crud.InsertRowPlan.putValues(InsertRowPlan.java:391) at org.apache.iotdb.db.qp.physical.crud.InsertRowPlan.serializeMeasurementsAndValues(InsertRowPlan.java:461) at org.apache.iotdb.db.qp.physical.crud.InsertRowPlan.subSerialize(InsertRowPlan.java:447) at org.apache.iotdb.db.qp.physical.crud.InsertRowPlan.serialize(InsertRowPlan.java:441) at org.apache.iotdb.db.writelog.node.ExclusiveWriteLogNode.putLog(ExclusiveWriteLogNode.java:130) at org.apache.iotdb.db.writelog.node.ExclusiveWriteLogNode.write(ExclusiveWriteLogNode.java:111) ... 17 common frames omitted

 

Issue Links

• links to: GitHub Pull Request #4279