<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sentinel</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>e21e0ba3 - Sentinel test: more correct sentinels config reset.</title>
        <link>http://172.16.0.5:8080/history/redis-3.2.3/tests/sentinel/#e21e0ba3</link>
        <description>Sentinel test: more correct sentinels config reset.In the initialization test for each instance we used to unregister theold master and register it again to clear the config.However there is a race condition doing this: as soon as we unregisterand re-register &quot;mymaster&quot;, another Sentinel can update the newconfiguration with the old state because of gossip &quot;hello&quot; messages.So the correct procedure is instead, unregister &quot;mymaster&quot; from all thesentinel instances, and re-register it everywhere again.

            List of files:
            /redis-3.2.3/tests/sentinel/tests/includes/init-tests.tcl</description>
        <pubDate>Mon, 23 Jun 2014 12:00:00 +0000</pubDate>
        <dc:creator>antirez &lt;antirez@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
