Bad table config may result in Zombie tables
See original GitHub issueIssue faced by user:
hey folks, does anyone have experience with “zombie” tables? I attempted to add a tableSpec but was missing a field in the
config. This resulted in a null pointer exception when Pinot processed the config. As a result, the table doesn’t exist in the
UI or by querying the list API, but I can’t create a table with the same name due to receiving an error that “table already
exists”. Presumably the spec reached ZK or something, but no where else? What can be done to remove the zombie table?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Zombie Processes are Eating your Memory | Random ASCII
It occurred to me that one cause of zombie processes could be one process failing to close the handles to other processes. And...
Read more >Can bulkinsert cause zombie records? - sql - Stack Overflow
Yes, it can cause INVOICE LINES rows referencing non-existing INVOICE ("zombie records" ... You can detect bad rows with a post-load query
Read more >Massive problems with database locks / zombies - JDELIST.com
We have had two mistakes in our environment - first misconfigured ODBC settings on the cluster nodes and another and really ugly issue...
Read more >Databases: Zombie Thread Mysql 5 Moodle 1.7 - Moodle in English
Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely...
Read more >Loot table - Minecraft Wiki - Fandom
Custom data packs use loot tables to change what loot can spawn in containers or drop by mobs. They can either change existing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Investigation in progress
Fix has been merged. We now do a full ZK metadata cleanup in case there is any failure during the table creation process.