Re: Can't stop Ignite instance using Ignition.stopAll() or Ignition.kill() until writeBehindFlushFrequency passed

[vkulichenko]

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.

Re: Can't stop Ignite instance using Ignition.stopAll() or Ignition.kill() until writeBehindFlushFrequency passed

[vkulichenko]

What is 'cache.stats.write.behind.flushFrequency.ms' system property? This
property is not defined in Ignite, do you have your own logic that uses it?

-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-tp4837p5052.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can't stop Ignite instance using Ignition.stopAll() or Ignition.kill() until writeBehindFlushFrequency passed

[zshamrock]

 

And then it is hanging for about 5 minutes after each IT case.
Does the picture above help somehow?

How I can do a thread dump? I've tried to use jstack, although could not
find anything meaningful in the report it has produced.



--
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-tp4837p4976.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can't stop Ignite instance using Ignition.stopAll() or Ignition.kill() until writeBehindFlushFrequency passed

[vdpyatkov]

Hello,
I can not reproduce the issue.
In my test case all data entries save immediately after call
Ignition.stopAll(true).
If you had have example, which demonstrate the behavior, can you please
provide source code?



--
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-tp4837p4889.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.