<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:56 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-1589] Current raft implementation seems to be unstable when dynamically adding peers when new nodes come up.</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1589</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Scenario were trying to do:&lt;/p&gt;

&lt;p&gt;We want to have a shard started with replicas on all cluster members(even ones added at any time in the future).&lt;/p&gt;


&lt;p&gt;Currently the raft implementation seems to quite fragile when dynamically adding peers, when you send an AddServer message to the actor on MemberUp/Reachable events the followers seem to always ignore it leading to each peer having different set of peers which leads to never ending elections.&lt;br/&gt;
The current implementation seems to rely either on having hardcoded replicas in the module conf. If we went similar route like the ClusterAdminService addReplica does this also seems to only update peers on the leader which leads to the neverending elections due to different peers for each actor.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26143">CONTROLLER-1589</key>
            <summary>Current raft implementation seems to be unstable when dynamically adding peers when new nodes come up.</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="tcere">Tomas Cere</reporter>
                        <labels>
                    </labels>
                <created>Fri, 27 Jan 2017 16:11:15 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:20 +0000</updated>
                            <resolved>Thu, 13 Apr 2017 12:42:09 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="51732" author="rovarga" created="Tue, 31 Jan 2017 16:28:10 +0000"  >&lt;p&gt;Based on the discussion on Clustering Hackers&apos; call, the configuration update should work as follows:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;ShardManager creates the local replica&lt;/li&gt;
	&lt;li&gt;ShardManager sends AddServer to the leader&lt;/li&gt;
	&lt;li&gt;The leader will catch up the new follower via a ApplySnapshot&lt;/li&gt;
	&lt;li&gt;It then updates its configuration and replicates to all followers&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;So sending AddServer to followers should not be necessary.&lt;/p&gt;</comment>
                            <comment id="51733" author="tpantelis" created="Thu, 16 Feb 2017 05:34:00 +0000"  >&lt;p&gt;Is there an actual issue here or can we close this?&lt;/p&gt;</comment>
                            <comment id="51734" author="jmorvay@cisco.com" created="Thu, 16 Feb 2017 10:45:21 +0000"  >&lt;p&gt;Hi Tom,&lt;/p&gt;

&lt;p&gt;I have tried approach mentioned above and I have been able to add new shards. However, I have seen some problems with creating shards in some scenarios, possibly, because of bugs in our shard starting logic.&lt;/p&gt;

&lt;p&gt;I will try to fix them and will see if this is an actual issue. If not I will close the bug.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="26142">CONTROLLER-1588</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7696</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=7696]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02ri7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>