Best Practice for Zero Downtime Maintenance
How can you maintain your Mindbreeze InSpire multi-node setup with zero downtime?
Here is a short video to explain:
To Summarize:
You have a couple of producers and consumers behind a load balancer.
First, start maintaining the producers – update, reindex, reinversion, and other operational tasks.
When the maintenance of the producer is complete, verify that everything is working correctly. Now, you deactivate the consumers for maintenance and synchronize the changes from the producers to the consumers.
Once you verify that the consumers are up and running, you activate all the nodes at the load balance. Now, you have effectively maintained your setup without end-users knowing any maintenance was even happening.
If you would like to learn more about this topic, please visit the Mindbreeze Academy webpage.
Latest Blogs
From Enterprise Search to Enterprise Action: Daniel Fallmann Joins the Disambiguation Podcast
What does an AI agent need before an enterprise can trust it to complete real work?
The Hidden Cost of Enterprise AI: Why Token Maxxing Is a C-Suite Problem, and What Mindbreeze Is Doing About It
For the last few years, enterprise AI has run on a comfortable assumption: more context produces better intelligence. If a model can accept a larger context window, feed it more. More documents, longer prompts, deeper histories, bigger retrieval payloads.