# NFS Gateway errors

**URL:** <https://discuss.elastic.co/t/nfs-gateway-errors/5118>\
**Category:** Elasticsearch\
**Created:** [August 10, 2011, 9:27pm UTC](https://discuss.elastic.co/t/nfs-gateway-errors/5118 "2011-08-10T21:27:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christopher\_Burkey\_2](https://avatars.discourse-cdn.com/v4/letter/c/ad7895/32.png) [@Christopher\_Burkey\_2](https://discuss.elastic.co/u/Christopher_Burkey_2)\
**Post date:** [August 10, 2011, 9:27pm UTC](https://discuss.elastic.co/t/nfs-gateway-errors/5118/1 "2011-08-10T21:27:11Z")

</div>

Hello,

We are deploying ElasticSearch for an exciting project at a  
University. It has gone well with just a couple of errors.

One of the errors has to do with the gateway that is stored on a an  
NFS file server.

[WARN] [Professor Power] [system][0] failed to obtain snapshot lock,  
ignoring snapshot  
org.elasticsearch.ElasticSearchIllegalStateException: failed to obtain  
snapshot lock [NativeFSLock@/export/home/apps/hbs/local/localhost/WEB-  
INF/data/elastic/gateway/entermediaprod/indices/system/0/  
snapshot.lock] at  
org.elasticsearch.index.gateway.fs.FsIndexShardGateway.obtainSnapshotLock(FsIndexShardGateway.java:  
65)  
at  
org.elasticsearch.index.gateway.IndexShardGatewayService.snapshot(IndexShardGatewayService.java:  
258)  
at org.elasticsearch.index.gateway.IndexShardGatewayService  
$SnapshotRunnable.run(IndexShardGatewayService.java:365)  
at java.util.concurrent.ThreadPoolExecutor  
$Worker.runTask(ThreadPoolExecutor.java:886)  
at java.util.concurrent.ThreadPoolExecutor  
$Worker.run(ThreadPoolExecutor.java:908)  
at java.lang.Thread.run(Thread.java:662)

---

<div class="post-metadata">

**Author:** ![Christopher\_Burkey\_3](https://avatars.discourse-cdn.com/v4/letter/c/edb3f5/32.png) [@Christopher\_Burkey\_3](https://discuss.elastic.co/u/Christopher_Burkey_3)\
**Post date:** [August 10, 2011, 11:11pm UTC](https://discuss.elastic.co/t/nfs-gateway-errors/5118/2 "2011-08-10T23:11:20Z")

</div>

Looks like there is a possible solution:

gateway.fs.snapshot\_lock = false

Now we will just need to keep an eye out for split brain condition.

[http://elasticsearch-users.115913.n3.nabble.com/Ensuring-Gateway-integrity-td1849804.html](http://elasticsearch-users.115913.n3.nabble.com/Ensuring-Gateway-integrity-td1849804.html)

On Wed, Aug 10, 2011 at 5:27 PM, Christopher Burkey  
[cburkey@entermediasoftware.com](mailto:cburkey@entermediasoftware.com) wrote:

> Hello,
> 
> We are deploying Elasticsearch for an exciting project at a  
> University. It has gone well with just a couple of errors.
> 
> One of the errors has to do with the gateway that is stored on a an  
> NFS file server.
> 
> [WARN] [Professor Power] [system][0] failed to obtain snapshot lock,  
> ignoring snapshot  
> org.elasticsearch.ElasticSearchIllegalStateException: failed to obtain  
> snapshot lock [NativeFSLock@/export/home/apps/hbs/local/localhost/WEB-  
> INF/data/elastic/gateway/entermediaprod/indices/system/0/  
> snapshot.lock] at  
> org.elasticsearch.index.gateway.fs.FsIndexShardGateway.obtainSnapshotLock(FsIndexShardGateway.java:  
> 65)  
> at  
> org.elasticsearch.index.gateway.IndexShardGatewayService.snapshot(IndexShardGatewayService.java:  
> 258)  
> at org.elasticsearch.index.gateway.IndexShardGatewayService  
> $SnapshotRunnable.run(IndexShardGatewayService.java:365)  
> at java.util.concurrent.ThreadPoolExecutor  
> $Worker.runTask(ThreadPoolExecutor.java:886)  
> at java.util.concurrent.ThreadPoolExecutor  
> $Worker.run(ThreadPoolExecutor.java:908)  
> at java.lang.Thread.run(Thread.java:662)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 11, 2011, 9:20am UTC](https://discuss.elastic.co/t/nfs-gateway-errors/5118/3 "2011-08-11T09:20:57Z")

</div>

Why are you using NFS gateway? I recommend using the (default) local  
gateway.

On Thu, Aug 11, 2011 at 2:11 AM, Christopher Burkey [cburkey@openedit.org](mailto:cburkey@openedit.org)wrote:

> Looks like there is a possible solution:
> 
> gateway.fs.snapshot\_lock = false
> 
> Now we will just need to keep an eye out for split brain condition.
> 
> [http://elasticsearch-users.115913.n3.nabble.com/Ensuring-Gateway-integrity-td1849804.html](http://elasticsearch-users.115913.n3.nabble.com/Ensuring-Gateway-integrity-td1849804.html)
> 
> On Wed, Aug 10, 2011 at 5:27 PM, Christopher Burkey  
> [cburkey@entermediasoftware.com](mailto:cburkey@entermediasoftware.com) wrote:
> 
> > Hello,
> > 
> > We are deploying Elasticsearch for an exciting project at a  
> > University. It has gone well with just a couple of errors.
> > 
> > One of the errors has to do with the gateway that is stored on a an  
> > NFS file server.
> > 
> > [WARN] [Professor Power] [system][0] failed to obtain snapshot lock,  
> > ignoring snapshot  
> > org.elasticsearch.ElasticSearchIllegalStateException: failed to obtain  
> > snapshot lock [NativeFSLock@/export/home/apps/hbs/local/localhost/WEB-  
> > INF/data/elastic/gateway/entermediaprod/indices/system/0/  
> > snapshot.lock] at
> 
> org.elasticsearch.index.gateway.fs.FsIndexShardGateway.obtainSnapshotLock(FsIndexShardGateway.java:
> 
> > 1. at
> 
> org.elasticsearch.index.gateway.IndexShardGatewayService.snapshot(IndexShardGatewayService.java:
> 
> > 1. at org.elasticsearch.index.gateway.IndexShardGatewayService  
> > $SnapshotRunnable.run(IndexShardGatewayService.java:365)  
> > at java.util.concurrent.ThreadPoolExecutor  
> > $Worker.runTask(ThreadPoolExecutor.java:886)  
> > at java.util.concurrent.ThreadPoolExecutor  
> > $Worker.run(ThreadPoolExecutor.java:908)  
> > at java.lang.Thread.run(Thread.java:662)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:57am UTC](https://discuss.elastic.co/t/nfs-gateway-errors/5118/4 "2017-07-06T03:57:28Z")

</div>

Closed on July 6, 2017, 3:57am UTC


