Skip to content

Failed to acquire lock #193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rb2k opened this issue May 26, 2010 · 2 comments
Closed

Failed to acquire lock #193

rb2k opened this issue May 26, 2010 · 2 comments
Labels
>enhancement v0.08.0

Comments

@rb2k
Copy link

rb2k commented May 26, 2010

Exception:
org.elasticsearch.index.shard.recovery.RecoveryFailedException: Index Shard [crawled][2]: Recovery failed from [ISAAC]
[...]
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/mnt/elasticsearch-0.7.1/work/elasticsearch/indices/cc4a7883-10b1-438d-a844-13930060205e/crawled/2/index/write.lock

happened while bulk-inserting data
@elasticsearch
Copy link

I think this might have to do with AWS. I will change things so there will be, by default, no locking since always a single shard is using the index.

@kimchy
Copy link
Member

kimchy commented May 26, 2010

Failed to acquire lock, closed by 26364af.

rmuir added a commit that referenced this issue Jun 5, 2015
@rmuir
Disable response metadata cache.
a36de1b 
This cache is only used for diagnostic purposes, but
can force objects from every response to the old generation.

Fixes #193
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
costin pushed a commit that referenced this issue Dec 6, 2022
@bpintea
Merge pull request #193 from elastic/main
1210ae5 
🤖 ESQL: Merge upstream
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.08.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rb2k @kimchy