pengxiangyu opened a new issue, #9278:
URL: https://github.com/apache/incubator-doris/issues/9278

   ### 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.15.1.rc09
   
   ### What's Wrong?
   
   image file is written by doCheckpint()
   editLog is written by other thread
   if they are running like this make an error:
   1. change table schema.
   2. write it into image file
   3. before editlog, PaloFe is down.
   
   After this, when restart PaloFe, only table schema is changed but editlog 
doesn't exit, it will cause a serious unexpected error.
   Other edit log may have the same error, all of them need to be checked.
   
   ### What You Expected?
   
   image file and editlog has the same order, it is better to write edit log 
before image.
   
   ### How to Reproduce?
   
   Add a big sleep in SchemaChangeJobV2.java,  between 
addShadowIndexToCatalog(tbl); and 
Catalog.getCurrentCatalog().getEditLog().logAlterJob(this);
   When the thread is sleeping and a new image is created, stop PaloFe and 
restart it.
   You can see new schema of the table but no SchemaChangeJob for it.
   
   ### 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: commits-unsubscr...@doris.apache.org.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to