# \[QA\] Infinite loop when catching failure due to file path error **URL:** \ **Category:** Elasticsearch\ **Created:** [May 25, 2011, 3:42pm UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475 "2011-05-25T15:42:50Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Pascal\_P\_Pochet](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pascal\_P\_Pochet](https://discuss.elastic.co/u/Pascal_P_Pochet)\ **Post date:** [May 25, 2011, 3:42pm UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/1 "2011-05-25T15:42:50Z")
When using Java API and starting an embedded server, we accidentally discovered this behavior : If for any reason you have an error in the path defined by gateway.fs.location Your application will of course fail if the path is unaccessible but also will be stuck in an infinite loop logging tons of: Error injecting constructor, java.io.IOException: Failed to obtain node lock at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:47) while locating org.elasticsearch.env.NodeEnvironment for parameter 6 at org.elasticsearch.indices.store.TransportNodesListShardStoreMetaData.(TransportNodesListShardStoreMetaData.java:72) while locating org.elasticsearch.indices.store.TransportNodesListShardStoreMetaData for parameter 2 at org.elasticsearch.gateway.blobstore.BlobReuseExistingNodeAllocation.(BlobReuseExistingNodeAllocation.java:68) while locating org.elasticsearch.gateway.blobstore.BlobReuseExistingNodeAllocation while locating org.elasticsearch.cluster.routing.allocation.NodeAllocation annotated with @org.elasticsearch.common.inject.multibindings.Element(setName=,uniqueId=9) at org.elasticsearch.cluster.routing.allocation.ShardAllocationModule.configure(ShardAllocationModule.java:46) while locating java.util.Set\ for parameter 1 at org.elasticsearch.cluster.routing.allocation.NodeAllocations.(NodeAllocations.java:52) while locating org.elasticsearch.cluster.routing.allocation.NodeAllocations for parameter 1 at org.elasticsearch.cluster.routing.allocation.ShardsAllocation.(ShardsAllocation.java:53) while locating org.elasticsearch.cluster.routing.allocation.ShardsAllocation for parameter 3 at org.elasticsearch.cluster.action.shard.ShardStateAction.(ShardStateAction.java:64) while locating org.elasticsearch.cluster.action.shard.ShardStateAction for parameter 5 at org.elasticsearch.action.deletebyquery.TransportShardDeleteByQueryAction.(TransportShardDeleteByQueryAction.java:44) while locating org.elasticsearch.action.deletebyquery.TransportShardDeleteByQueryAction for parameter 4 at org.elasticsearch.action.deletebyquery.TransportIndexDeleteByQueryAction.(TransportIndexDeleteByQueryAction.java:41) while locating org.elasticsearch.action.deletebyquery.TransportIndexDeleteByQueryAction for parameter 4 at org.elasticsearch.action.deletebyquery.TransportDeleteByQueryAction.(TransportDeleteByQueryAction.java:41) while locating org.elasticsearch.action.deletebyquery.TransportDeleteByQueryAction for parameter 5 at org.elasticsearch.action.admin.indices.mapping.delete.TransportDeleteMappingAction.(TransportDeleteMappingAction.java:62) while locating org.elasticsearch.action.admin.indices.mapping.delete.TransportDeleteMappingAction for parameter 5 at org.elasticsearch.action.admin.indices.delete.TransportDeleteIndexAction.(TransportDeleteIndexAction.java:57) while locating org.elasticsearch.action.admin.indices.delete.TransportDeleteIndexAction for parameter 4 at org.elasticsearch.client.node.NodeIndicesAdminClient.(NodeIndicesAdminClient.java:129) while locating org.elasticsearch.client.node.NodeIndicesAdminClient for parameter 2 at org.elasticsearch.client.node.NodeAdminClient.(NodeAdminClient.java:39) Not catastrophic in itself since the file path error should be cleaned-up anyway to make the app working, but probably interesting to check the logic leading to this kind of infinite "catch/try again" loop. ---
**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:** [May 26, 2011, 11:02am UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/2 "2011-05-26T11:02:39Z")
There isn't really an infinite loop, it just tries 50 times to obtain a lock ... . The user experience is annoying though, need to think of how to improve it... On Wednesday, May 25, 2011 at 6:42 PM, Pascal Pochet wrote: > When using Java API and starting an embedded server, > we accidentally discovered this behavior : > > If for any reason you have an error in the path defined by > > gateway.fs.location > > Your application will of course fail if the path is unaccessible but also will be stuck in an infinite loop logging tons of: > > Error injecting constructor, java.io.IOException: Failed to obtain node lock > at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:47) > while locating org.elasticsearch.env.NodeEnvironment > for parameter 6 at org.elasticsearch.indices.store.TransportNodesListShardStoreMetaData.(TransportNodesListShardStoreMetaData.java:72) > while locating org.elasticsearch.indices.store.TransportNodesListShardStoreMetaData > for parameter 2 at org.elasticsearch.gateway.blobstore.BlobReuseExistingNodeAllocation.(BlobReuseExistingNodeAllocation.java:68) > while locating org.elasticsearch.gateway.blobstore.BlobReuseExistingNodeAllocation > while locating org.elasticsearch.cluster.routing.allocation.NodeAllocation annotated with @org.elasticsearch.common.inject.multibindings.Element(setName=,uniqueId=9) > at org.elasticsearch.cluster.routing.allocation.ShardAllocationModule.configure(ShardAllocationModule.java:46) > while locating java.util.Set\ > for parameter 1 at org.elasticsearch.cluster.routing.allocation.NodeAllocations.(NodeAllocations.java:52) > while locating org.elasticsearch.cluster.routing.allocation.NodeAllocations > for parameter 1 at org.elasticsearch.cluster.routing.allocation.ShardsAllocation.(ShardsAllocation.java:53) > while locating org.elasticsearch.cluster.routing.allocation.ShardsAllocation > for parameter 3 at org.elasticsearch.cluster.action.shard.ShardStateAction.(ShardStateAction.java:64) > while locating org.elasticsearch.cluster.action.shard.ShardStateAction > for parameter 5 at org.elasticsearch.action.deletebyquery.TransportShardDeleteByQueryAction.(TransportShardDeleteByQueryAction.java:44) > while locating org.elasticsearch.action.deletebyquery.TransportShardDeleteByQueryAction > for parameter 4 at org.elasticsearch.action.deletebyquery.TransportIndexDeleteByQueryAction.(TransportIndexDeleteByQueryAction.java:41) > while locating org.elasticsearch.action.deletebyquery.TransportIndexDeleteByQueryAction > for parameter 4 at org.elasticsearch.action.deletebyquery.TransportDeleteByQueryAction.(TransportDeleteByQueryAction.java:41) > while locating org.elasticsearch.action.deletebyquery.TransportDeleteByQueryAction > for parameter 5 at org.elasticsearch.action.admin.indices.mapping.delete.TransportDeleteMappingAction.(TransportDeleteMappingAction.java:62) > while locating org.elasticsearch.action.admin.indices.mapping.delete.TransportDeleteMappingAction > for parameter 5 at org.elasticsearch.action.admin.indices.delete.TransportDeleteIndexAction.(TransportDeleteIndexAction.java:57) > while locating org.elasticsearch.action.admin.indices.delete.TransportDeleteIndexAction > for parameter 4 at org.elasticsearch.client.node.NodeIndicesAdminClient.(NodeIndicesAdminClient.java:129) > while locating org.elasticsearch.client.node.NodeIndicesAdminClient > for parameter 2 at org.elasticsearch.client.node.NodeAdminClient.(NodeAdminClient.java:39) > > Not catastrophic in itself since the file path error should be cleaned-up anyway to make the app working, > but probably interesting to check the logic leading to this kind of infinite "catch/try again" loop. ---
**Author:** ![Pascal\_P\_Pochet](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pascal\_P\_Pochet](https://discuss.elastic.co/u/Pascal_P_Pochet)\ **Post date:** [May 26, 2011, 3:18pm UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/3 "2011-05-26T15:18:40Z")
50 ? FYI, I stopped it with counter already \> 300… so maybe more than one aspect to check here. (And sorry I forgot to specify: ES version 0.16.1) On 26 mai, 13:02, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > There isn't really an infinite loop, it just tries 50 times to obtain a lock ... . The user experience is annoying though, need to think of how to improve it... ---
**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:** [May 26, 2011, 8:59pm UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/4 "2011-05-26T20:59:04Z")
Which counter? On Thursday, May 26, 2011 at 6:18 PM, P3 wrote: > 50 ? > FYI, I stopped it with counter already \> 300… > so maybe more than one aspect to check here. > > (And sorry I forgot to specify: ES version 0.16.1) > > On 26 mai, 13:02, Shay Banon \<[shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) ([http://elasticsearch.com](http://elasticsearch.com))\> wrote: > > > There isn't really an infinite loop, it just tries 50 times to obtain a lock ... . The user experience is annoying though, need to think of how to improve it... ---
**Author:** ![Pascal\_P\_Pochet](https://avatars.discourse-cdn.com/v4/letter/p/3da27b/32.png) [@Pascal\_P\_Pochet](https://discuss.elastic.co/u/Pascal_P_Pochet)\ **Post date:** [May 28, 2011, 7:00pm UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/5 "2011-05-28T19:00:39Z")
the one in the log prefixing the "Error injecting constructor" line: 1. Error injecting constructor, java.io.IOException: Failed to obtain node lock On 26 mai, 22:59, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Which counter? > > On Thursday, May 26, 2011 at 6:18 PM, P3 wrote: > > > 50 ? > > FYI, I stopped it with counter already \> 300… > > so maybe more than one aspect to check here. > > > (And sorry I forgot to specify: ES version 0.16.1) > > > On 26 mai, 13:02, Shay Banon \<[shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) ([http://elasticsearch.com](http://elasticsearch.com))\> wrote: > > > > > There isn't really an infinite loop, it just tries 50 times to obtain a lock ... . The user experience is annoying though, need to think of how to improve it... ---
**Author:** ![fashionalwallet](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@fashionalwallet](https://discuss.elastic.co/u/fashionalwallet)\ **Post date:** [June 10, 2011, 3:43am UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/6 "2011-06-10T03:43:08Z")
- deleted - ---
**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, 4:04am UTC](https://discuss.elastic.co/t/qa-infinite-loop-when-catching-failure-due-to-file-path-error/4475/7 "2017-07-06T04:04:00Z")