write rejected

version 1.2.0

Write rejected when insert data via java interface:
`spark.scheduler.ResultTask.runTask(ResultTask.scala:90) spark.scheduler.Task.run(Task.scala:131)
spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506) spark.util.Utils$.tryWithSafeFinally(Utils.scala:1491)
spark.executor.Executor$TaskRunner.run(Executor.scala:509)
concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) Thread.run(Thread.java:750)
.iotdb.rpc.StatementExecutionException: 606: The write is rejected because the wal directory size has reached the thresholold 53687091200 bytes. You may need to adjust the flush policy of the storage engine or the IoTConsen:
iotdb.session.Session.insertByGroup(Session.java:3254)
iotdb.session.Session.insertRecordsWithLeaderCache(Session.java:2178) iotdb.session.Session.insertAlignedRecords(Session.java:1671)
seatunnel.connectors.seatunnel.iotdb.sink.IoTDBSinkClient.insertAlignedRecords(IoTDBSinkClient.java:217).seatunnel.connectors.seatunnel.iotdb.sink.IoTDBSinkClient.flush(IoTDBSinkClient.java:160)`

Change which parameter can avoid this?

Start with the WAL-threshold exception in the reported write path, following Session.insertAlignedRecords and the seatunnel IoTDBSinkClient files named in the trace. Identify which configuration controls the 53687091200-byte WAL limit and how it relates to the flush policy; done means Java-interface inserts no longer fail with the WAL-size rejection.

Written by the indexing model from the issue text.