All content with label cluster+failover.
Related Labels: partioned-cache , heap , coherence-web , proxy , namedcache , cache-topologies , production-environment , listeners , reliability , defaultcacheserver , jms , availability , c-w-archive , mutex , service , sessions , failback , performance , optimistic , testing , agents , faq-coherence-web , operating-system , session-cache-config , developer-to-review , mbeans , replication , local , mutext , hardware , manageability , faq-code-examples , security , events , cache-config , best-practices , provider , session-management , servletcontext , rtc , backing-map , extend , core-concept , scalability , network , serialization , serviceability , httpsessioncontext , death-detection , paged , invocation , example , real-time-client , partitioned , multicast , faq-config , member , glossary , federation , tcp , huge-caches , distributed , update-after-forums-move , clients , high-availability , singleton , local-storage , local-cache , load-balancing more » ( - cluster , - failover )

Clustering (Coherence 3.4 User Guide) Coherence is built on a fully clustered architecture. Since "clustered" is an overused term in the industry, it is worth stating exactly what it means to say that Coherence is clustered. Coherence is based on a peertopeer clustering protocol, using a conference room model, in which servers ...