benmayersohn opened a new issue, #50187:
URL: https://github.com/apache/doris/issues/50187

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   doris-3.0.4-rc02
   
   ### What's Wrong?
   
   I noticed that when running `show proc '/colocation_group'`, some tables 
that show up are previous tables that were dropped, but are still assigned to 
the colocation group. For example
   
   GroupId | GroupName | TableIds | BucketsNum | ReplicaAllocation | DistCols | 
IsStable | ErrorMsg
   -- | -- | -- | -- | -- | -- | -- | --
   10522.1744747308069 | example_group_1 | 1744747308027 | 10 | 
tag.location.default: 3 | bigint | true |  
   10522.1744747308024 | example_group_2 | 112897, 125844 | 10 | 
tag.location.default: 3 | int | true |  
   10522.103738 | example_group_3 | 188926, 1744747308071 | 10 | 
tag.location.default: 3 | bigint | true |  
   10522.1744747308025 | example_group_4 | 218843, 220282 | 10 | 
tag.location.default: 3 | bigint | true |  
   10522.1744747308023 | example_group_5 | 95318, 185813, 185871, 186240, 
186518, 186581, 200362, 212188, 1744211469161, 1744747293286, 1744747293293, 
1744747307786 | 10 | tag.location.default: 3 | bigint | false | Colocation 
group modified by user
   
   `example_group_1` and `example_group_3` only contain tables that are no 
longer in the database, but are still referenced here. I'm not sure how to 
purge them from the metadata.
   
   ### What You Expected?
   
   Only Table IDs corresponding to existing tables in the corresponding 
database should be listed
   
   ### How to Reproduce?
   
   Create a table with a given colocation group, drop the table, and then run 
`show proc '/colocation_group'`.
   
   I've had a bunch of residual issues since dropping a backend that some 
replicas were created on (no data was lost as there were two other replicas, 
but I had to manually change the replicas on the dropped backend to bad to have 
new ones created on an existing backend server). I'm not sure if this issue is 
reproducible outside of this scenario.
   
   ### Anything Else?
   
   I would love some more documentation on cleaning up metadata when it doesn't 
match the underlying data. Doris has tools to handle some of this stuff 
automatically under the hood, but I've found manual intervention to be needed 
more often than not.
   
   ### 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