You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Davalb <da...@forcam.com> on 2019/02/13 12:29:54 UTC
OverlappingFileLockException when restarting client node
When restarting a client node (Client Node 1) another node (Client Node 2) in
the cluster failed with a OverlappingFileLockException. After the error
occured Client Node 2 left the cluster.
Client Node 2 is running together with another client node (Client Node 3)
in the same Tomcat.
Client Node 1 logs:
Client Node 2 logs:
Unfortunatly its not logged which file is causing the problem but I guess
the error is caused by a concurrent file access of Node 2 and Node 3. Is
there a way to prevent this by configuration? If not I guess this is a bug
in ignite?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: OverlappingFileLockException when restarting client node
Posted by Davalb <da...@forcam.com>.
Since we did not set the workDir explicitly it seems like the temp dir of the
tomcat was used as workDir which was of course the same directory for the
nodes running in the same tomcat.
Thanks for your help.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: OverlappingFileLockException when restarting client node
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
Can you try specifying different workDir or IGNITE_HOME for different
client instances? From the exceptions it seems that workDir is exactly the
same?
Regards,
--
Ilya Kasnacheev
ср, 13 февр. 2019 г. в 17:37, Davalb <da...@forcam.com>:
> Hi,
>
> you can find the relevant log file entries related to ignite here:
>
> Client Node 1:
>
> https://gist.github.com/dalbrx-forcam/c18af85799b92c0fe0e9fe6ed4581bf1
>
> Client Node 2:
>
> https://gist.github.com/dalbrx-forcam/afdd6c10fb86b96c54b9b1f54d1475a4
>
> Server Node:
>
>
> https://gist.githubusercontent.com/dalbrx-forcam/4418fd1ae965f05adaa96f37f7c62d5e/raw/b3f3c83b5978ff8764a8b8eb8f2e1a6629a8a683/server-node.log
>
> Tell me if you need anything else.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: OverlappingFileLockException when restarting client node
Posted by Davalb <da...@forcam.com>.
Hi,
you can find the relevant log file entries related to ignite here:
Client Node 1:
https://gist.github.com/dalbrx-forcam/c18af85799b92c0fe0e9fe6ed4581bf1
Client Node 2:
https://gist.github.com/dalbrx-forcam/afdd6c10fb86b96c54b9b1f54d1475a4
Server Node:
https://gist.githubusercontent.com/dalbrx-forcam/4418fd1ae965f05adaa96f37f7c62d5e/raw/b3f3c83b5978ff8764a8b8eb8f2e1a6629a8a683/server-node.log
Tell me if you need anything else.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: OverlappingFileLockException when restarting client node
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
We will need more details. Can you provide full logs from affected nodes?
Regards,
--
Ilya Kasnacheev
ср, 13 февр. 2019 г. в 15:29, Davalb <da...@forcam.com>:
> When restarting a client node (Client Node 1) another node (Client Node 2)
> in
> the cluster failed with a OverlappingFileLockException. After the error
> occured Client Node 2 left the cluster.
>
> Client Node 2 is running together with another client node (Client Node 3)
> in the same Tomcat.
>
> Client Node 1 logs:
>
>
> Client Node 2 logs:
>
>
> Unfortunatly its not logged which file is causing the problem but I guess
> the error is caused by a concurrent file access of Node 2 and Node 3. Is
> there a way to prevent this by configuration? If not I guess this is a bug
> in ignite?
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>