Hi, TL:DR, is it safe to delete the `_statistics_`...
# questions-and-troubleshooting
j
Hi, TL:DR, is it safe to delete the
_statistics_
database and let starrocks recreate it? More details - In our shared data cluster we moved storage blobs a while back. The main database we use is called events, so we changed the name of the events database, created a new events database with the new storage volume and copied all of the data. Then we dropped the old events database. I did something similar with the
_statistics_
database. However, in the
_statistics_
database I see thousands of entries in different tables referencing the OLD events database ID, which no longer exists. Is it safe to just drop the
_statistics_
database and let starrocks recreate it or will that cause problems? The reason I need to do this is because starrocks is still trying to go out to the old storage blob container which no longer exists, so we're getting millions of errored out transactions to our blob storage every hour
I dropped the database and it's since been recreated by SR, so I assume everything is fine 🤷
е
it is ok
j
However, I'm still seeing our CNs trying to reach out to the old storage account. The database that it's trying to reach out too was deleted months ago. This is in my storage blob logs, db10107 is the old
events
database ID and the
dataops-k8-blob
container does not exist in that storage account any more
Copy code
https://<storage_account>.<http://dfs.core.windows.net/dataops-k8-blob?directory=starrocks/8718abd5-2c3e-4a04-9515-c6b64d99ff44/db10107/10364/162011/meta&maxResults=1000&recursive=false&resource=filesystem|dfs.core.windows.net/dataops-k8-blob?directory=starrocks/8718abd5-2c3e-4a04-9515-c6b64d99ff44/db10107/10364/162011/meta&maxResults=1000&recursive=false&resource=filesystem>
I don't know if this has been causing problems in starrocks, but each transaction into the blob storage costs money, and it's adding up with millions of transactions every day