Log Failed to lock all shards for index interrupted – How To Solve Related Issues


Log Failed to lock all shards for index interrupted – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to lock all shards for index interrupted ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, index, indices and shards.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}] failed to lock all shards for index – interrupted” classname is IndicesClusterStateService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             // lock is released so it's guaranteed to be deleted by the time we get the lock
                            indicesService.processPendingDeletes(index; indexSettings; new TimeValue(30; TimeUnit.MINUTES));
                        } catch (ShardLockObtainFailedException exc) {
                            logger.warn("[{}] failed to lock all shards for index - timed out after 30 seconds"; index);
                        } catch (InterruptedException e) {
                            logger.warn("[{}] failed to lock all shards for index - interrupted"; index);
                        }
                    }
                });
            }
        }




 

Optimize Elasticsearch Performance

Try The Tool