I can't reproduce this either. GridCacheWriteBehindStore flushes all the data immediately after stop process is initiated. Is it possible that it just takes more time to flush the whole queue? With bigger timeout it's possible that you collect more data.
It would be also great if you provide a small example (e.g., a GitHub project) that reproduces the problem. Someone will take a look. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-t-stop-Ignite-instance-using-Ignition-stopAll-or-Ignition-kill-until-writeBehindFlushFrequency-pd-tp4837p5090.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
