Hello,
Could you please tell which version are you using and if possible, share
ignite/cache configuration, full log and some short reproducer to this
issue?
Best regards,
Anton
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for reply, but unfortunately, I could understand the details in the
link provided. Could you please brief about it. Whats the root cause.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
Seems to you have the issue related to
https://issues.apache.org/jira/browse/IGNITE-7865 that fixed in the 2.5
version.
As workaround you could change WALMode to LOG_ONLY or start ignite with the
jvm property -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true
Thanks,
Pavel
2018-05-10 9:50 GMT+03:
Hi,
I am getting this exception in logs but not sure on which cache it is
happening. Logs does not help me identifying the cache either.
Apologies to ask here without much details but just wondering if someone
know what are the chances to get this exception.
I have set of caches and CacheMode is
