GitHub user robshep added a comment to the discussion: Cannot parse <null> schema
I can't relaiably re-produce this, but the issue persists. Thanks @dhinesherode91 for adding your observations. We do not have this load. We have a single standalone running on ample VM (no cpu, memory , i/o or disk pressures) with usual statistics output of 0.3msg/sec We get this error when re-deploying the only consumer application. (producer remains connected). Restarting one or more times resolves the issue to the point where a valid schema definition is printed to the console, not a null one. (so we deploy manually for now) I can't comment on this timing related workaround (_maybe_, **possibly**, there is nothing in the queue, then on a restart there is - next time we re-deploy I will poll the admin interface for queue length and feedback If we leave it, after a null schema is found, it does not recover and no msgs are processed on the topic. **However**, We run the same application in integration tests daily, using an ephemeral pular-standalone in a docker container to test against and never see this issue. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414973 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
