Elastics index folder doesn't contain project name after upgrading from 3.9 to 3.11

Solution Verified - Updated -

Issue

After EFK stack was upgraded to 3.11, it seems I can't longer match a directory within the Elasticsearch data path with an index name. In example:

In 3.9:

[root@redhat indices]# pwd
/mnt/local-storage/infra-sc/elastic/logging-es/data/logging-es/nodes/0/indices
[root@redhat indices]# ls -lrt | tail -1
drwxr-sr-x. 3 1000080000 1000080000 20 Jan 15 08:46 project.test-rh.d2da18f1-2bb-11e9-81c0-000d3aa32fcf.2020.01.15

In 3.11:

[root@redhat indices]# pwd                           
/mnt/local-storage/lab-es/elastic/logging-es/data/logging-es/nodes/0/indices                        
[root@redhat indices]# ls -lrt | tail -5             
drwxrwsr-x. 6 1000080000 1000080000 47 Jan 15 15:49 4QK5TTmaR9Gq0P2zFCkYDA                                                  
drwxr-sr-x. 4 1000080000 1000080000 29 Jan 15 15:49 OEdnhb40QG6FJ3ldQ30pgA                                                  
drwxrwsr-x. 4 1000080000 1000080000 29 Jan 15 15:49 z6f1oPQSS3SDz7x_O7JKJA                                                  
drwxrwsr-x. 4 1000080000 1000080000 29 Jan 15 15:49 1Via72n2RxSzCwPFxUquxw                                                  
drwxrwsr-x. 4 1000080000 1000080000 29 Jan 15 15:49 XwfrYbiaRR6cBSwAfGrAHQ 

Environment

OCP 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content