Is this also the case if you kill a topology or the machine goes down? Or do I need to write a jvm hook to handle this? But in any case, is there a way to know which files are in use by storm (as I said fuser and lsof are not of no help here).
thanks. On Wed, Mar 4, 2015 at 11:34 AM, Bobby Evans <ev...@yahoo-inc.com.invalid> wrote: > Storm is supposed to be cleaning them up itself. The supervisor is > supposed to know when a topology is no longer needed and remove them after > a specific timeout. If this is not happening for you there may be a bug in > the code. Could you file a JIRA and post the JIRA number here. If you > could include the version number of storm and any logs you have from the > supervisor that would be helpful. I cannot guarantee how quickly the > community can get to this though. > - Bobby > > > On Tuesday, March 3, 2015 4:39 PM, clay teahouse < > clayteaho...@gmail.com> wrote: > > > Hi all, > How do I remove storm generated system files programmatically without > stepping over the files that I shouldn't be deleting? I need this to > cleanup the files left behind from the aborted topologies. I tried fuser > and lsof, but with no luck. For example, fuser shows stormconf.ser and > stormcode.ser not in use even in cases where these files are being used. > thanksClay > > > >
