Rebuilding ROR indices prior to upgrading to Elastic V8

1

Hi,

We want to upgrade to Elastic V8 but we still have readonlyrest indices originating of pre-V7 versions of Elastic and the ROR plugin.

What’s the best practice to rebuild those with Elastic V7 prior to upgrading to Elastic V8?

Thanks & regards,
Arjen

2

Hello @abuising!

This is a bit of a pain, but what I’d try to do is:

  • get a list of kibana indices you use for tenancies
  • install the latest version of Kibana 7.x (8.x has removed the kibana.index setting)
  • for each kibana index, set kibana.index: <the-kibana-index> in kibana.yml
  • start Kibana for some seconds, until it does the auto migration
3

Hi Simone,

Thank you!
That’s what we already do for every tenancy index with every new installation of Kibana!

So those are probably recent enough then.
How should we proceed in Elastic V8 then when this setting is not available anymore?

And the .readonlyrest index is still the original one.
How can we rebuild that one?

Thanks & regards,
Arjen

4

the .readonlyrest index needs to be recreated? I was not aware, how did you discover this necessary?

Moving forward we will need to re-enable main kibana index changing via the kibana patcher utility ror-tools.js. Good point!

1 Like
5

Just for clarification, are you having issues with reusing v7.x kibana indices in v8.x kibana right now?

6

Hi Simone,

We are planning to upgrade to ELK V8 and we are making an inventory what we need to do to be able to do this successfully. We are currently running v7.17.6.

Thanks & regards,
Arjen

1 Like
7

Hi @sscarduzio,

We discovered this by running the GET /_migration/deprecations call in Kibana to show us which indices need attention prior to upgrading to (in the meantime) V9.

  • .readonlyrest
  • .readonlyrest_license

were two of the indices popping up there which still had an older version (7.17.6), while we’re already on 8.18.1 with the ELK stack.

We already have an idea how to fix the .readonlyrest index. (by opening two tabs, deleting it in one tab and re-save the config in the other, which should create a new index with the newer version).
But we don’t know how to fix the .readonlyrest_license index. Can we just re-index this one without harming it?

Thanks & regards,
Arjen

8

Hello @abuising

You can remove .readonlyrest_licenseand load the activation key via the Activation Key tab in the Edit security settings page. Thanks to it, a new .readonlyrest_license index will be recreated.

1 Like