Leave Bridge

A running clustered cache can leave a Bridge if the Bridge is unresponsive. It is first checked if the Bridge service is up; there is a probability that the Bridge is experiencing a network glitch. You can then remove the cache from the Bridge, if needed. However, if the service is stopped, it indicates that the Bridge is not coming back. In that case, the cache can leave the Bridge, which will empty the queue and remove all the Bridge-related configuration tags from the cache configuration file (config.ncconf).

This functionality is required when the bridge becomes unavailable, and the associated cache needs to be released so it can join another bridge. If the bridge is available, you need to remove caches from it through the bridge management section instead, as discussed below.

Using the NCache Management Center

To leave a Bridge, follow the steps mentioned below.

• Launch the NCache Management Center by browsing to http://localhost:8251 or <server-ip>:8251 on Windows and Linux.

• Open Clustered Caches. Select the cache which is to leave the Bridge and click on "...".

• Select Leave Bridge from the options displayed.

• If your Bridge nodes are available, it will ask you to redirect to the Bridge settings page so the cache can be removed from there. Please refer to the chapter Remove Cache from Bridge for more details.

• If your Bridge nodes are unavailable and you chose to remove the Bridge, you are prompted with a warning message. Select Yes. This will remove the Bridge tags from config.ncconf, and this cache can now be a part of any other Bridge.

See Also

Add Clustered Caches to Bridge
Configure Conflict Resolver
Change Cache Synchronization Modes
Remove Cache from Bridge