BitSet.or took high cpu usage

Elastic Stack Elasticsearch
1

Continuing the discussion from BitSet.or consumes almost 60% cpu:

We found sth. new here.

In fact , we ran into this problem twice after the topic was closed.

And We found some similarities in these cases: this problem was occurred right after we deleted an index.

It looks like this delete action is causing a problem with the caching mechanism.

Now we keep digging into this and hopefully, someone may take sometime to take a look at this.

2

Since @Mark_Harwood is left, and he highly recommends that @DavidTurner you follow up on this issue.

So could you take a look at this?
Thanks in advance.

3

Please don't @mention people to get their attention if they aren't involved in your conversation already. We are all volunteers here.