<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:19 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-1733] Add re-balancing of Entities</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1733</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;I have a cluster with three members and create six entities. Every cluster member registers these entities. When the cluster is running normally, each member owns two entities and the cluster is load balanced.&lt;br/&gt;
Situation one: I use Iptables command to isolate member1. Now member2 and member3 both own three entities and candidate member1 doesn&apos;t disappear. But when member1 is back to the cluster. It doesn&apos;t own any entity. So when the network shock happens, the load balanced can not guaranteed.&lt;br/&gt;
Situation two: When I kill and restart the app on member1. It doesn&apos;t own any entities too.&lt;/p&gt;

&lt;p&gt;Steps to reproduce,&lt;br/&gt;
1. Bring up a 3 node cluster&lt;br/&gt;
2. Kill the controller process for member-1.(Or isolate the member-1 network)&lt;br/&gt;
3. Now the member-2 and member-3 both have three entities. Candidate member-1 still alive but it doesn&apos;t own any entities.&lt;br/&gt;
4. Restart the member-1(Or recovery the member-1 network)&lt;br/&gt;
5. Member-1 still doesn&apos;t own any entities. Member-2 and Member-3 both own three entities. The load balanced is destroyed.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26287">CONTROLLER-1733</key>
            <summary>Add re-balancing of Entities</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</type>
                                                <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="m13269178667@163.com">hege</reporter>
                        <labels>
                    </labels>
                <created>Fri, 30 Jun 2017 07:07:38 +0000</created>
                <updated>Mon, 6 Sep 2021 09:02:40 +0000</updated>
                                            <version>Carbon</version>
                                                    <component>eos</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="52485" author="tpantelis" created="Fri, 30 Jun 2017 11:11:02 +0000"  >&lt;p&gt;The EOS does not load balance - the default policy is first-come, first server although there is an experimental policy to load-balance initial owner assignment. But once an owner is assigned, it stays assigned until it goes down or is isolated. Adding re-balancing, either via explicit user action or via some automated process, would be an enhancement (and we would need a contributor to implement it).&lt;/p&gt;</comment>
                            <comment id="52486" author="rovarga" created="Thu, 24 Aug 2017 12:48:48 +0000"  >&lt;p&gt;Yes, and can potentially wreck singleton service, so it needs to be a completely different policy.&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>8777</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=8777]]></customfieldvalue>

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

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

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