Hi there, Where do I configure this ? I put the following line in the elasticsearch.yml but still couldn't start up the server. index.store.fs.lock: none
We are running version 1.2.1 on Centos 5 using Lustre file system and for certain reasons we need to turn off the support for native locking. When we use Solr it supports different lock types and 'Simple' works well for us. I also tried index.store.fs.lock: simple but no luck either. >From here https://github.com/elasticsearch/elasticsearch/commit/775339d78a55b84799b823e23bed38b8f10d794f I can see that Elasticsearch would support those too but just can't get that to work. Any help would be really appreciated! Regards, Patrick On Tuesday, December 13, 2011 11:49:24 AM UTC+13, kimchy wrote: > > Great, though its still strange why it would time out getting native lock > in this virtualized env... > > 2011/12/12 Björn Lilja <rundk...@gmail.com <javascript:>> > >> On the trunk there is a new setting availibe: index.store.fs.lock: >> none >> >> This solved things! Thanks kimchy! >> >> On Dec 12, 11:08 am, Björn Lilja <rundkvad...@gmail.com> wrote: >> > Hi >> > >> > Hi all. We are just getting started with elastic and it works great on >> > our local machines. However, when moving to our test and production >> > servers on OpenVZ we get a bunch of problems. The one we really can't >> > get our head around is when elastic suddenly fails to aquire new >> > locks. >> > >> > We are running Ubuntu 10.10 on a OpenVC virtual machine. We have 3GB >> > of memory availible and when starting elasticsearch it consumes about >> > 1,5 of those. >> > >> > This is our settings: >> > cluster.name: elasticsearch-kundotest >> > index.number_of_shards: 1 >> > index.number_of_replicas: 0 >> > bootstrap.mlockall: true >> > discovery.zen.ping.multicast.enabled: false >> > >> > When we build all our indexes we create about 600 indexes and adds in >> > total about 30 000 documents. Some indexes are big (3000+ documents) >> > and some are really small (2-3 documents). >> > >> > This is our ulimit conif: >> > root@testserver:/usr/sbin/elasticsearch# ulimit -a >> > core file size (blocks, -c) 0 >> > data seg size (kbytes, -d) unlimited >> > scheduling priority (-e) 20 >> > file size (blocks, -f) unlimited >> > pending signals (-i) 16382 >> > max locked memory (kbytes, -l) unlimited >> > max memory size (kbytes, -m) unlimited >> > open files (-n) 64000 >> > pipe size (512 bytes, -p) 8 >> > POSIX message queues (bytes, -q) 819200 >> > real-time priority (-r) 0 >> > stack size (kbytes, -s) 8192 >> > cpu time (seconds, -t) unlimited >> > max user processes (-u) unlimited >> > virtual memory (kbytes, -v) unlimited >> > file locks (-x) unlimited >> > >> > We use celery as a queue and pyes to interface elastic so there is >> > basically one connection created for every document indexed if I >> > understands things correctly... >> > >> > The problem we get after running the indexing process for a while is >> > this: >> > >> > [2011-12-12 10:38:37,173][INFO ][cluster.metadata ] [Aginar] >> > [orebro-sk] create_mapping [dialog] >> > [2011-12-12 10:38:38,152][WARN ][indices.cluster ] [Aginar] >> > [orebro-sk][0] failed to start shard >> > org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: >> > [orebro-sk][0] failed recovery >> > at org.elasticsearch.index.gateway.IndexShardGatewayService >> > $1.run(IndexShardGatewayService.java:229) >> > at >> > >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: >> > 1110) >> > at java.util.concurrent.ThreadPoolExecutor >> > $Worker.run(ThreadPoolExecutor.java:603) >> > at java.lang.Thread.run(Thread.java:636) >> > Caused by: >> > org.elasticsearch.index.engine.EngineCreationFailureException: [orebro- >> > sk][0] Failed to create engine >> > at >> > org.elasticsearch.index.engine.robin.RobinEngine.start(RobinEngine.java: >> > 249) >> > at >> > >> org.elasticsearch.index.shard.service.InternalIndexShard.start(InternalInde >> xShard.java: >> > 267) >> > at >> > >> org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalI >> ndexShardGateway.java: >> > 123) >> > at org.elasticsearch.index.gateway.IndexShardGatewayService >> > $1.run(IndexShardGatewayService.java:179) >> > ... 3 more >> > Caused by: org.apache.lucene.store.LockObtainFailedException: Lock >> > obtain timed out: NativeFSLock@/usr/sbin/elasticsearch/data/ >> > elasticsearch-kundotest/nodes/0/indices/orebro-sk/0/index/write.lock: >> > java.io.IOException: No locks available >> > at org.apache.lucene.store.Lock.obtain(Lock.java:84) >> > at >> org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1108) >> > at >> > >> org.elasticsearch.index.engine.robin.RobinEngine.createWriter(RobinEngine.j >> ava: >> > 1303) >> > at >> > org.elasticsearch.index.engine.robin.RobinEngine.start(RobinEngine.java: >> > 247) >> > ... 6 more >> > Caused by: java.io.IOException: No locks available >> > at sun.nio.ch.FileChannelImpl.lock0(Native Method) >> > at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:924) >> > at java.nio.channels.FileChannel.tryLock(FileChannel.java:978) >> > at >> > org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java: >> > 216) >> > at org.apache.lucene.store.Lock.obtain(Lock.java:95) >> > ... 9 more >> > [2011-12-12 10:38:38,156][WARN ][cluster.action.shard ] [Aginar] >> > sending failed shard for [orebro-sk][0], node[50DYl0MPTbOum-IFi8R-ug], >> > [P], s[INITIALIZING], reason [Failed to start shard, message >> > [IndexShardGatewayRecoveryException[[orebro-sk][0] failed recovery]; >> > nested: EngineCreationFailureException[[orebro-sk][0] Failed to create >> > engine]; nested: LockObtainFailedException[Lock obtain timed out: >> > NativeFSLock@/usr/sbin/elasticsearch/data/elasticsearch-kundotest/ >> > nodes/0/indices/orebro-sk/0/index/write.lock: java.io.IOException: No >> > locks available]; nested: IOException[No locks available]; ]] >> > [2011-12-12 10:38:38,156][WARN ][cluster.action.shard ] [Aginar] >> > received shard failed for [orebro-sk][0], node[50DYl0MPTbOum-IFi8R- >> > ug], [P], s[INITIALIZING], reason [Failed to start shard, message >> > [IndexShardGatewayRecoveryException[[orebro-sk][0] failed recovery]; >> > nested: EngineCreationFailureException[[orebro-sk][0] Failed to create >> > engine]; nested: LockObtainFailedException[Lock obtain timed out: >> > NativeFSLock@/usr/sbin/elasticsearch/data/elasticsearch-kundotest/ >> > nodes/0/indices/orebro-sk/0/index/write.lock: java.io.IOException: No >> > locks available]; nested: IOException[No locks available]; ]] >> > [2011-12-12 10:38:54,463][INFO ][node ] [Aginar] >> > {0.18.5}[31853]: stopping ... >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > OpenJDK 64-Bit Server VM warning: Attempt to allocate stack guard >> > pages failed. >> > >> > [1]+ Stopped ./bin/elasticsearch -f -Des.max-open- >> > files=true >> > >> > ANY ideas on what could be causing this? >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b400261a-6192-4ac8-a56a-93d8a210db0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
