Why am I getting multiple indices for the same Tenant on Searchguard? Is this an intended outcome?
I have a tenant called ‘admintenant’, but the system indices show ''kibana_admintenant_1" and “kibana_admintenant_2”.
Also, the “kibana_admintenant_2” has an alias set to “kibana_admintenant”.
I do not understand why it is creating two separate indices, and if it is safe to delete one of them.
Thank you.
Configurations:
Searchguard version: 6.6.1-18.1
Elastic Version: 6.6.1
OS version: CentOS Version 7
Elastic master nodes: 5 (statefulset)
Elastic data nodes: 4 (statefulset)
The indices are not created by Search Guard, but by Kibana. This feature (“saved objects migrations”) was added in Kibaba 6.5:
With multi-tenancy the saved objects are stored in a separate index per tenant, tthus the saved objects migrations are applied to each tenant index.
···
On Tuesday, March 26, 2019 at 6:36:27 PM UTC+1, mchakradeo@zuora.com wrote:
Why am I getting multiple indices for the same Tenant on Searchguard? Is this an intended outcome?
I have a tenant called ‘admintenant’, but the system indices show ''kibana_admintenant_1" and “kibana_admintenant_2”.
Also, the “kibana_admintenant_2” has an alias set to “kibana_admintenant”.
I do not understand why it is creating two separate indices, and if it is safe to delete one of them.
Thank you.
Configurations:
Searchguard version: 6.6.1-18.1
Elastic Version: 6.6.1
OS version: CentOS Version 7
Elastic master nodes: 5 (statefulset)
Elastic data nodes: 4 (statefulset)