Redis 2.6.1 has been released

Redis 2.6 has been released and a new version is already out: Redis 2.6.1 fixing a bug preventing compilation on pretty old Linux systems that are still pretty widespread (RHLE5 & similar)

 

Scripting, bitops, and all big features are part of the Redis 2.6, main features added:

 

  • Server side Lua scripting, see http://redis.io/commands/eval
  • Virtual Memory removed (was deprecated in 2.4)
  • Hardcoded limits about max number of clients removed.
  • AOF low level semantics is generally more sane, and especially when used  in slaves.
  • Milliseconds resolution expires, also added new commands with milliseconds  precision (PEXPIRE, PTTL, …).
  • Better memory usage for “small” lists, ziplists and hashes when fields or  values contain small integers.
  • Read only slaves.
  • New bit opeations: BITCOUNT and BITOP commands.
  • Clients max output buffer soft and hard limits. You can specifiy different  limits for different classes of clients (normal,pubsub,slave).
  • More incremental (less blocking) expired keys collection algorithm, in  practical terms this means that Redis is more responsive when a very  big number of keys expire about at the same time.
  • AOF is now able to rewrite aggregate data types using variadic commands,  often producing an AOF that is faster to save, load, and is smaller in size.
  • Every redis.conf directive is now accepted as a command line option for the  redis-server binary, with the same name and number of arguments.
  • Hash table seed randomization for protection against collisions attacks.
  • Performances improved when writing large objects to Redis.
  • Integrated memory test, see redis-server –test-memory.
  • INCRBYFLOAT and HINCRBYFLOAT commands.
  • New DUMP, RESTORE, MIGRATE commands (back ported from Redis Cluster to 2.6).
  • CRC64 checksump in RDB files.
  • Better MONITOR output and behavior (now commands are logged before execution).
  • “Software Watchdog” feature to debug latency issues.
  • Significant parts of the core refactored or rewritten. New internal APIs  and core changes allowed to develop Redis Cluster on top of the new code,  however for 2.6 all the cluster code was removed, and will be released with  Redis 3.0 when it is more complete and stable.
  • Redis ASCII art logo added at startup.
  • Crash report on memory violation or failed asserts improved significantly  to make debugging of hard to catch bugs simpler.
  • redis-benchmark improvements: ability to run selected tests,  CSV output, faster, better help.
  • redis-cli improvements: –eval for comfortable development of Lua scripts.
  • SHUTDOWN now supports two optional arguments: “SAVE” and “NOSAVE”.
  • INFO output split into sections, the command is now able to just show  pecific sections.
  • New statistics about how many time a command was called, and how much  execution time it used (INFO commandstats).
  • More predictable SORT behavior in edge cases.
  • Better support for big endian and *BSD systems.

 

Download 

Release notes 

 

Future road maps includes:

  • Redis Sentinel
  • Redis Cluster
  • Redis 2.8

 

 

Indeed Redis @Instagram

Today in a great article Instragram what powers their platform: Hundreds of Instances and Dozens of Technologies … of which Redis.

 

We also use Redis extensively; it powers our main feed, our activity feed, our sessions system (here’s our Django session backend), and other related systems. All of Redis’ data needs to fit in memory, so we end up running several Quadruple Extra-Large Memory instances for Redis, too, and occasionally shard across a few Redis instances for any given subsystem. We run Redis in a master-replica setup, and have the replicas constantly saving the DB out to disk, and finally use EBS snapshots to backup those DB dumps (we found that dumping the DB on the master was too taxing). Since Redis allows writes to its replicas, it makes for very easy online failover to a new Redis machine, without requiring any downtime.
 
 

Read the full article here

Redis 2.4.15 has been released

Redis 2.4.15 has been released. Here is the short changelog :

  • [BUGFIX] Jemalloc updated to 3.0.0. This fixes a possibly AOF rewrite issue. See issue #504 for info.

 

Download

