Log no shard lock for pending delete – How To Solve Related Issues


Log no shard lock for pending delete – 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 ” no shard lock for pending delete ” 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: delete, indices and shard.

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 “{} no shard lock for pending delete” classname is IndicesService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                     iterator.remove();
                                } catch (IOException ex) {
                                    logger.debug(() -> new ParameterizedMessage("{} retry pending delete"; shardLock.getShardId()); ex);
                                }
                            } else {
                                logger.warn("{} no shard lock for pending delete"; delete.shardId);
                                iterator.remove();
                            }
                        }
                    }
                    if (remove.isEmpty() == false) {




 

Optimize Elasticsearch Performance

Try The Tool