Custom metadata field does not contain a valid long Actual value – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch attempts to read a custom metadata field expecting a long integer, but the actual value is not a valid long. This could be due to incorrect data type or format. To resolve this issue, you can: 1) Check the data input and ensure it’s a valid long integer. 2) Modify the mapping of the index to correctly define the data type of the field. 3) Use a script or ingest pipeline to transform the data into the correct format before indexing.

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 ” Custom metadata field [{}] does not contain a valid long. Actual value: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, metadata, long.

Log Context

Log “Custom metadata field [{}] does not contain a valid long. Actual value: [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (customData.containsKey(INDEX_CREATION_DATE)) {
 try {
 } catch (NumberFormatException e) {
 throw new ElasticsearchException("Custom metadata field [{}] does not contain a valid long. Actual value: [{}]";
 if (customData.containsKey(PHASE_TIME)) {
 try {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?