You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/01 17:26:00 UTC

[jira] [Commented] (GEODE-8965) Implement Redis "noevict" policy for Geode Redis

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

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

Commit b58bfc50e70973ef56daff95bed8c5bbfc02d43c in geode's branch refs/heads/support/1.14 from Ray Ingles
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b58bfc5 ]

GEODE-8965:  Support Redis-style OOM error message (#6085) (#6213)

- Allow execution of Redis commands in low-memory conditions
- Test with large key size to guarantee OOM error
- In tests use multiple key sizes to pack used memory more tightly
- force multiple GCs as memory is filled, add memory-pressure thread in tests
- Add memory pressure to del and expire tests

Co-authored-by: Ray Ingles <ri...@vmware.com>
(cherry picked from commit 08da3aaa1dd3dd5dd212353ecead32819e584c62)

> Implement Redis "noevict" policy for Geode Redis
> ------------------------------------------------
>
>                 Key: GEODE-8965
>                 URL: https://issues.apache.org/jira/browse/GEODE-8965
>             Project: Geode
>          Issue Type: New Feature
>          Components: redis
>            Reporter: Ray Ingles
>            Assignee: Ray Ingles
>            Priority: Major
>              Labels: blocks-1.14.0​, pull-request-available
>             Fix For: 1.14.0, 1.15.0
>
>
> Redis supports the "noevict" eviction policy. When this is selected, Redis returns an OOM error when commands that consume new memory are attempted. New data cannot be written to the cache until either TTL expiration or explicit deletion of keys has freed enough memory to allow write operations again.



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