You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/02/22 19:17:00 UTC
[jira] [Updated] (GEODE-4720) data is not re-loaded after cluster
rebooted while geode acts as a redis server
[ https://issues.apache.org/jira/browse/GEODE-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker updated GEODE-4720:
---------------------------------
Affects Version/s: 1.4.0
> data is not re-loaded after cluster rebooted while geode acts as a redis server
> -------------------------------------------------------------------------------
>
> Key: GEODE-4720
> URL: https://issues.apache.org/jira/browse/GEODE-4720
> Project: Geode
> Issue Type: Bug
> Components: redis
> Affects Versions: 1.4.0
> Reporter: pengxu
> Priority: Major
>
> In Apache 1.4.0, the redis keys cann't be reloaded after the cluster is rebooted.
> How to reproduce it?
> 1. start server,
> ```bash
> start server --name=server1 --redis-bind-address=localhost --redis-port=11211 --J=-Dgemfireredis.regiontype=PARTITION_PERSISTENT
> ```
> 2. using redis-cli connect to the server
> sadd hello 1
> smembers hello
> 3. stop the redis server
> ```bash
> stop server --name=server1
> ```
> 4. restart the server
> after the server is restarted, no data is reloaded automatically.
> 5. connect to the server by using redis-cli
> sadd hello 2
> the strange thing is that the old entry recovered while adding one new entry
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)