ParserException is seen in ES Pod logs causing Readiness probe failure on Logging 5.5 preview

ES pod Logs: http://pastebin.test.redhat.com/1024206

[kbharti@cube ~]$ oc get csv -n openshift-logging

NAME                            DISPLAY                            VERSION   REPLACES   PHASE

clusterlogging.v5.4.0           Red Hat OpenShift Logging          5.4.0                Succeeded

elasticsearch-operator.v5.4.0   OpenShift Elasticsearch Operator   5.4.0                Succeeded

Steps to reproduce:

• Create QE catsrc with quay.io/logging/logging-index:latest index image.
• Deploy Logging 5.4 stacking with vector as collector

Expected Result: ES pod should be up and running with no error in logs.

Actual Result: ParserException seen in ES pod logs

OCP Version: 4.9, 4.10

Cluster Logging instance: http://pastebin.test.redhat.com/1024422