-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3-output doesn't remove temporary dir. #28
Comments
Hi @mashhurs need some information on this before digging to resolve it.
WDYT? |
The root cause is same. With #34 we introduced retry-like temp folder deletion on LS startup which swipes out empty dirs but those empty dirs are caused by this #28 in a reality.
As I remember, this access fix was also included when I was investigating that traversing |
Thanks a lot for these information, could be useful to try a reproducer. |
Logstash information:
Please include the following information:
bin/logstash --version
): 8.6.2integration-aws-v7.0.1
JVM (e.g.
java -version
):If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
java -version
)JAVA_HOME
environment variable if set.OS version (
uname -a
if on a Unix-like system): any OS butFileUtils.rm_r
error happens on WindowsDescription of the problem including expected versus actual behavior:
FileUtils.rm_r
failsWe introduced
is_deleted?
method for the file factory and it becomes true when file is physically deleted.If any error happens such like
FileUtils.rm_r
, factory lives forever and temporary dirs staySteps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
Opened an issue in fileutils after long investigation: ruby/fileutils#111
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: