[
https://issues.jboss.org/browse/ISPN-9111?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-9111:
----------------------------------------
Actually, not all internal caches might need x-site replicating. As per Dan's
comments:
bq. The CONFIG cache is also internal, but it shouldn't be replicated across sites,
because the backup cache can have a different name and config compared to the original
cache. Index manager caches are also internal, and I don't think they should be backed
up either. If the backup needs to be indexed, it should compute its own index.
Internal caches should be replicated across sites
-------------------------------------------------
Key: ISPN-9111
URL:
https://issues.jboss.org/browse/ISPN-9111
Project: Infinispan
Issue Type: Enhancement
Components: Cross-Site Replication, Remote Querying
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Labels: redhat-summit-18
Given a cache manager, we should look for all enabled x-site locations and add those
sites as SYNC backups for the protobuf metadata cache. Without this data, the user has to
implement its own code to make sure the data is added in each site which is troublesome.
Using SYNC/FAIL combo turns out to be very buggy. In the initial test created, only one
site was up and the other was not. The put call to replicate the metadata was failing (as
a result of ISPN-9113) but this was going under the radar (more tests needed!), and it
ended up waiting for the replication timeout to happen.
Even after replication timeout happened, the put call was completing fine. This is
because invocation batching was enabled for protobuf metadata cache which means any update
failures would not make the cache operations fail.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)