Hi Marco Cold Standby is a TarMK feature that allows for a quick failover. You may think of it as a near real-time backup. It is _not_ a cluster. As you noted, the sync is one-way only.
Therefore, I don't think it is possible to direct reads or writes to the cold standby instance. AFAIK this should be prevented by the implementation. But others are more knowledgable about these details. Regards Julian On Mon, Oct 16, 2017 at 11:28 AM, Marco Piovesana <[email protected]> wrote: > Hi all, > I'm trying to set-up a cluster environment with Oak, so that anytime I can > take down for maintenance one machine without stopping the service. One > option is of course to use Mongo or RDBM storages. Talking with the guys at > adaptTo() this year I've been told that maybe there's another option: > replicate the repository in each instance of the cluster and use the "*cold > standby*" for the synchronization. > The sync process, however, is one-way only. My question is: do you guys > think is possible to use it in a cluster where read and write requests are > coming from any of the instances of the cluster? > > Marco.
