[jira] [Updated] (GEODE-8192) Redis MSET command needs to be atomic
[ https://issues.apache.org/jira/browse/GEODE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-8192: - Labels: pull-request-available unreleased (was: pull-request-available) > 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 >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > 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.20.1#820001)
[jira] [Updated] (GEODE-8192) Redis MSET command needs to be atomic
[ https://issues.apache.org/jira/browse/GEODE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-8192: Summary: Redis MSET command needs to be atomic (was: Redis String commands are not atomic) > 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 > > Some of the unsupported redis string commands have implementations that are > not atomic. > Examples are: getset, incr*, decr*, mset*, mget. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8192) Redis MSET command needs to be atomic
[ https://issues.apache.org/jira/browse/GEODE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-8192: Description: 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. was: Some of the unsupported redis string commands have implementations that are not atomic. Examples are: getset, incr*, decr*, mset*, mget. > 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 > > 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)
[jira] [Updated] (GEODE-8192) Redis MSET command needs to be atomic
[ https://issues.apache.org/jira/browse/GEODE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-8192: -- Labels: pull-request-available (was: ) > 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)
