<?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 nfs failure behaviors in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/nfs-failure-behaviors/m-p/48058#M70090</link>
    <description>&lt;P&gt;If you're using nfs for cold, and the nfs goes away for awhile, what happens? &lt;/P&gt;

&lt;P&gt;What happens to rolling? &lt;/P&gt;

&lt;P&gt;Does Splunk just sit on the buckets in hot/warm until it can copy them? &lt;/P&gt;

&lt;P&gt;What about searches that involve these buckets that are now in limbo?&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jul 2011 16:11:08 GMT</pubDate>
    <dc:creator>vbumgarner</dc:creator>
    <dc:date>2011-07-25T16:11:08Z</dc:date>
    <item>
      <title>nfs failure behaviors</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/nfs-failure-behaviors/m-p/48058#M70090</link>
      <description>&lt;P&gt;If you're using nfs for cold, and the nfs goes away for awhile, what happens? &lt;/P&gt;

&lt;P&gt;What happens to rolling? &lt;/P&gt;

&lt;P&gt;Does Splunk just sit on the buckets in hot/warm until it can copy them? &lt;/P&gt;

&lt;P&gt;What about searches that involve these buckets that are now in limbo?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2011 16:11:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/nfs-failure-behaviors/m-p/48058#M70090</guid>
      <dc:creator>vbumgarner</dc:creator>
      <dc:date>2011-07-25T16:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: nfs failure behaviors</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/nfs-failure-behaviors/m-p/48059#M70091</link>
      <description>&lt;P&gt;This probably depends, in part, on how your NFS is configured.  An NFS hard mount that is unresponsive could freeze your splunkd -- or at least one or more threads -- until the NFS server does respond again.  A soft mount would return an error back to splunk, which may be the more interesting case for your question.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2011 17:15:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/nfs-failure-behaviors/m-p/48059#M70091</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-07-25T17:15:59Z</dc:date>
    </item>
  </channel>
</rss>

