tinkerrrr opened a new issue #7344:
URL: https://github.com/apache/incubator-doris/issues/7344


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Version
   
   0.14.0 and 0.15.0
   
   ### What's Wrong?
   
   I was going to upgrade Doris from 0.14.0 to 0.15.0, it performs well during 
the upgrade process. But a complete upgrade plan of production environment 
should contain degradation plan. When degrade from 0.15 to 0.14, FE crash with 
excetion: 
   
   ```
   java.io.EOFException
       at java.io.DataInputStream.readFully(DataInputStream.java:197)
       at org.apache.doris.common.io.Text.readString(Text.java:415)
       at org.apache.doris.catalog.Catalog.loadMasterInfo(Catalog.java:1580)
       at org.apache.doris.catalog.Catalog.loadImage(Catalog.java:1479)
       at org.apache.doris.catalog.Catalog.initialize(Catalog.java:760)
       at org.apache.doris.PaloFe.start(PaloFe.java:108)
       at org.apache.doris.PaloFe.main(PaloFe.java:60)
   ```
   
   This could reduce the confidence of upgrading
   
   ### What You Expected?
   
   Guarantee compatibility between FE 0.14 and FE 0.15
   
   ### How to Reproduce?
   
   upgrade from 0.14 to 0.15 and then degrade from 0.15 to 0.14
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to