[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse 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

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi No, sadly I cannot recreate this issue in isolation. But It occurs on ~50% of redeploys and requires repeated restarts of the application to clear it. We use TestContainers as part of the integration tests to spin

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse 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 occ

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Thank you, If the components are generally stable then there could be issues with my setup? In this case I am grateful for your support, and will look you up on slack With thanks R Get Outlook for iOS

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi, This is still happening and we still need to keep restarting connected producers/consumers after updating our application. Occasionally if 20+restarts does not clear it, we destroy the (docker standalone) broker

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Thank you, I'm afraid I don't know how to get the schema compatibility policy of a topic - please can you advise. I don't see a cli command to show this) On the few occasions this has happened, it typically works OK

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi, thanks for taking a look. There are 3 topics in use in this deployment. All have schemas. None of this code, or the Payload objects have changed for many months. I notice in App1 there is another topic `-RETRY`

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema A log file showing the same issue encountered just now. A restart of the application recovered, but seemingly wasn't able to recover itself. [thingping.log](https://github.com/apache/pulsar/files/5490475/thingping.l