We also need: backup priority for internal caches as well as conflict
resolution for backups to avoid broken data replicating in the wrong
direction.
Tristan
On 4/12/18 10:13 PM, Tristan Tarrant wrote:
> I think we can certainly make it additive, especially now that we have
> configuration tem
I think we can certainly make it additive, especially now that we have
configuration templates in place: the user supplies a base template, and
the internal cache logic override with what is needed so that broken
configs are less probable (but still possible). Alternatively, instead
of overridi
Backing up caches with protobuf payload to a remote site will not work
if they are indexed, unless the remote site already has the schema for
the types in question, or else indexing will fail. If the cache is not
indexed it matters less.
So the replication of protobuf metadata cache has to be a
It is definitely an internal cache. Because of this, automatically
backing it up to a remote site might not be such a good idea.
Backups are enabled per-cache, and therefore just blindly replicating
the schema cache to the other site is not a good idea.
I think that we need a cache-manager-leve
Wouldn't be better to assume the protobuf cache doesn't fit the internal
cache use case? :)
On 12-04-2018 17:21, Galder Zamarreno wrote:
> Ok, we do need to find a better way to deal with this.
>
> JIRA: https://issues.jboss.org/browse/ISPN-9074
>
> On Thu, Apr 12, 2018 at 5:56 PM Pedro Ruivo
Ok, we do need to find a better way to deal with this.
JIRA: https://issues.jboss.org/browse/ISPN-9074
On Thu, Apr 12, 2018 at 5:56 PM Pedro Ruivo wrote:
>
>
> On 12-04-2018 15:49, Galder Zamarreno wrote:
> > Hi,
> >
> > We have an issue with protobuf metadata cache.
> >
> > If you run in a mul
On 12-04-2018 15:49, Galder Zamarreno wrote:
> Hi,
>
> We have an issue with protobuf metadata cache.
>
> If you run in a multi-site scenario, protobuf metadata information does
> not travel across sites by default.
>
> Being an internal cache, is it possible to somehow override/reconfigure
Hi,
We have an issue with protobuf metadata cache.
If you run in a multi-site scenario, protobuf metadata information does not
travel across sites by default.
Being an internal cache, is it possible to somehow override/reconfigure it
so that cross-site configuration can be added in standalone.xm