Briefly, this error occurs when there is an attempt to update the existing Elasticsearch license to a new version. This could be due to an expired license, a version mismatch, or an incorrect license type. To resolve this issue, you can try the following: 1) Verify the license type and ensure it matches with your Elasticsearch version. 2) Check the license expiration date and renew it if necessary. 3) If the problem persists, consider reinstalling Elasticsearch and applying the new license.
This guide will help you check for common problems that cause the log ” Updating existing license to the new version.\n\nOld license:\n {}\n\n New license:\n{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: license, plugin, version.
Overview
A version corresponds to the Elasticsearch built-in tracking system that tracks the changes in each document’s update. When a document is indexed for the first time, it is assigned a version 1 using _version key. When the same document gets a subsequent update, the _version is incremented by 1 with every index, update or delete API call.
What it is used for
A version is used to handle the concurrency issues in Elasticsearch which come into play during simultaneous accessing of an index by multiple users. Elasticsearch handles this issue with an optimistic locking concept using the _version parameter to avoid letting multiple users edit the same document at the same time and protects users from generating incorrect data.
Notes
You cannot see the history of the document using _version. That means Elasticsearch does not use _version to keep a track of original changes that had been performed on the document. For example, if a document has been updated 10 times, it’s _version would be marked by Elasticsearch as 11, but you cannot go back and see what version 5 of the document looked like. This has to be implemented independently.
Common problems
If optimistic locking is not implemented while making updates to a document, Elasticsearch may return a conflict error with the 409 status code, which means that multiple users are trying to update the same version of the document at the same time.
POST /ratings/123?version=50
{
"name": "Joker",
"rating": 50
}Log Context
Log “Updating existing license to the new version.\n\nOld license:\n {}\n\n New license:\n{}” classname is StartupSelfGeneratedLicenseTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
.expiryDate(expiryDate);
License selfGeneratedLicense = SelfGeneratedLicense.create(specBuilder; currentState.nodes());
Version trialVersion = currentLicenseMetadata.getMostRecentTrialVersion();
LicensesMetadata newLicenseMetadata = new LicensesMetadata(selfGeneratedLicense; trialVersion);
mdBuilder.putCustom(LicensesMetadata.TYPE; newLicenseMetadata);
logger.info("Updating existing license to the new version.\n\nOld license:\n {}\n\n New license:\n{}";
license; newLicenseMetadata.getLicense());
return ClusterState.builder(currentState).metadata(mdBuilder).build();
}
@Override
[ratemypost]
