Demogorgon314 opened a new pull request, #23286:
URL: https://github.com/apache/pulsar/pull/23286

   ### Motivation
   When upgrading broker version from `3.0.x` to `3.3.x` with 
`ExtensibleLoadManagerImpl` enabled, it will have an `Unable to read schema` 
exception. And the broker will fail to start. This issue is caused by 
https://github.com/apache/pulsar/pull/22055 .
   
   ```
   ***************
   *** 23,29 ****
         "default" : null
       }, {
         "name" : "bundleCount",
   !     "type" : "int"
       }, {
         "name" : "cpu",
         "type" : [ "null", 
"org.apache.pulsar.policies.data.loadbalancer.ResourceUsage" ],
   --- 23,29 ----
         "default" : null
       }, {
         "name" : "bundleCount",
   !     "type" : "long"
       }, {
         "name" : "cpu",
         "type" : [ "null", 
"org.apache.pulsar.policies.data.loadbalancer.ResourceUsage" ],
   ***************
   *** 59,65 ****
         "type" : "long"
       }, {
         "name" : "topics",
   !     "type" : "int"
       }, {
         "name" : "updatedAt",
         "type" : "long"
   --- 59,65 ----
         "type" : "long"
       }, {
         "name" : "topics",
   !     "type" : "long"
       }, {
         "name" : "updatedAt",
         "type" : "long"
   ```
   
   
   ### Modifications
   
   Add a new class `NonPersistentSystemTopic`, and it will use for system 
non-persistent topic.
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to