RedisLive the Redis dashboard

If you’re looking for something to get a better feeling about what’s going on with your Redis server, RedisLive is out and lets you visualize your Redis instances, analyze query patterns and spikes. Its open source and freely available at Github.

https://github.com/kumarnitin/RedisLive

 

Redis 2.6 Release Candidate 4 has been released

Redis 2.5.10 aka 2.6 Release Candidate 4 has been released and is available for download.

Changes:

  • BUGFIX Allow PREFIX to be overwritten on “make install”.
  • BUGFIX Run the test with just one client if the computer is slow.
  • BUGFIX Event port support in our event driven libray.
  • BUGFIX Jemalloc updated to 3.0.0. This fixes a possibly AOF rewrite issue.
  • See https://github.com/antirez/redis/issues/504 for info.
  • BUGFIX Fixed issue #516: ZINTERSTORE / ZUNIONSTORE with mixed sets/zsets.
  • BUGFIX Set fd to writable when poll(2) detects POLLERR or POLLHUP event.
  • BUGFIX Fixed RESTORE hash failure (Issue #532).
  • IMPROVED Allow an AOF rewrite buffer > 2GB (Related to issue #504).
  • IMPROVED Server cron function frequency is now configurable (REDIS_HZ).
  • IMPROVED Better, less blocking expired keys collection algorithm.
  • FEATURE New commands: BITOP and BITCOUNT.
  • FEATURE redis-cli –pipe for mass import.

Redis 2.4.14 has been released

Redis 2.4.14 has been released with an upgrade urgency qualified as high, many non trivial bugs fixed in this release.

  • [BUGFIX] Fixed issue #518 (Redis 99% CPU when master down).
  • [BUGFIX] Fixed issue #516 (ZINTERSTORE mixing sets and zsets).
  • [BUGFIX] Fixed a bug in install_server.sh when using chkconfig
  • [BUGFIX] Fixes to –test-memory implementation.
  • [BUGFIX] Allow PREFIX to be overridden in Makefile.
  • [BUGFIX] The test is now more reliable on slow computers.
  • redis-cli –pipe mode, see http://redis.io/topics/mass-insert
  • Much better expired keys collection algorithm that makes the server much more responsive when a lot of keys are expiring at the same time.

 

Download from http://redis.io/download as usually

Microsoft Open Technologies released Redis on Windows

Microsoft Open Technologies released Redis on Windows

 

Microsoft has announced the release of an updated version of the Redis on Windows, the first deliverable from the company’s Microsoft Open Technologies subsidiary.

Redis is an open-source, networked, in-memory, key-value data store with optional durability. It is written in ANSI C. The development of Redis is sponsored by VMware. In a blog post, Claudio Caldato, principal program manager for Microsoft Open Technologies, said the unit’s first deliverable is “a new and significant iteration” of Redis on Windows.

“The major improvements in this latest version involve the process of saving data on disk,” Caldato said. “Redis on Linux uses an OS feature called Fork/Copy On Write. This feature is not available on Windows, so we had to find a way to be able to mimic the same behavior without changing completely the save-on-disk process so as to avoid any future integration issues with the Redis code.”

Thus, the new version of Redis on Windows implements the Copy On Write process at the application level: Instead of relying on the OS, Microsoft added code to Redis so that some data structures are duplicated in such a way that Redis can still serve requests from clients while saving data on disk (thus achieving the same effect that Fork/Copy On Write does automatically on Linux), Caldato said.

Developers can find the code for this new version on the new MS Open Techrepository in GitHub, which is currently the place to work on the Windows version of Redis as per guidance from Salvatore Sanfilippo, the original author of the project, Caldato said.

“We will also continue working with the community to create a solid Windows port,” he said. “We consider this not to be production-ready code, but a solid code base to be shared with the community to solicit feedback: as such, while we pursue stabilization, we are keeping the older version as default/stable on the GitHub repository. To try out the new code, please go to the bksavecow branch.”

Meanwhile, in the next few weeks, Microsoft plans to test the code extensively so that developers can use it for more serious testing, Caldato said.

Redis 2.6.0 RC1 have been released

Redis 2.6.0-RC1 have been released and can be downloaded here

Overview of new features and changes introduced in Redis 2.6.x:
  • Server side Lua scripting, see http://redis.io/commands/eval
  • Virtual Memory removed (was deprecated in 2.4)
  • Hardcoded limits about max number of clients removed.
  • AOF low level semantics is generally more sane, and especially when used in slaves.
  • Milliseconds resolution expires, also added new commands with milliseconds precision (PEXPIRE, PTTL, …).
  • Better memory usage for “small” lists, ziplists and hashes when fields or values contain small integers.
  • Read only slaves.
  • Clients max output buffer soft and hard limits. You can specifiy different limits for different classes of clients (normal,pubsub,slave).
  • AOF is now able to rewrite aggregate data types using variadic commands, often producing an AOF that is faster to save, load, and is smaller in size.
  • Every redis.conf directive is now accepted as a command line option for the redis-server binary, with the same name and number of arguments.
  • Hash table seed randomization for protection against collisions attacks.
  • Performances improved when writing large objects to Redis.
  • Integrated memory test, see redis-server –test-memory.
  • INCRBYFLOAT and HINCRBYFLOAT commands.
  • New DUMP, RESTORE, MIGRATE commands (back ported from Redis Cluster to 2.6).
  • CRC64 checksump in RDB files.
  • Better MONITOR output and behavior (now commands are logged before execution).
  • “Software Watchdog” feature to debug latency issues.
  • Significant parts of the core refactored or rewritten. New internal APIs and core changes allowed to develop Redis Cluster on top of the new code, however for 2.6 all the cluster code was removed, and will be released with Redis 3.0 when it is more complete and stable.
  • Redis ASCII art logo added at startup.
  • Crash report on memory violation or failed asserts improved significantly to make debugging of hard to catch bugs simpler.
  • redis-benchmark improvements: ability to run selected tests,CSV output, faster, better help.
  • redis-cli improvements: –eval for comfortable development of Lua scripts.
  • SHUTDOWN now supports two optional arguments: “SAVE” and “NOSAVE”.
  • INFO output split into sections, the command is now able to just show pecific sections.
  • New statistics about how many time a command was called, and how much execution time it used (INFO commandstats).
  • More predictable SORT behavior in edge cases.
  • Better support for big endian and *BSD systems.
  • Build system improved.

 

 

Redis 2.4.9 has been released

Redis 2.4.9 has been released bringing mostly new features and minor bug fixing.

 

  • [FEATURE] Redis server is now able to test your memory for broken RAM.

Usage: ./redis-server –test-memory <megabytes>.

  • [FEATURE] redis-benchmark backported from unstable. Pipelining, run selected

tests, and a few more features.

  • [BUGFIX] utils/install_server.sh script now works on Redhat / Centos.
  • [BUGFIX] Minor fix to redis-cli (github issue #306).

 

Download Redis 2.4.9

 

Hacker News NoSQL Mentions

Redis is a high performance key value store database, used at places like The Guardian. Like MongoDB it also includes messaging functionality for replication, which means it’s being used for developers for all kinds of stuff, not all what it was “intended” for.

Given that just a couple of hours ago I said MongoDB is emerging from the NoSQL pack I found the chart really interesting.

Sadly our Hacker News data is not up to date (also note the x axis is incorrectly labelled. its data for 2010-2011) but I will be looking to get a better handle on Redis, and its developer mindshare with some solid data points. Watch this space.

Read more:

 http://www.redmonk.com/jgovernor/2012/03/15/redis-utterly-killed-it-in-2010-check-out-the-growth-in-share-of-developer-conversation/#ixzz1pUgGvbLw