<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:53 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-1183] Clustering : When handling an append entry Follower should apply log to state machine only till it&apos;s current commit index</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1183</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;In Follower we apply log to state machine as follows,&lt;/p&gt;


&lt;p&gt;Line 219 : applyLogToStateMachine(appendEntries.getLeaderCommit());&lt;/p&gt;

&lt;p&gt;For a slow follower the leader commit may be far ahead of what is in it&apos;s log. This can cause the following message to get printed over and over in the logs.&lt;/p&gt;

&lt;p&gt;LOG.warn(&lt;br/&gt;
                        &quot;{}: Missing index {} from log. Cannot apply state. Ignoring {} to {}&quot;,&lt;br/&gt;
                        logName(), i, i, index);&lt;/p&gt;

&lt;p&gt;A simple fix for this may be to simply apply only the Followers commit index to the state machine.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25737">CONTROLLER-1183</key>
            <summary>Clustering : When handling an append entry Follower should apply log to state machine only till it&apos;s current commit index</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="10000">Done</resolution>
                                        <assignee username="tpantelis">Tom Pantelis</assignee>
                                    <reporter username="moraja@cisco.com">Moiz Raja</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 Mar 2015 01:59:26 +0000</created>
                <updated>Sat, 6 Jun 2015 18:52:09 +0000</updated>
                            <resolved>Sat, 6 Jun 2015 18:52:09 +0000</resolved>
                                    <version>Post-Helium</version>
                                                    <component>mdsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="50194" author="kramesha@cisco.com" created="Mon, 9 Mar 2015 23:11:56 +0000"  >&lt;p&gt;This happens for a slow follower.&lt;/p&gt;

&lt;p&gt;Whenever this happens, it means that the follower is trailing behind. &lt;/p&gt;

&lt;p&gt;Although we can remove this log and pass in the min(leadercommit, follower-lastindex) to the applystate, presence of this log indicates an issue.&lt;/p&gt;

&lt;p&gt;We need to come with a strategy to make a slow follower catch-up faster, possibly by sending multiple entries in 1 AE message.&lt;br/&gt;
Since we have the streaming solution now, I hope it should not cause any serialization issues.&lt;/p&gt;

&lt;p&gt;As i write this , i have an idle system with a slow inv-topology-follower at index 990 catching up to a leader (index 1213), and AE is coming in every 1 min!!&lt;br/&gt;
The mean-rate in the leader is 0.11 and Mean is 7.9.&lt;/p&gt;</comment>
                            <comment id="50195" author="tpantelis" created="Sun, 31 May 2015 18:55:45 +0000"  >&lt;p&gt;This can also happen when a node is (re)started with an empty journal, either when adding a new node to the cluster or re-installing a node from catastrophic failure. &lt;/p&gt;

&lt;p&gt;I think at the very least we can change the log from warn to debug - the message looks a little ominous in the log at warn level.&lt;/p&gt;

&lt;p&gt;I agree we should look into sending multiple entries in an AE message.&lt;/p&gt;</comment>
                            <comment id="50196" author="tpantelis" created="Tue, 2 Jun 2015 20:27:48 +0000"  >&lt;p&gt;Submitted draft &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/21701&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/21701&lt;/a&gt; to batch AppenEntries.&lt;/p&gt;</comment>
                    </comments>
                    <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>2787</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=2787]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10315"><![CDATA[Lithium]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10301"><![CDATA[Normal]]></customfieldvalue>

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

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