The Elasticsearch trial ends when I add an ML node after 10 minutes

Elastic Stack Elasticsearch
1

I'm playing around a bit with Elastic Cloud on K8s, and I decided to activate the trial.

Ten minutes later, I decided to add a node with ML and Transform roles so I could run some jobs and do some testing.

It's a test environment, so it doesn't have a lot of resources to spare. That's why when I added the ML node, it started to slow down, and I shut down the machine to give it more RAM and vCPUs. When I turned it back on, the licence had reverted to basic and no longer allows me to use the ML node :frowning:

Can anyone help me?

2

Elasticsearch basic or licensed version doesn’t prevent adding ML nodes. But it restrict using the ML features with basic license. You can try the followings:

  1. Create a brand new cluster and use the 30 days trial.
  2. Send trial extension request - Self-managed Trial Extension Request | Elastic
3

Hi Musab,

I know it doesn't prevent adding new ML nodes, but the strange thing was that when I added it to the cluster, the licence was deleted xD

I'm going to try to request an extension of the trial, because I don't want to start over with the nodes, although I know that by making a backup I could restore everything, but I'm a bit short on time these weeks.

Thank you so much!

1 Like
4

How did you activate the trial?

You have to activate the trial via ECK, and not via Elasticsearch.

When an ES deployment is managed by ECK, the license is also managed by ECK so you need to do all license management in ECK or it will keep reverting your changes.

1 Like
5

Wow, that’s the problem! I tried to apply the trial via ES api /_license :_)

Thank you so much!

6

Hi @TimV !

I'm realizing that it hasn't been licensed properly. Look, I followed the steps on the Elastic website and created the corresponding secret to start the trial.

image
image540×343 7.38 KB

But ES endpoint:

{

"license": {

    "status": "active",

    "uid": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",

    "type": "basic",

    "issue_date": "2025-09-16T22:20:03.707Z",

    "issue_date_in_millis": 1758061203707,

    "max_nodes": 1000,

    "max_resource_units": **null**,

    "issued_to": "cluster-funcional",

    "issuer": "elasticsearch",

    "start_date_in_millis": -1

}

}

And the same for the security capabilities in the Kibana webpage…

I tried restarting the cluster, but nothing happened.

Any suggestion?