[GitHub] [pulsar] robshep commented on issue #8429: Cannot parse schema

[GitBox <gi...@apache.org>]

robshep commented on issue #8429:
URL: https://github.com/apache/pulsar/issues/8429#issuecomment-1062755688


   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. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org