something's wrong with our datahub helm deploy and I'm not sure what to do with it except delete everything and deploy again (which leads me to my previous two threads in #getting-started & #all-things-deployment which seem to have died, asking for useful ways to have datahub not be the master of the data, but rather a view on the data) what do I do when helm times out and e.g. datahub-mysql-setup-job is still running after 22m ?

might have to do with reindexing- did you recently upgrade? There’s a regression/fix we’re looking into that we’ll post about soon in #announcements

eventually fixed it: turns out the binlogs for mysql were being spammed full, had the full 8GB of disk space used by those logs