https://community.splunk.com/t5/Getting-Data-In/Splunk-5-0-4-migration-Should-the-forwarder-be-stopped-while/m-p/53377#M10288 <P>If you are using useAck=true then you should be OK. Otherwise you should stop the forwarder.</P> Tue, 03 Sep 2013 17:22:43 GMT lukejadamec 2013-09-03T17:22:43Z https://community.splunk.com/t5/Getting-Data-In/Splunk-5-0-4-migration-Should-the-forwarder-be-stopped-while/m-p/53376#M10287 <P>Hi Everyone,</P> <P>First a few words about my setup. <BR /> I have a distributed setup with the following nodes </P> <OL> <LI>Indexer</LI> <LI>Search Head</LI> <LI>Forwarder (Lets call this the 'Light Weight' forwarder )</LI> <LI>Job Scheduler</LI> </OL> <P>I have some devices whose logs are transferred using their forwarder (Lets call this the Universal Forwarder).</P> <P>The universal forwarder send the logs to the light weight forwarder which just pass them on to the indexer.</P> <P>Now, I am trying to migrate from Splunk 4.3 to Splunk 5.0. During this process, the splunk process on the indexer node should be stopped.</P> <P>My question is, should the light weight forwarder also be stopped while migrating the indexer to prevent data loss? Will splunk keep the data in the pipe of the light weight forwarder when the indexer is down or will it keep on sending resulting in data loss?</P> Tue, 03 Sep 2013 11:01:43 GMT https://community.splunk.com/t5/Getting-Data-In/Splunk-5-0-4-migration-Should-the-forwarder-be-stopped-while/m-p/53376#M10287 spiketide 2013-09-03T11:01:43Z https://community.splunk.com/t5/Getting-Data-In/Splunk-5-0-4-migration-Should-the-forwarder-be-stopped-while/m-p/53377#M10288 <P>If you are using useAck=true then you should be OK. Otherwise you should stop the forwarder.</P> Tue, 03 Sep 2013 17:22:43 GMT https://community.splunk.com/t5/Getting-Data-In/Splunk-5-0-4-migration-Should-the-forwarder-be-stopped-while/m-p/53377#M10288 lukejadamec 2013-09-03T17:22:43Z