Skip to main content

Redis troubleshooting (Windows)

Redis is temporary storage for certain Informer processes (importing and exporting files, sample queries, flow steps, UI logs, progress monitors, and OAuth). These load data into Redis and remove it when finished. Sometimes a system error leaves orphaned data in Redis, growing its memory usage and degrading performance. Use this article to troubleshoot Redis performance issues.

Nothing in Redis is critical

Nothing stored in Redis is critical to Informer. Stop the Informer service while doing Redis maintenance.

Check and flush Redis memory​

With Redis running:

  1. Open an elevated PowerShell and change to the Redis root directory (by default C:\Program Files\Redis).

  2. Run redis-cli and check memory usage:

    info memory

  3. Clear all memory Redis is using:

    flushall

  4. Close the window and restart Informer.

Disable snapshot persistence​

Informer does not need this. With Redis and Informer stopped, edit redis.windows-service.conf in the Redis root directory and set:

stop-writes-on-bgsave-error no

The default is yes. Save, then restart the Redis and Informer services.

Disable snapshots saving to disk​

Informer does not need this, and disabling it removes potentially high disk I/O (a cost and performance win in cloud hosting).

  1. Stop the Redis and Informer services.

  2. In redis.windows-service.conf, comment out these entries with #:

    #save 900 1
    #save 300 10
    #save 60 10000

  3. Save and restart the Redis and Informer services.

Full Redis memory purge​

Occasionally you may need to wipe all of Redis's memory.

  1. Stop the Informer and Redis services.

  2. Open an elevated PowerShell and change to the Redis root directory.

  3. Remove all Redis dump files:

    rm *.rdb

  4. Restart the Redis and Informer services.

Advanced key troubleshooting​

To find problematic keys that persist after flushing, with Redis running:

  1. Open an elevated PowerShell and change to the Redis root directory.

  2. Run redis-cli and list the active keys (keys beginning with log, upload, and download are normal and can be ignored):

    info memory
    keys *

  3. For other keys, check their time to live:

    ttl <keyName>

    The integer is the time remaining for the key, in seconds.

  4. Delete an outlying key and recheck memory usage, repeating for other outliers:

    del <keyName>
    info memory