[ 
https://issues.apache.org/jira/browse/NIFI-13996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897292#comment-17897292
 ] 

Daniel Stieglitz edited comment on NIFI-13996 at 11/18/24 7:18 PM:
-------------------------------------------------------------------

So far I was able to identify and correct
 # TestPutSQL<some uuid>
 # zeroByte<some long number>.txt
 # Three files named with current system milliseconds
 # poifiles.
 # org.apache.nifi.processors.groovyx.ExecuteGroovyScriptTest<some long 
number>.tmp
 # PutHDFS_testPutFileFromLocalFile_<long number>
 # <current milliseconds><some long number> (2 directories)
 # zookeeper.configuration<some long number>.properties (16 files)

      But for the following I was able to identify where they are created but I 
am unsure how get  them to delete on exit:
 * operationId<some long number> files are created in 
TransferDebugOperationHandler line 147
 * InvokeHTTP<some long number> is created in InvokeHttp on line 1288-1290 
 * <some uuid><some long number>.tmp files are created in 
org.apache.nifi.minifi.c2.command.syncresource.DefaultSyncResourceStrategy 
specifically when method synchronizeResourceRepository is called (one of the 
low level private members it calls is method persistToTemporaryLocation where 
temp files are being created).
 * zookeeper.configuration<some long number>.properties are created when 
running TestZooKeeperStateProvider.

 


was (Author: JIRAUSER294662):
So far I was able to identify and correct
 # TestPutSQL<some uuid>
 # zeroByte<some long number>.txt
 # Three files named with current system milliseconds
 # poifiles.
 # org.apache.nifi.processors.groovyx.ExecuteGroovyScriptTest<some long 
number>.tmp
 # PutHDFS_testPutFileFromLocalFile_<long number>
 # <current milliseconds><some long number> (2 directories)
 # zookeeper.configuration<some long number>.properties

      But for the following I was able to identify where they are created but I 
am unsure how get  them to delete on exit:
 * operationId<some long number> files are created in 
TransferDebugOperationHandler line 147
 * InvokeHTTP<some long number> is created in InvokeHttp on line 1288-1290 
 * <some uuid><some long number>.tmp files are created in 
org.apache.nifi.minifi.c2.command.syncresource.DefaultSyncResourceStrategy 
specifically when method synchronizeResourceRepository is called (one of the 
low level private members it calls is method persistToTemporaryLocation where 
temp files are being created).
 * zookeeper.configuration<some long number>.properties are created when 
running TestZooKeeperStateProvider.

 

> Files being created in /tmp during a build not cleaned up afterwards
> --------------------------------------------------------------------
>
>                 Key: NIFI-13996
>                 URL: https://issues.apache.org/jira/browse/NIFI-13996
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>
> There seems to be quite a few directories and files created but never deleted 
> after running a 2.X build. 
>       Files where there are numerous instances of
>  # zookeeper.configuration<some long number>.properties (16 files)
>  # org.codehaus.plexus.compiler.javac.JavacCompiler<some long 
> number>arguments (TBD if that is coming from a Maven build or when building 
> in Intellij).
>  # org.apache.nifi.processors.groovyx.ExecuteGroovyScriptTest<some long 
> number>.tmp
>  # <some uuid><some long number>.tmp
>  # Three files named with current system milliseconds
>       Directories
>  # InvokeHTTP<some long number>
>  # operationId<some long number>
>  # poifiles
>  # metastore<some long number>
>  # <current milliseconds><some long number> (2 directories)
>        Single instance files
>  # TestPutSQL<some uuid>
>  # zeroByte<some long number>.txt 
>  # PutHDFS_testPutFileFromLocalFile_<long number>



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to