# Node seems to lock up randomly **URL:** \ **Category:** Elasticsearch\ **Created:** [December 7, 2016, 3:56pm UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323 "2016-12-07T15:56:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Chris\_Andreassen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_andreassen/32/13697_2.png) [@Chris\_Andreassen](https://discuss.elastic.co/u/Chris_Andreassen)\ **Post date:** [December 7, 2016, 3:56pm UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323/1 "2016-12-07T15:56:20Z")
I have two different 5 node ES clusters. Both are running on the same VMware cluster. Every now and again the health of the cluster will go to red or even yellow. When I look at marvel i'll see that one of the nodes is no longer part of the cluster. I'll log into the node and I can move around various directories just fine until I attempt to go into the directory we have ES installed in. For example if I attempt to just do an ls within /opt (which is where ES is installed) the system will lock up and I cannot do anything within /opt. I am able to go into say /var/log and look at various log files. I don't see anything related to why that part of the filesystem is not accessible. Once I reboot the system it comes back up just fine, ES, kibana and Marvel all come up and it becomes part of the cluster again. It will work for various amounts of time. Might be a week or day, It's even gone a couple of weeks without a problem. OEL 7 3.10.0-123.el7 OpenJDK 25.101-b13 JRE 1.8.0\_101-b13 ES 2.3.4 kibana 4.5.4 Each VM has 32gb of memory and 4 cpu's ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 8, 2016, 2:20am UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323/2 "2016-12-08T02:20:02Z")
> [@Chris\_Andreassen](#): > > I'll log into the node and I can move around various directories just fine until I attempt to go into the directory we have ES installed in. For example if I attempt to just do an ls within /opt (which is where ES is installed) the system will lock up and I cannot do anything within /opt. This sounds like a FS problem, are you using NFS mounted into the VM, or as underlying block storage that the hypervisor pulls in? ---
**Author:** ![Chris\_Andreassen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_andreassen/32/13697_2.png) [@Chris\_Andreassen](https://discuss.elastic.co/u/Chris_Andreassen)\ **Post date:** [December 8, 2016, 2:37am UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323/3 "2016-12-08T02:37:04Z")
The underlying storage is iscsi, all the elasticsearch stuff sits on the hard drive presented to the OS through vmware. I had a discussion with some of the folks on my team and we're talking about the use of xfs vs ext4. What is the recommended fs? We have another cluster in production that is using ext4 ours which is having the problems is using xfs. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 8, 2016, 2:49am UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323/4 "2016-12-08T02:49:52Z")
We don't really make recommendations there (other than stay away from NFS as a data mount the app uses directly). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 5, 2017, 2:49am UTC](https://discuss.elastic.co/t/node-seems-to-lock-up-randomly/68323/5 "2017-01-05T02:49:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.