<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Qlik Sense Uses Round Robin User Balancing during a multi node install in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31098#M2107</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a Confirmation from Qlik that - In the case of Multi Node Installation, the Current User Load Balancing Methodology in Sense Uses Round Robin instead of going to the Node where the app is already open in Memory and this would be fixed in the upcoming releases.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Jun 2018 02:40:30 GMT</pubDate>
    <dc:creator>phaniskaja</dc:creator>
    <dc:date>2018-06-15T02:40:30Z</dc:date>
    <item>
      <title>Qlik Sense Uses Round Robin User Balancing during a multi node install</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31097#M2106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see Qlik Sense Uses Round Robin in a multi node install until Feb 2018 SR1 release.&lt;/P&gt;&lt;P&gt;Is this fixed in April 2018 release or is their a setting that we need to do to have the new user direct to the Node that already has the app open with all the Cached App components in the engine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ Appreciate your inputs on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Phani Kaja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Apr 2018 02:55:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31097#M2106</guid>
      <dc:creator>phaniskaja</dc:creator>
      <dc:date>2018-04-28T02:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Uses Round Robin User Balancing during a multi node install</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31098#M2107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a Confirmation from Qlik that - In the case of Multi Node Installation, the Current User Load Balancing Methodology in Sense Uses Round Robin instead of going to the Node where the app is already open in Memory and this would be fixed in the upcoming releases.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 02:40:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31098#M2107</guid>
      <dc:creator>phaniskaja</dc:creator>
      <dc:date>2018-06-15T02:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Uses Round Robin User Balancing during a multi node install</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31099#M2108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any update on Qlik sense June 2018 version ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Clark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2018 12:04:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-Uses-Round-Robin-User-Balancing-during-a-multi-node/m-p/31099#M2108</guid>
      <dc:creator>millan123</dc:creator>
      <dc:date>2018-08-20T12:04:20Z</dc:date>
    </item>
  </channel>
</rss>

