<?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 Splunk logs : After randomization, why current is first in the list swapping with last item? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logs-After-randomization-why-current-is-first-in-the-list/m-p/630253#M108038</link>
    <description>&lt;P&gt;Splunkd logs - in universal forwarder I notice,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;INFO  AutoLoadBalancedConnectionStrategy [XXXXX TcpOutEloop] - After randomization, current is first in the list. Swapping with last item&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what is this log indicate ?&lt;/P&gt;</description>
    <pubDate>Thu, 09 Feb 2023 18:41:48 GMT</pubDate>
    <dc:creator>chimbudp</dc:creator>
    <dc:date>2023-02-09T18:41:48Z</dc:date>
    <item>
      <title>Splunk logs : After randomization, why current is first in the list swapping with last item?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logs-After-randomization-why-current-is-first-in-the-list/m-p/630253#M108038</link>
      <description>&lt;P&gt;Splunkd logs - in universal forwarder I notice,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;INFO  AutoLoadBalancedConnectionStrategy [XXXXX TcpOutEloop] - After randomization, current is first in the list. Swapping with last item&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what is this log indicate ?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 18:41:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-logs-After-randomization-why-current-is-first-in-the-list/m-p/630253#M108038</guid>
      <dc:creator>chimbudp</dc:creator>
      <dc:date>2023-02-09T18:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk logs : After randomization, current is first in the list. Swapping with last item</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logs-After-randomization-why-current-is-first-in-the-list/m-p/630254#M108039</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161095"&gt;@chimbudp&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This is just a notice. UF changes the indexer connection every 30 seconds as a default. &amp;nbsp;It selects the next indexer randomly. This log shows that the next selected indexer is the same as the current one, which is why changed with another one which is on the last in the list.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 10:13:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-logs-After-randomization-why-current-is-first-in-the-list/m-p/630254#M108039</guid>
      <dc:creator>scelikok</dc:creator>
      <dc:date>2023-02-09T10:13:09Z</dc:date>
    </item>
  </channel>
</rss>

