<?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: mvexpand in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609449#M13633</link>
    <description>&lt;P&gt;mvexpand functionality can be replicated to some extent using makecontinuous&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Enterprise/Mutlivalue-Field-Problem-Is-there-any-way-to-do-this-without/m-p/608898/highlight/true?search-action-id=87185142412&amp;amp;search-result-uid=608898#M13589" target="_blank"&gt;https://community.splunk.com/t5/Splunk-Enterprise/Mutlivalue-Field-Problem-Is-there-any-way-to-do-this-without/m-p/608898/highlight/true?search-action-id=87185142412&amp;amp;search-result-uid=608898#M13589&lt;/A&gt;&lt;/P&gt;&lt;P&gt;However, you may still run into memory issues.&lt;/P&gt;&lt;P&gt;The memory issue can be postponed by configuring more memory in limits.conf&lt;/P&gt;</description>
    <pubDate>Mon, 15 Aug 2022 08:08:09 GMT</pubDate>
    <dc:creator>ITWhisperer</dc:creator>
    <dc:date>2022-08-15T08:08:09Z</dc:date>
    <item>
      <title>Receiving error while using mvexpand</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609445#M13631</link>
      <description>&lt;P&gt;While using the&lt;STRONG&gt; mvexpand&amp;nbsp;&lt;/STRONG&gt;command, i am getting the below error.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;ERROR -&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;command.mvexpand: output will be truncated at 1000 results due to excessive memory usage. Memory threshold of 500 MB as configured in limits.conf /[mvexpand]/max_mem_usage_mb has been reached.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Question 1&lt;/STRONG&gt;- How can i resolve the above error ?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Question 2&lt;/STRONG&gt; -&amp;nbsp; Is there any other alternative command of mvexpand ?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 13:51:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609445#M13631</guid>
      <dc:creator>super_saiyan</dc:creator>
      <dc:date>2022-08-15T13:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: mvexpand</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609449#M13633</link>
      <description>&lt;P&gt;mvexpand functionality can be replicated to some extent using makecontinuous&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Enterprise/Mutlivalue-Field-Problem-Is-there-any-way-to-do-this-without/m-p/608898/highlight/true?search-action-id=87185142412&amp;amp;search-result-uid=608898#M13589" target="_blank"&gt;https://community.splunk.com/t5/Splunk-Enterprise/Mutlivalue-Field-Problem-Is-there-any-way-to-do-this-without/m-p/608898/highlight/true?search-action-id=87185142412&amp;amp;search-result-uid=608898#M13589&lt;/A&gt;&lt;/P&gt;&lt;P&gt;However, you may still run into memory issues.&lt;/P&gt;&lt;P&gt;The memory issue can be postponed by configuring more memory in limits.conf&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 08:08:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609449#M13633</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2022-08-15T08:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: mvexpand</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609463#M13634</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/244498"&gt;@super_saiyan&lt;/a&gt;&amp;nbsp;- Generally you should look at the option of changing your query in such a way that you do not require to use mvexpand. (Avoid multi-valued fields where you expect to have more than 1000 values.)&lt;/P&gt;&lt;P&gt;If not possible, then you can look at the option provided by&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/225168"&gt;@ITWhisperer&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps!!!&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 11:15:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609463#M13634</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-08-15T11:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: mvexpand</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609467#M13637</link>
      <description>&lt;P&gt;You can raise the limits of course to delay the onset of the problem a little, as others already mention. But the question is why do you have such a big mvexpand. If you're mvexpanding original events, maybe it's worth reviewing onboarding of this sourcetype. If it's because you did some huge "stats values" or something similar, maybe you should review your search and try to get to the results another way.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 11:26:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Receiving-error-while-using-mvexpand/m-p/609467#M13637</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-08-15T11:26:33Z</dc:date>
    </item>
  </channel>
</rss>

