Searched refs:masters (Results 1 – 4 of 4) sorted by relevance
| /redis-3.2.3/tests/cluster/ |
| H A D | cluster.tcl | 92 proc cluster_allocate_slaves {masters slaves} { 94 set master_id [expr {$j % $masters}] 95 set slave_id [cluster_find_available_slave $masters] 102 proc create_cluster {masters slaves} { 103 cluster_allocate_slots $masters 105 cluster_allocate_slaves $masters $slaves
|
| /redis-3.2.3/src/ |
| H A D | redis-trib.rb | 350 sorted = masters.sort{|a,b| 365 masters = 0 371 masters += 1 661 masters = [] 699 masters = interleaved.slice!(0, masters_count) 700 nodes_count -= masters.length 702 masters.each{|m| puts m} 708 masters.each_with_index{|n,masternum| 731 masters.each do |m| 1268 masters = @nodes.length/(@replicas+1) [all …]
|
| H A D | sentinel.c | 647 di = dictGetIterator(sentinel.masters); in sentinelGenerateInitialMonitorEvents() 1026 di = dictGetIterator(sentinel.masters); in sentinelTryConnectionSharing() 1060 di = dictGetIterator(sentinel.masters); in sentinelUpdateSentinelAddressInAllMasters() 1168 if (flags & SRI_MASTER) table = sentinel.masters; in createSentinelRedisInstance() 1354 ri = dictFetchValue(sentinel.masters,sdsname); in sentinelGetMasterByName() 1438 di = dictGetIterator(sentinel.masters); in sentinelResetMastersByPattern() 1708 di = dictGetIterator(sentinel.masters); in rewriteConfigSentinelOption() 3110 dict *masters_local = sentinel.masters; in sentinelCommand() 3247 dictSize(sentinel.masters), in sentinelInfoCommand() 3253 di = dictGetIterator(sentinel.masters); in sentinelInfoCommand() [all …]
|
| /redis-3.2.3/ |
| H A D | 00-RELEASENOTES | 56 2. Redis Sentinel, when monitoring multiple masters, could crash after 246 masters), a bug was introduced that mis-counted the number of pending 301 reconfigure back old masters to slaves after they are reachable again 1148 1/5 of all the cluster slots from master 0 to the other 4 masters and 1155 | New masters with slots are now targets of migration if others are. 1164 to other masters with non-zero nodes. However the old master now empty, 1170 are assigend with their first slot, if other masters in the cluster have 1670 * [NEW] Better consistency behavior between masters and slaves for expired 1693 * [NEW] CLIENT KILL TYPE MASTER, to kill (disconnect) masters from slaves. 1718 monitor many masters. (Salvatore Sanfilippo)
|