Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes
I have been noticing Redis crashes that can only be solved by restarting the VM.
We have Redis 2.8.21 running on a Windows Server 2012 VM with Node.JS and MySQL and use it for sessions, pub/sub and "message" queues.
I have ran redis --test-memory, but cut it off (ctrl+c) after about 7-10 hours when I was not sure if it would go on forever (does it?). I did not notice any anomalies and it was at Random fill (41)
The log file is almost 3GB and mainly contains two messages:
The first one is about 95% of the file and contains only these three lines:
[1356] 18 Aug 11:23:55.804 # Can't save in background: fork: Invalid argument
[1356] 18 Aug 11:23:55.914 * 1 changes in 900 seconds. Saving...
[1356] 18 Aug 11:23:55.914 # BeginForkOperation: system error caught. error code=0x000005af, message=BeginForkOperation: VirtualProtect failed: unknown error
These got spammed every second until this happened:
At this moment the Node.JS server kept crashing because it could not access it's sessions anymore. (It sort of looks like it only happens when it's trying to save a session, but I could be wrong)
P.S. I have tried to be smart and configure the service to restart the computer on the third crash, but that does not seem to work.
P.P.S Redis 3.2 is currently running on our test server and we'll be upgrading to this soon.
I have been noticing Redis crashes that can only be solved by restarting the VM.
We have Redis 2.8.21 running on a Windows Server 2012 VM with Node.JS and MySQL and use it for sessions, pub/sub and "message" queues.
I have ran
redis --test-memory
, but cut it off(ctrl+c)
after about 7-10 hours when I was not sure if it would go on forever (does it?). I did not notice any anomalies and it was atRandom fill (41)
The log file is almost 3GB and mainly contains two messages: The first one is about 95% of the file and contains only these three lines:
These got spammed every second until this happened:
At this moment the Node.JS server kept crashing because it could not access it's sessions anymore. (It sort of looks like it only happens when it's trying to save a session, but I could be wrong)
P.S. I have tried to be smart and configure the service to restart the computer on the third crash, but that does not seem to work.
P.P.S Redis 3.2 is currently running on our test server and we'll be upgrading to this soon.