sripathikrishnan/redis-rdb-tools is one of the open-source repositories TopGit tracks, currently at 5.2k stars, written primarily in Python. Parse Redis dump.rdb files, Analyze Memory, and Export Data to JSON
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Parse Redis dump.rdb files, Analyze Memory, and Export Data to JSON
Rdbtools is a parser for Redis' dump.rdb files. The parser generates events similar to an xml sax parser, and is very efficient memory wise.
In addition, rdbtools provides utilities to :
Generate a Memory Report of your data across all databases and keys
Convert dump files to JSON
Compare two dump files using standard diff tools
Rdbtools is written in Python, though there are similar projects in other languages. See FAQs for more information.
See https://rdbtools.com for a gui to administer redis, commercial support, and other enterprise features.
Installing rdbtools
Pre-Requisites :
python-lzf is optional but highly recommended to speed up parsing.
redis-py is optional and only needed to run test cases.
To install from PyPI (recommended) :
pip install rdbtools python-lzf
To install from source :
git clone https://github.com/sripathikrishnan/redis-rdb-tools
cd redis-rdb-tools
sudo python setup.py install
Command line usage examples
Every run of RDB Tool requires to specify a command to indicate what should be done with the parsed RDB data.
Valid commands are: json, diff, justkeys, justkeyvals and protocol.
The json command output is UTF-8 encoded JSON.
By default, the callback try to parse RDB data using UTF-8 and escape non 'ASCII printable' characters with the \U notation, or non UTF-8 parsable bytes with \x.
Attempting to decode RDB data can lead to binary data curroption, this can be avoided by using the --escape raw option.
Another option, is to use -e base64 for Base64 encoding of binary data.
Parse the dump file and print the JSON on standard output:
> rdb -c json /var/redis/6379/dump.rdb
[{
"Citat":["B\u00e4ttre sent \u00e4n aldrig","Bra karl reder sig sj\u00e4lv","Man ska inte k\u00f6pa grisen i s\u00e4cken"],
"bin_data":"\\xFE\u0000\u00e2\\xF2"}]
Parse the dump file to raw bytes and print the JSON on standard output:
> rdb -c json /var/redis/6379/dump.rdb --escape raw
[{
"Citat":["B\u00c3\u00a4ttre sent \u00c3\u00a4n aldrig","Bra karl reder sig sj\u00c3\u00a4lv","Man ska inte k\u00c3\u00b6pa grisen i s\u00c3\u00a4cken"],
"bin_data":"\u00fe\u0000\u00c3\u00a2\u00f2"}]
Generate Memory Report
Running with the -c memory generates a CSV report with the approximate memory used by that key. --bytes C and '--largest N can be used to limit output to keys larger than C bytes, or the N largest keys.
The generated CSV has the following columns - Database Number, Data Type, Key, Memory Used in bytes and RDB Encoding type.
Memory usage includes the key, the value and any other overheads.
Note that the memory usage is approximate. In general, the actual memory used will be slightly higher than what is reported.
You can filter the report on keys or database number or data type.
The memory report should help you detect memory leaks caused by your application logic. It will also help you optimize Redis memory usage.
Find Memory used by a Single Key
Sometimes you just want to find the memory used by a particular key, and running the entire memory report on the dump file is time consuming.
In such cases, you can use the redis-memory-for-key command:
> redis-memory-for-key person:1
> redis-memory-for-key -s localhost -p 6379 -a mypassword person:1
Key person:1
Bytes 111
Type hash
Encoding ziplist
Number of Elements 2
Length of Largest Element 8
NOTE :
This was added to redis-rdb-tools version 0.1.3
This command depends redis-py package
Comparing RDB files
First, use the --command diff option, and pipe the output to standard sort utility
You can pipe the output to netcat and re-import a subset of the data.
For example, if you want to shard your data into two redis instances, you can use the --key flag to select a subset of data,
and then pipe the output to a running redis instance to load that data.
Read Redis Mass Insert for more information on this.
When printing protocol output, the --escape option can be used with printable or utf8 to avoid non printable/control characters.
By default, expire times are emitted verbatim if they are present in the rdb file, causing all keys that expire in the past to be removed.
If this behaviour is unwanted the -x/--no-expire option will ignore all key expiry commands.
Otherwise you may want to set an expiry time in the future with -a/--amend-expire option which adds an integer number of seconds to the expiry time of each key which is already set to expire.
This will not change keys that do not already have an expiry set.
Using the Parser
from rdbtools import RdbParser, RdbCallback
from rdbtools.encodehelpers import bytes_to_unicode
class MyCallback(RdbCallback):
''' Simple example to show how callback works.
See RdbCallback for all available callback methods.
See JsonCallback for a concrete example
'''
def __init__(self):
super(MyCallback, self).__init__(string_escape=None)
def encode_key(self, key):
return bytes_to_unicode(key, self._escape, skip_printable=True)
def encode_value(self, val):
return bytes_to_unicode(val, self._escape)
def set(self, key, value, expiry, info):
print('%s = %s' % (self.encode_key(key), self.encode_value(value)))
def hset(self, key, field, value):
print('%s.%s = %s' % (self.encode_key(key), self.encode_key(field), self.encode_value(value)))
def sadd(self, key, member):
print('%s has {%s}' % (self.encode_key(key), self.encode_value(member)))
def rpush(self, key, value):
print('%s has [%s]' % (self.encode_key(key), self.encode_value(value)))
def zadd(self, key, score, member):
print('%s has {%s : %s}' % (str(key), str(member), str(score)))
callback = MyCallback()
parser = RdbParser(callback)
parser.parse('/var/redis/6379/dump.rdb')
Other Pages
Frequently Asked Questions
Redis Dump File Specification
Redis Dump File Version History - this also has notes on converting a dump file to an older version.
License
rdbtools is licensed under the MIT License. See LICENSE
Does sripathikrishnan/redis-rdb-tools have any tags?
TopGit's last sync did not record any GitHub topics for sripathikrishnan/redis-rdb-tools. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on sripathikrishnan/redis-rdb-tools?
The most recent commit recorded on sripathikrishnan/redis-rdb-tools was 7 months ago, based on the GitHub push timestamp. The repository has 743 forks — one of the better signals of community interest.
How many stars does sripathikrishnan/redis-rdb-tools have?
sripathikrishnan/redis-rdb-tools has 5.2k GitHub stars — refresh the page for the live number, or check github.com/sripathikrishnan/redis-rdb-tools. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is sripathikrishnan/redis-rdb-tools written in?
sripathikrishnan/redis-rdb-tools is written primarily in Python. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about sripathikrishnan/redis-rdb-tools?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/sripathikrishnan/redis-rdb-tools is the definitive source.
Read full README in the tab above.
Curious whether redis-rdb-tools is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about redis-rdb-tools.