qidaye opened a new pull request #6893:
URL: https://github.com/apache/incubator-doris/pull/6893


   ## Proposed changes
   
   When loading meta by meta_tool goes wrong, we only get an error code from 
`json2pb`, which is inconvenient for us to locate the problem.
   
   This change is adding error message when loading meta goes wrong.
   
   Log change is like below.
   
   ```
   # before
   ./meta_tool --root_path=/home/disk1/qjl/mydoris/be/storage 
--operation=load_meta --json_meta_path=/home/disk1/qjl/data/meta-json.json
   WARNING: Logging before InitGoogleLogging() is written to STDERR
   I1020 11:41:56.564241 74937 data_dir.cpp:837] path: 
/home/disk1/qjl/mydoris/be/storage total capacity: 7750843404288, available 
capacity: 7583325925376
   I1020 11:41:56.564415 74937 data_dir.cpp:275] path: 
/home/disk1/qjl/mydoris/be/storage, hash: 7528840506668047470
   load meta failed, status:-1410
   
   # after 
   ./meta_tool --root_path=/home/disk1/qjl/mydoris/be/storage 
--operation=load_meta --json_meta_path=/home/disk1/qjl/data/meta-json.json
   WARNING: Logging before InitGoogleLogging() is written to STDERR
   I1020 14:41:40.084342 50727 data_dir.cpp:837] path: 
/home/disk1/qjl/mydoris/be/storage total capacity: 7750843404288, available 
capacity: 7584601022464
   I1020 14:41:40.084496 50727 data_dir.cpp:275] path: 
/home/disk1/qjl/mydoris/be/storage, hash: 7528840506668047470
   E1020 14:41:40.163007 50727 tablet_meta_manager.cpp:161] JSON to protobuf 
message failed: Fail to decode base64 string=0
   load meta failed, status:-1410
   
   ```
   
   ## Types of changes
   
   What types of changes does your code introduce to Doris?
   _Put an `x` in the boxes that apply_
   
   - [ ] Bugfix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] Documentation Update (if none of the other choices apply)
   - [ ] Code refactor (Modify the code structure, format the code, etc...)
   - [x] Optimization. Including functional usability improvements and 
performance improvements.
   - [ ] Dependency. Such as changes related to third-party components.
   - [ ] Other.
   
   ## Checklist
   
   _Put an `x` in the boxes that apply. You can also fill these out after 
creating the PR. If you're unsure about any of them, don't hesitate to ask. 
We're here to help! This is simply a reminder of what we are going to look for 
before merging your code._
   
   - [ ] I have created an issue on (Fix #ISSUE) and described the bug/feature 
there in detail
   - [ ] Compiling and unit tests pass locally with my changes
   - [ ] I have added tests that prove my fix is effective or that my feature 
works
   - [ ] If these changes need document changes, I have updated the document
   - [ ] Any dependent changes have been merged
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[email protected] by explaining why you chose the solution you did and what 
alternatives you considered, etc...
   


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