market price and kline doesn't update

[TaylorWenOne]

i find that trade is going and correct, but market price and kline data doesn't update, that is why?

[TaylorWenOne]

i see some error like this
btc-redis-master | 1:M 27 Jul 06:01:36.045 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:01:36.046 # Can't save in background: fork: Out of memory
btc-redis-master | 1:M 27 Jul 06:01:42.056 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:01:42.057 # Can't save in background: fork: Out of memory
btc-redis-master | 1:M 27 Jul 06:01:48.064 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:01:48.064 # Can't save in background: fork: Out of memory
btc-redis-master | 1:M 27 Jul 06:01:54.070 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:01:54.071 # Can't save in background: fork: Out of memory
btc-redis-master | 1:M 27 Jul 06:02:00.078 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:02:00.078 # Can't save in background: fork: Out of memory
btc-redis-sentinel | 1:X 27 Jul 06:02:06.081 # +sdown master mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:06.082 # +odown master mymaster 172.18.0.4 6379 #quorum 1/1
btc-redis-sentinel | 1:X 27 Jul 06:02:06.082 # +new-epoch 1
btc-redis-sentinel | 1:X 27 Jul 06:02:06.082 # +try-failover master mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:06.084 # +vote-for-leader 57e77c4f9ec50110af5e874a4c9bb245dd7c8468 1
btc-redis-sentinel | 1:X 27 Jul 06:02:06.084 # +elected-leader master mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:06.084 # +failover-state-select-slave master mymaster 172.18.0.4 6379
btc-redis-master | 1:M 27 Jul 06:02:06.086 * 100 changes in 300 seconds. Saving...
btc-redis-master | 1:M 27 Jul 06:02:06.087 # Can't save in background: fork: Out of memory
btc-redis-sentinel | 1:X 27 Jul 06:02:06.155 # +selected-slave slave redis_slave:6379 172.18.0.5 6379 @ mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:06.155 * +failover-state-send-slaveof-noone slave redis_slave:6379 172.18.0.5 6379 @ mymaster 172.18.0.4 6379

[TaylorWenOne]

btc-redis-sentinel | 1:X 27 Jul 06:02:06.245 * +failover-state-wait-promotion slave redis_slave:6379 172.18.0.5 6379 @ mymaster 172.18.0.4 6379
btc-redis-slave | 1:M 27 Jul 06:02:06.246 # Setting secondary replication ID to 4d9a9f571043a275847d545963b1f1c780db637e, valid up to offset: 493821. New replication ID is 94bde5269a2e24511e98cf33a700b4e3451501eb
btc-redis-slave | 1:M 27 Jul 06:02:06.246 # Connection with master lost.
btc-redis-slave | 1:M 27 Jul 06:02:06.246 * Caching the disconnected master state.
btc-redis-slave | 1:M 27 Jul 06:02:06.246 * Discarding previously cached master state.
btc-redis-slave | 1:M 27 Jul 06:02:06.246 * MASTER MODE enabled (user request from 'id=2 addr=172.18.0.7:38340 fd=9 name= age=2164 idle=0 flags=x db=0 sub=0 psub=0 multi=3 qbuf=0 qbuf-free=32768 obl=36 oll=0 omem=0 events=r cmd=exec')
btc-redis-master | 1:M 27 Jul 06:02:06.246 # Connection with slave 172.18.0.5:6379 lost.
btc-redis-sentinel | 1:X 27 Jul 06:02:07.161 # +promoted-slave slave redis_slave:6379 172.18.0.5 6379 @ mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:07.161 # +failover-state-reconf-slaves master mymaster 172.18.0.4 6379
btc-redis-sentinel | 1:X 27 Jul 06:02:07.210 * +slave-reconf-sent slave 172.18.0.5:6379 172.18.0.5 6379 @ mymaster 172.18.0.4 6379
btc-redis-slave | 1:S 27 Jul 06:02:07.210 * Before turning into a slave, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
btc-redis-slave | 1:S 27 Jul 06:02:07.210 * SLAVE OF 172.18.0.5:6379 enabled (user request from 'id=8 addr=172.18.0.7:50412 fd=8 name=sentinel-57e77c4f-cmd age=1 idle=0 flags=x db=0 sub=0 psub=0 multi=3 qbuf=135 qbuf-free=32633 obl=36 oll=0 omem=0 events=r cmd=exec')
btc-redis-slave | 1:S 27 Jul 06:02:07.932 * Connecting to MASTER 172.18.0.5:6379
btc-redis-slave | 1:S 27 Jul 06:02:07.933 * MASTER <-> SLAVE sync started
btc-redis-slave | 1:S 27 Jul 06:02:07.933 * Non blocking connect for SYNC fired the event.
btc-redis-slave | 1:S 27 Jul 06:02:07.934 * Master replied to PING, replication can continue...
btc-redis-slave | 1:S 27 Jul 06:02:07.934 * Trying a partial resynchronization (request 94bde5269a2e24511e98cf33a700b4e3451501eb:493821).
btc-redis-slave | 1:S 27 Jul 06:02:07.935 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master

btc-redis-slave | 1:S 27 Jul 06:13:55.003 * MASTER <-> SLAVE sync started
btc-redis-slave | 1:S 27 Jul 06:13:55.003 * Non blocking connect for SYNC fired the event.
btc-redis-slave | 1:S 27 Jul 06:13:55.003 * Master replied to PING, replication can continue...
btc-redis-slave | 1:S 27 Jul 06:13:55.003 * Trying a partial resynchronization (request 94bde5269a2e24511e98cf33a700b4e3451501eb:493821).
btc-redis-slave | 1:S 27 Jul 06:13:55.004 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master
btc-redis-slave | 1:S 27 Jul 06:13:56.004 * Connecting to MASTER 172.18.0.5:6379
btc-redis-slave | 1:S 27 Jul 06:13:56.004 * MASTER <-> SLAVE sync started
btc-redis-slave | 1:S 27 Jul 06:13:56.005 * Non blocking connect for SYNC fired the event.
btc-redis-slave | 1:S 27 Jul 06:13:56.005 * Master replied to PING, replication can continue...
btc-redis-slave | 1:S 27 Jul 06:13:56.005 * Trying a partial resynchronization (request 94bde5269a2e24511e98cf33a700b4e3451501eb:493821).
btc-redis-slave | 1:S 27 Jul 06:13:56.005 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master

[TaylorWenOne]

it looks like redis-master crash because out of memory？

[TaylorWenOne]

@haipome could you help me?yang,thank you very much