Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when the function score query in OpenSearch returns an invalid score for a document. This could be due to incorrect query syntax, a bug in the scoring function, or an issue with the document data. To resolve this, you can first check the query syntax and ensure it’s correct. If the syntax is correct, try to debug the scoring function to identify any potential issues. Lastly, verify the document data for any inconsistencies or errors that might be causing the function score query to return an invalid score.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” function score query returned an invalid score: ” + finalScore + ” for doc: ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: query, lucene, search.
Overview
Lucene or Apache Lucene is an open-source Java library used as a search engine. OpenSearch is built on top of Lucene.
OpenSearch converts Lucene into a distributed system/search engine for scaling horizontally. OpenSearch also provides other features like thread-pool, queues, node/cluster monitoring API, data monitoring API, Cluster management, etc. In short, OpenSearch extends Lucene and provides additional features beyond it.
OpenSearch hosts data on data nodes. Each data node hosts one or more indices, and each index is divided into shards with each shard holding part of the index’s data. Each shard created in OpenSearch is a separate Lucene instance or process.
Notes and good things to know
When an index is created in OpenSearch, it is divided into one or more primary shards for scaling the data and splitting it into multiple nodes/instances.
- As each shard is a separate instance of Lucene, creating too many shards will consume unnecessary resources and damage performance.
It takes proper planning to decide the number of primary shards for your index, taking into account the index size, max growth, and the number of data nodes.
- Previous versions of OpenSearch defaulted to creating five shards per index. Starting with 7.0.0, the default is now one shard per index.
Quick links
Overview
Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.
Examples
When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.
GET my_documents/_search
A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.
{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}Notes and good things to know
- Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
- There are two phases of search: the query phase and the fetch phase.
- In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list.
- In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
- A coordinating node needs enough memory and CPU in order to handle the fetch phase.
Log Context
Log “function score query returned an invalid score: ” + finalScore + ” for doc: ” class name is FunctionScoreQuery.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :
if (finalScore < 0f || Float.isNaN(finalScore)) {
/*
These scores are invalid for score based {@link org.apache.lucene.search.TopDocsCollector}s.
See {@link org.apache.lucene.search.TopScoreDocCollector} for details.
*/
throw new OpenSearchException("function score query returned an invalid score: " + finalScore + " for doc: " + docId);
}
return finalScore;
} protected double computeScore(int docId; float subQueryScore) throws IOException {
