GitHub user robshep added a comment to the discussion: Cannot parse <null> schema
Thank you, Attached is the application log from the first time this happened. It isn't clear exaclty which topic the consumer finds a null schema, but you can see in this example it was both consumers. On this occasion a plain restart recovered one of them (persistent://myorg/appB/notify:expiry) but the other (persistent://myorg/myappA/ingress) did not recover (same error of Null schema on each message received) and so I just trashed the standalone pulsar and started a new instance. It has done it since, but a restart recovered them. Thanks again. [main.log.2020-10-27.txt](https://github.com/apache/pulsar/files/5530118/main.log.2020-10-27.txt) GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414962 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
