How To Solve Issues Related to Log – Percolate original reduce error

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Prevent Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Percolate original reduce error” it’s important to understand common problems related to Elasticsearch concepts: percolate. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 How to Optimize elasticsearch percolator index Memory Performance 0.44 K 6

2All shards failed 65.07 K  28


Log Context

Log ”{} Percolate original reduce error” classname is TransportMultiPercolateAction.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                         // so expectedOperationsPerItem will not be decremented twice.
                        reduce(item.slot());
                    }
                }
            } catch (Throwable e) {
                logger.error("{} Percolate original reduce error"; e; shardId);
                finalListener.onFailure(e);
            }
        }

        
SuppressWarnings("unchecked")





About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster