As a follow up to this email, we are starting to collect evidence that
replicated caches within our Ignite grid are failing to replicate values in
a small number of cases.
In the cases we observe so far, with a cluster of 4 nodes participating in
a replicated cache, only one node reports having
I kicked off a separate thread for this as requested.
On Tue, Jul 25, 2023 at 9:43 PM Pavel Tupitsyn wrote:
> > If the primary node 'comes back' after the primary node failure would
> you expect the new value to propagate to all nodes?
>
> I don't think so, but I'm not 100% sure - could you ask
> If the primary node 'comes back' after the primary node failure would you
expect the new value to propagate to all nodes?
I don't think so, but I'm not 100% sure - could you ask about this specific
case in a separate thread?
On Tue, Jul 25, 2023 at 8:50 AM Raymond Wilson
wrote:
> >>
>> However, if a primary node fails before at least 1 backup node receives
an update, then the update will be lost, and all nodes will have the old
value.
Does this imply that it is a good idea to have the FullSync write
synchronization mode? If the primary node 'comes back' after the primary
> if a hard failure occurs to one of the backup servers in the replicated
cache will the server that failed have an inconsistent (old) copy of that
element in the replicated cache when it restarts
If only a backup server fails and restarts, it will get new data from the
primary node, no issue
Hi Pavel,
I understand the differences between the sync modes in terms of when the
write returns. What I want to understand is if there are consistency risks
with the PrimarySync versus FullSync modes.
For example, if I have 4 nodes participating in the replicated cache (and
am using the default
Please check this reply on StackOverflow - does it help?
https://stackoverflow.com/questions/45497095/explicit-setting-of-write-synchronization-mode-full-sync-needed-for-replicated-c
On Wed, Jul 19, 2023 at 1:38 AM Raymond Wilson
wrote:
> I have a query regarding the
I have a query regarding the CacheWriteSynchronizationMode in
CacheConfiguration.
This enum is defined like this in the .Net client:
public enum CacheWriteSynchronizationMode
{
///
/// Mode indicating that Ignite should wait for write or commit replies
from all nodes.
/// This
