You can translate the question and the replies:

unavailability of shared cache during deployments in mult-node architecture

we have a single cache DB ( shared cache) for multiple Prodution denodo nodes. but problem with this architecture is when we do deployment of views having cache associated with it on any of nodes . this makes the cache unavailable/invalid for other nodes as well. this is problem as we cant have downtime in denodo and we need to ensure that other nodes can access cache during deployment. does denodo offers management of multiple cache with in house replication solution ? or can we have a secondary shared cache which can act as primary during deployment and denodo can manage this swapping of cache. we are using denodo 6 and using shell scripts/import.sh for deployments
user
24-01-2020 01:13:58 -0500

1 Answer

Hi, I recommend using two cache servers to prevent downtime when using a shared cache. Switching Denodo servers to the second cache after updating will allow you separate the updated servers from the ones that haven't been updated yet and also update the cache server. I've included a link to the [Denodo Platform Cluster Architecture](https://community.denodo.com/kb/view/document/Denodo%20Platform%20Cluster%20Architecture?category=Best+practices) page; you can find more information about best practices for Denodo cluster cache architecture here. I hope this helps!
Denodo Team
28-01-2020 11:10:19 -0500
You must sign in to add an answer. If you do not have an account, you can register here