Hi,
Are you seeing pool starvation messages? How long does it stay in this
state?
Are you not seeing any data saved, even when you close the jdbc
connection?
Are you able to reproduce this scenario? If so please describe steps/send
a reproducer and send full logs.
Data Streamer pool config:
https://apacheignite.readme.io/docs/thread-pools#data-streamer-pool
info on data streamer:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html
see:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteDataStreamer.html#perNodeBufferSize-int-
from the doc: https://apacheignite-sql.readme.io/docs/set#description
When streaming is enabled, JDBC/ODBC driver will pack your commands in
batches and send them to the server (Ignite cluster). On the server side,
the batch is converted into a stream of cache update commands which are
distributed asynchronously between server nodes.
In a JDBC SET STREAMING ON/OFF, this buffer is set internally to, and you
need to flush the data by closing the connection.
see : https://apacheignite-sql.readme.io/docs/set#example
Thanks, Alex
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
