- Falls back to mysql handler if it can't connect to Redis. Mysql handler falls back to file handler.
- When a session's data size exceeds the compression threshold the session data will be compressed.
- Compression libraries supported are 'gzip', 'lzf', 'lz4', and 'snappy'. -- Gzip is the slowest but offers the best compression ratios. -- Lzf can be installed easily via PECL. -- Lz4 is supported by HHVM.
- Compression can be enabled, disabled, or reconfigured on the fly with no loss of session data.
- Expiration is handled by Redis; no garbage collection needed.
- Logs when sessions are not written due to not having or losing their lock.
- Limits the number of concurrent lock requests before a 503 error is returned.
- Detects inactive waiting processes to prevent false-positives in concurrency throttling.
- Detects crashed processes to prevent session deadlocks (Linux only).
- Gives shorter session lifetimes to bots and crawlers to reduce wasted resources.
- Locking can be disabled entirely using config or
define('CM_REDISSESSION_LOCKING_ENABLED', FALSE);or by setting
$this->setFlag('', Cm_RedisSession_Model_Session::FLAG_READ_ONLY, 1)flag in controller predispatch.
- Requires PHP >= 5.3. Yes, this is a feature. You're welcome. ;)
- Only one process may get a write lock on a session.
- A process may lose it's lock if another process breaks it, in which case the session will not be written.
- The lock may be broken after
BREAK_AFTERseconds and the process that gets the lock is indeterminate.
MAX_CONCURRENCYprocesses may be waiting for a lock for the same session or else a 503 error is returned.
The Cookie Lifetime is configured here (Magento default): System > Configuration > Web > Session Cookie Management > Cookie Lifetime.
You can override the default session lifetime settings of this module by setting the
<min_lifetime> handle if you need to adjust your session lifetime settings.
Be aware that if the
<max_lifetime> setting is below your Cookie Lifetime, the
<max_lifetime>-setting will be taken.
This extension can be installed with either Composer or modman.
Important: The 3.0.0 release is packaged exclusively as a composer module and cannot be installed with modman. If you do not use composer stick with the 2.x release.
The Magento Compiler feature is currently not supported.
Install module using modman:
modman clone https://github.com/colinmollenhour/Cm_RedisSession
If you want to install a specific version, you can add
-- --branch x.y.zto the command.
Configure via app/etc/local.xml adding a
global/redis_sessionsection with the appropriate configuration if needed. See the "Configuration Example" below.
Refresh the config cache to allow the module to be installed by Magento.
Test the configuration by running the migrateSessions.php script in
sudo php .modman/Cm_RedisSession/migrateSessions.php --test
global/session_saveconfiguration to "db" in app/etc/local.xml. The "db" value is the MySQL handler, but Cm_RedisSession overrides it to avoid modifying core files.
Migrate the old sessions to Redis. See the "Migration" section below for details. The migration script will clear the config cache after migration is complete to activate the config change made in step 5.
<config> <global> ... <session_save>db</session_save> <redis_session> <!-- All options seen here are the defaults --> <host>127.0.0.1</host> <!-- Specify an absolute path if using a unix socket --> <port>6379</port> <password></password> <!-- Specify if your Redis server requires authentication --> <timeout>2.5</timeout> <!-- This is the Redis connection timeout, not the locking timeout --> <persistent></persistent> <!-- Specify unique string to enable persistent connections. E.g.: sess-db0; bugs with phpredis and php-fpm are known: https://github.com/nicolasff/phpredis/issues/70 --> <db>0</db> <!-- Redis database number; protection from accidental loss is improved by using a unique DB number for sessions --> <compression_threshold>2048</compression_threshold> <!-- Known bug with strings over 64k: https://github.com/colinmollenhour/Cm_Cache_Backend_Redis/issues/18 --> <compression_lib>gzip</compression_lib> <!-- gzip, lzf, lz4, snappy or none to disable compression --> <log_level>1</log_level> <!-- 0 (emergency: system is unusable), 4 (warning; additional information, recommended), 5 (notice: normal but significant condition), 6 (info: informational messages), 7 (debug: the most information for development/testing) --> <max_concurrency>6</max_concurrency> <!-- maximum number of processes that can wait for a lock on one session; for large production clusters, set this to at least 10% of the number of PHP processes --> <break_after_frontend>5</break_after_frontend> <!-- seconds to wait for a session lock in the frontend; not as critical as admin --> <fail_after>10</fail_after> <!-- seconds after which we bail from attempting to obtain lock (in addition to break after time) --> <break_after_adminhtml>30</break_after_adminhtml> <first_lifetime>600</first_lifetime> <!-- Lifetime of session for non-bots on the first write. 0 to disable --> <bot_first_lifetime>60</bot_first_lifetime> <!-- Lifetime of session for bots on the first write. 0 to disable --> <bot_lifetime>7200</bot_lifetime> <!-- Lifetime of session for bots on subsequent writes. 0 to disable --> <disable_locking>0</disable_locking> <!-- Disable session locking entirely. --> <min_lifetime>60</min_lifetime> <!-- Set the minimum session lifetime --> <max_lifetime>2592000</max_lifetime> <!-- Set the maximum session lifetime --> <log_exceptions>0</log_exceptions> <!-- Log connection failure and concurrent connection exceptions in exception.log. --> </redis_session> ... </global> ... </config>
A script is included to make session migration from files storage to Redis with minimal downtime very easy. Use a shell script like this for step 6 of the "Installation" section.
cd /var/www # Magento installation root touch maintenance.flag # Enter maintenance mode sleep 2 # Allow any running processes to complete # This will copy sessions into redis and clear the config cache so local.xml changes will take effect sudo php .modman/Cm_RedisSession/migrateSessions.php -y rm maintenance.flag # All done, exit maintenance mode
Depending on your server setup this may require some changes. Old sessions are not deleted so you can run it again
if there are problems. The migrateSessions.php script has a
--test mode which you definitely should use before
the final migration. Also, the
--test mode can be used to compare compression performance and ratios. Last but
not least, the
--test mode will tell you roughly how much space your compressed sessions will consume so you know
roughly how to configure
maxmemory if needed. All sessions have an expiration so
are both good
Session data compresses very well so using compression is a great way to increase your capacity without
dedicating a ton of RAM to Redis and reducing network utilization.
compression threshold is 2048 bytes so any session data equal to or larger than this size
will be compressed with the chosen
compression_lib which is
gzip by default. Compression can be disabled by setting the
none. However, both
snappy offer much faster compression with comparable compression ratios so I definitely recommend using
one of these if you have root. lzf is easy to install via pecl:
sudo pecl install lzf
NOTE: If using suhosin with session data encryption enabled (default is
suhosin.session.encrypt=on), two things:
- You will probably get very poor compression ratios.
- Lzf fails to compress the encrypted data in my experience. No idea why...
If any compression lib fails to compress the session data an error will be logged in
system.log and the
session will still be saved without compression. If you have
suhosin.session.encrypt=on I would either
recommend disabling it (unless you are on a shared host since Magento does it's own session validation already)
or disable compression or at least don't use lzf with encryption enabled.
Using Cm_RedisSession alongside Cm_Cache_Backend_Redis should be no problem at all. The main thing to keep in mind is that if both the cache and the sessions are using the same database, flushing the cache backend would also flush the sessions! So, don't use the same 'db' number for both if running only one instance of Redis. However, using a separate Redis instance for each is recommended to make sure that one or the other can't run wild consuming space and cause evictions for the other. For example, configure two instances each with 100M maxmemory rather than one instance with 200M maxmemory.
@copyright Copyright (c) 2013 Colin Mollenhour (http://colin.mollenhour.com) This project is licensed under the "New BSD" license (see source).