mirror of
https://github.com/predis/predis.git
synced 2026-10-14 07:47:49 +00:00
Daniele Alessandri
7664f1f29b
Predis\Client now requires a list of connection parameters pointing to sentinel instances and mandatory options "replication" and "service" set respectively to "sentinel" and the chosen name for the master instance. $sentinels = ['tcp://127.0.0.1:5381', 'tcp://127.0.0.1:5382']; $options = ['replication' => 'sentinel', 'service' => 'mymaster']; $client = new Predis\Client($sentinels, $options); Despite being nice and clean on the outside I am not really fond of the code being used internally to make this kind of configuration possible. Improvements in this respect would require a few breaking changes (not even an option for a minor release) so things will change for the good with Predis 2.0.
61 lines
2.1 KiB
PHP
61 lines
2.1 KiB
PHP
<?php
|
|
|
|
/*
|
|
* This file is part of the Predis package.
|
|
*
|
|
* (c) Daniele Alessandri <suppakilla@gmail.com>
|
|
*
|
|
* For the full copyright and license information, please view the LICENSE
|
|
* file that was distributed with this source code.
|
|
*/
|
|
|
|
require __DIR__.'/shared.php';
|
|
|
|
// Predis supports redis-sentinel to provide high availability in master / slave
|
|
// scenarios. The only but relevant difference with a basic replication scenario
|
|
// is that sentinel servers can manage the master server and its slaves based on
|
|
// their state, which means that they are able to provide an authoritative and
|
|
// updated configuration to clients thus avoiding static configurations for the
|
|
// replication servers and their roles.
|
|
|
|
use Predis\Connection\Aggregate\SentinelReplication;
|
|
|
|
// Instead of connection parameters pointing to redis nodes, we provide a list
|
|
// of instances of redis-sentinel. Users should always provide a timeout value
|
|
// low enough to not hinder operations just in case a sentinel is unreachable
|
|
// but Predis uses a default value of 100 milliseconds for sentinel parameters
|
|
// without an explicit timeout value.
|
|
//
|
|
// NOTE: in real-world scenarios sentinels should be running on different hosts!
|
|
$sentinels = array(
|
|
'tcp://127.0.0.1:5380?timeout=0.100',
|
|
'tcp://127.0.0.1:5381?timeout=0.100',
|
|
'tcp://127.0.0.1:5382?timeout=0.100',
|
|
);
|
|
|
|
$client = new Predis\Client($sentinels, array(
|
|
'replication' => 'sentinel',
|
|
'service' => 'mymaster',
|
|
));
|
|
|
|
// Read operation.
|
|
$exists = $client->exists('foo') ? 'yes' : 'no';
|
|
$current = $client->getConnection()->getCurrent()->getParameters();
|
|
echo "Does 'foo' exist on {$current->alias}? $exists.", PHP_EOL;
|
|
|
|
// Write operation.
|
|
$client->set('foo', 'bar');
|
|
$current = $client->getConnection()->getCurrent()->getParameters();
|
|
echo "Now 'foo' has been set to 'bar' on {$current->alias}!", PHP_EOL;
|
|
|
|
// Read operation.
|
|
$bar = $client->get('foo');
|
|
$current = $client->getConnection()->getCurrent()->getParameters();
|
|
echo "We fetched 'foo' from {$current->alias} and its value is '$bar'.", PHP_EOL;
|
|
|
|
/* OUTPUT:
|
|
Does 'foo' exist on slave? yes.
|
|
Now 'foo' has been set to 'bar' on master!
|
|
We fetched 'foo' from master and its value is 'bar'.
|
|
*/
|