Denis, Alexey, please share you vision.
Sincerely,
Dmitriy Pavlov
вт, 5 июн. 2018 г. в 19:39, Andrey Mashenkov :
> Dmitry,
>
> There are other cases that can result in inconsistent state of Atomic cache
> with 2 or more backups.
>
> 1. For PRIMARY_SYNC. Primary sends requests to all backups
Dmitry,
There are other cases that can result in inconsistent state of Atomic cache
with 2 or more backups.
1. For PRIMARY_SYNC. Primary sends requests to all backups and respond to
near and then one of backup update fails.
Will primary retry update operation? I doubt.
2. For all sync
Denis,
Seem that you right, it is a problem.
I guess in this case primary node should send CachePartialUpdateException
to near node.
On Tue, Jun 5, 2018 at 6:13 PM, Denis Garus wrote:
> Fix formatting
>
> Hello Igniters!
>
> I have found some confusing behavior of atomic partitioned cache with
Fix formatting
Hello Igniters!
I have found some confusing behavior of atomic partitioned cache with
`PRIMARY_SYNC` write synchronization mode.
Node with a primary partition sends a message to remote nodes with backup
partitions via `GridDhtAtomicAbstractUpdateFuture#sendDhtRequests`.
If during
Hello Igniters!
I have found some confusing behavior of atomic partitioned cache with
`PRIMARY_SYNC` write synchronization mode.
Node with a primary partition sends a message to remote nodes with backup
partitions via `GridDhtAtomicAbstractUpdateFuture#sendDhtRequests`.
If during of sending
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4126
reproducer for atomic cache inconsistent state
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite inc_atomic
Alternatively you can
