This likely indicates that you have an integration test configured to run every 2 hours, and that test is consistently failing. Integration tests create new namespaces on the fly to run your test in isolation, and the namespace is only deleted if the test succeeds. If the test fails, it’s left behind so you can switch to that namespace and debug whatever went wrong.
I would recommend that you remove the scheduling from that test so it stops running until you have a chance to debug the test and understand why it is consistently failing. Once you figure out why your test is failing it should be safe to delete all of these generated namespaces.
Please reach out to support if you have any trouble.
A “Best Practice” when using Vantiq is to check your error logs at the start and end of each day. Ensure that your applications are not spewing errors. If at the end of the day, the application is not working then turn it off. If it is failing at the beginning of the day, either fix the problem or disable it until you have time to work on it.
Similarly, when you deploy your applications to production you should monitor them for correct operation, expected performance, etc.
When troubleshooting real problems, it is a distraction to wade through 100K’s of error messages.
- You must be logged in to reply to this topic.
I suddenly realized that I had created 236 namespaces in my Vantiq organization of the form Atest_<date_time> (one every two hours since 21-February).
How did this happen?