[jira] [Commented] (GEODE-8192) Redis MSET command needs to be atomic

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419912#comment-17419912 ] 

ASF subversion and git services commented on GEODE-8192:
--------------------------------------------------------

Commit db60e0e06b41ae3b37335bf29e2e9c3c3691b863 in geode's branch refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=db60e0e ]

GEODE-8192: Make Radish MSET command atomic (#6862)

- Replace SynchronizedStripedCoordinator with LockingStripedCoordinator
  which locks against a list of locks instead of recurisively locking.
- Perform the MSET operation within a transacation. This will avoid
  partial results in the case of a server shutdown.
- Add DUnit tests to repeatedly crash the primary server while
  performing concurrent MSETs.

> Redis MSET command needs to be atomic
> -------------------------------------
>
>                 Key: GEODE-8192
>                 URL: https://issues.apache.org/jira/browse/GEODE-8192
>             Project: Geode
>          Issue Type: Bug
>          Components: redis
>            Reporter: Darrel Schneider
>            Priority: Major
>              Labels: pull-request-available
>
> All of the supported and unsupported redis string commands (for the 1.14 release) that need to be atomic now are except for MSET.
> Note that MGET does not need to be atomic.
> To make MSET atomic it could do something like RENAME does to lock multiple keys in a manner that prevent a distributed deadlock.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)