; org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStra
> tegy.log(AwaitCompletionReliabilityStrategy.java:63)
> [log4j-core-2.5.jar:2.5]
> at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:
> 147)
> [log4j-core-2.5.jar:2.5]
> at
> org.apache.lo
ufferedOutputStream.java:82)
~[?:1.8.0_66]
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
~[?:1.8.0_66]
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:156)
~[log4j-core-2.5.jar:2.5]
... 22 more
--
View th
Hi,
If Ignite could not write to home directory, it will got some side effect.
Could you please provide thread dump from this server node?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Home-Directory-tp12271p12303.html
Sent from the Apache Ignite Users
We recently ran into a situation where the directory we allocate log files to
filled up to our limit and could not be written to. We had the Ignite home
directory configured to write to this location. When examining the contents
of this directory we see a lock file along with shared memory files
