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.