Re: Could not lock IndexWriter isLocked [false]
Hi Alex, Thanks for your reply. ES instance running on a Linux machine and I have only one instance 1 shard 1 replica too. I think it is solved now by adding this line. index.store.fs.lock: none After I have added that parameter this problem no more occur. On Monday, June 16, 2014 2:42:18 PM UTC+3, Alexander Reelsen wrote: > > Hey, > > what elasticsearch version are you using? Judging from the directory I > dont think you are using NFS, right? Are you running multiple instances > locally? > Have you shutdown elasticsearch properly so that no other instance is > lingering around (you can use jps or or to check) > > > --Alex > > > On Mon, Jun 2, 2014 at 1:16 PM, Fatih Karatana > wrote: > >> I try to create an index in a couple of seconds and i got this: >> [2014-06-02 14:10:14,414][WARN ][index.engine.internal] [shardicaprio >> ] [myindex][0] Could not lock IndexWriter isLocked [false] >> >> >> And here is full stack trace: >> >> org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: >> NativeFSLock@/var/lib/elasticsearch/data/shardicaprio/nodes/0/indices/ >> myindex/0/index/write.lock >> at org.apache.lucene.store.Lock.obtain(Lock.java:84) >> at org.apache.lucene.index.IndexWriter.(IndexWriter.java: >> 702) >> at org.elasticsearch.index.engine.internal.InternalEngine. >> createWriter(InternalEngine.java:1388) >> at org.elasticsearch.index.engine.internal.InternalEngine.start( >> InternalEngine.java:256) >> at org.elasticsearch.index.shard.service.InternalIndexShard. >> postRecovery(InternalIndexShard.java:684) >> at org.elasticsearch.index.gateway.local.LocalIndexShardGateway. >> recover(LocalIndexShardGateway.java:158) >> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run >> (IndexShardGatewayService.java:189) >> at java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1145) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> [2014-06-02 14:10:14,533][WARN ][indices.cluster ] [shardicaprio >> ] [myindex][0] failed to start shard >> org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: [ >> myindex][0] failed recovery >> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run >> (IndexShardGatewayService.java:248) >> at java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1145) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: org.elasticsearch.index.engine.EngineCreationFailureException: >> [myindex][0] failed to create engine >> at org.elasticsearch.index.engine.internal.InternalEngine.start( >> InternalEngine.java:258) >> at org.elasticsearch.index.shard.service.InternalIndexShard. >> postRecovery(InternalIndexShard.java:684) >> at org.elasticsearch.index.gateway.local.LocalIndexShardGateway. >> recover(LocalIndexShardGateway.java:158) >> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run >> (IndexShardGatewayService.java:189) >> ... 3 more >> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock >> obtain timed out: NativeFSLock@/var/lib/elasticsearch/data/shardicaprio/ >> nodes/0/indices/myindex/0/index/write.lock >> at org.apache.lucene.store.Lock.obtain(Lock.java:84) >> at org.apache.lucene.index.IndexWriter.(IndexWriter.java: >> 702) >> at org.elasticsearch.index.engine.internal.InternalEngine. >> createWriter(InternalEngine.java:1388) >> at org.elasticsearch.index.engine.internal.InternalEngine.start( >> InternalEngine.java:256) >> ... 6 more >> [2014-06-02 14:10:14,536][WARN ][cluster.action.shard ] [shardicaprio >> ] [myindex][0] sending failed shard for [myindex][0], node[ >> kHOedr2wQpa3DSZj81ep_A], [P], s[INITIALIZING], indexUUID [29Uf2hH4S2- >> FJf1LnNrM0A], reason [Failed to start shard, message [ >> IndexShardGatewayRecoveryException[[myindex][0] failed recovery]; nested: >> EngineCreationFailureException[[myindex][0] failed to create engine]; >> nested: LockObtainFailedException[Lock obtain timed out: NativeFSLock@/ >> var/lib/elasticsearch/data/shardicaprio/nodes/0/indices/myindex/0/index/ >> write.lock]; ]] >> [2014-06-02 14:10:14,536][WARN ][cluster.action.shard ] [shardicaprio >&g
Date range query ignore month
Hi guys,
I've been using Elasticsearch as my data store and I got lots of documents
in it. My problem is, I figured it out that Elasticsearch does ignore month
field regarding mapping and I can not get real search response.
Here is what I have in my index and my query, please tell me if I'm wrong:
curl -XPUT 'http://localhost:9200/tt6/' -d '{}'
curl -XPUT 'http://localhost:9200/tt6/tweet/_mapping' -d '{"tweet" :
{"properties" : {"date" : {"type" : "date", "format": "-MM-DD HH:mm:ss"
'
curl -XPUT 'http://localhost:9200/tt6/tweet/1' -d '{"date": "2014-02-14
04:00:45"}'
curl -XGET 'http://localhost:9200/tt6/_search' -d '
{
"query": {
"bool": {
"must": [
{
"range": {
"tweet.date": {
"from": "2014-12-01 00:00:00",
"to": "2014-12-30 00:00:00"
}
}
}
],
"must_not": [],
"should": []
}
},
"from": 0,
"size": 10,
"sort": [],
"facets": {}
}'
And my response is
{
"took": 3,
"timed_out": false,
"_shards": {
"total": 5,
"successful": 5,
"failed": 0
},
"hits": {
"total": 1,
"max_score": 1,
"hits": [
{
"_index": "tt6",
"_type": "tweet",
"_id": "1",
"_score": 1,
"_source": {
"date": "2014-02-14 04:00:45",
"name": "test"
}
}
]
}
}
By given date range it must has no response beet 1st of December 2014 and
30th of December 2014, but it returns.
Any help will be appreciated.
Regards.
Fatih.
--
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/6ee655cf-9e77-439f-9aac-8255efafcb2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
