<?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 What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enforce-counts' does? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192904#M38473</link>
    <description>&lt;P&gt;Does anybody know what parameters I should pass to the REST API endpoint &lt;STRONG&gt;/services/cluster/slave/control/control/decommission&lt;/STRONG&gt;  to archive the same thing that command '&lt;STRONG&gt;splunk offline --enforce-counts&lt;/STRONG&gt;' does?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jan 2015 00:13:33 GMT</pubDate>
    <dc:creator>rongshengfang</dc:creator>
    <dc:date>2015-01-14T00:13:33Z</dc:date>
    <item>
      <title>What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enforce-counts' does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192904#M38473</link>
      <description>&lt;P&gt;Does anybody know what parameters I should pass to the REST API endpoint &lt;STRONG&gt;/services/cluster/slave/control/control/decommission&lt;/STRONG&gt;  to archive the same thing that command '&lt;STRONG&gt;splunk offline --enforce-counts&lt;/STRONG&gt;' does?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2015 00:13:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192904#M38473</guid>
      <dc:creator>rongshengfang</dc:creator>
      <dc:date>2015-01-14T00:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enforce-counts' does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192905#M38474</link>
      <description>&lt;P&gt;Bumping this because I'd really like to know the answer.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2016 16:56:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192905#M38474</guid>
      <dc:creator>jacobwilkins</dc:creator>
      <dc:date>2016-11-30T16:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enforce-counts' does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192906#M38475</link>
      <description>&lt;P&gt;Through some testing, it seems that &lt;CODE&gt;enforce_counts=true&lt;/CODE&gt; might be the correct POST parameter.&lt;/P&gt;

&lt;P&gt;It would be nice if someone from Splunk could confirm.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2016 17:05:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192906#M38475</guid>
      <dc:creator>jacobwilkins</dc:creator>
      <dc:date>2016-11-30T17:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enforce-counts' does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192907#M38476</link>
      <description>&lt;P&gt;Greeting from the future,&lt;/P&gt;

&lt;P&gt;according to the latest docs &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTcluster#cluster.2Fslave.2Fcontrol.2Fcontrol.2Fdecommission"&gt;https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTcluster#cluster.2Fslave.2Fcontrol.2Fcontrol.2Fdecommission&lt;/A&gt; it is like this :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k -u admin:pass &lt;A href="https://indexer:8089/services/cluster/slave/control/control/decommission" target="test_blank"&gt;https://indexer:8089/services/cluster/slave/control/control/decommission&lt;/A&gt; -X POST
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 23:42:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/192907#M38476</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-03-26T23:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: What parameters should I pass to this Splunk REST API endpoint to archive the same thing that 'splunk offline --enfo</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/600366#M104670</link>
      <description>&lt;P&gt;I've tested and confirmed that when you add the &lt;FONT face="courier new,courier"&gt;enforce_counts=true&lt;/FONT&gt; to the api call like seen below, it will perform a full decommissioning of the host. Thank you for bringing it up!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -k -u admin:pass https://indexer:8089/services/cluster/slave/control/control/decommission -d enforce_counts=true -X POST&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 23:00:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-parameters-should-I-pass-to-this-Splunk-REST-API-endpoint/m-p/600366#M104670</guid>
      <dc:creator>melcher</dc:creator>
      <dc:date>2022-06-02T23:00:56Z</dc:date>
    </item>
  </channel>
</rss>

