[
https://issues.apache.org/jira/browse/GEODE-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-8840:
-------------------------------
Description:
Note: see implementation of SETNX, RENAME
Notes from the now-closed PR Currently there's a race condition between when
the new key's existence is checked, and the old key is renamed. It's possible
for two RENAMENX operations, on separate threads, renaming to the SAME new key,
to BOTH succeed. At most one should succeed. The existing DUNIT test
illustrates this problem.
> implement redis RENAMENX command
> --------------------------------
>
> Key: GEODE-8840
> URL: https://issues.apache.org/jira/browse/GEODE-8840
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: John Hutchison
> Priority: Major
> Labels: pull-request-available
>
> Note: see implementation of SETNX, RENAME
> Notes from the now-closed PR Currently there's a race condition between when
> the new key's existence is checked, and the old key is renamed. It's possible
> for two RENAMENX operations, on separate threads, renaming to the SAME new
> key, to BOTH succeed. At most one should succeed. The existing DUNIT test
> illustrates this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
