Current license is non-compliant for – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when the Elasticsearch cluster is using features that are not included in the current license. This could be due to the expiration of a trial license or a downgrade from a higher level license. To resolve this issue, you can either disable the features that are not included in your current license or upgrade your license to a level that includes these features. Additionally, ensure that your license is not expired. If it is, you will need to renew it.

This guide will help you check for common problems that cause the log ” current license is non-compliant for [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, license.

Log Context

Log “current license is non-compliant for [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * feature accessible through {@link #EXPIRED_FEATURE_METADATA} in the
 * exception's rest header
 public static ElasticsearchSecurityException newComplianceException(String feature) {
 ElasticsearchSecurityException e = new ElasticsearchSecurityException("current license is non-compliant for [{}]";
 RestStatus.FORBIDDEN; feature);
 e.addMetadata(EXPIRED_FEATURE_METADATA; feature);
 return e;