Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JournalStorage with JournalFileSymlinkLock may fail to resume #5921

Open
not522 opened this issue Jan 9, 2025 · 0 comments
Open

JournalStorage with JournalFileSymlinkLock may fail to resume #5921

not522 opened this issue Jan 9, 2025 · 0 comments
Labels
bug Issue/PR about behavior that is broken. Not for typos/examples/CI/test but for Optuna itself.

Comments

@not522
Copy link
Member

not522 commented Jan 9, 2025

Expected behavior

JournalStorage should be able to resume even if the process terminates unexpectedly. However, if the process terminates suddenly, a lock file may remain and it may not be able to resume.

Environment

  • Optuna version:4.2.0.dev
  • Python version:3.11.0
  • OS:macOS-15.1-x86_64-i386-64bit
  • (Optional) Other libraries and their versions:

Error messages, stack traces, or logs

If we encounter the above bug, the resumed process will sleep forever.

Steps to reproduce

  1. Terminate the process suddenly (not Ctrl-C; it deletes the lock file correctly.)
  2. Resume the optimization process

Additional context (optional)

No response
@not522 not522 added the bug Issue/PR about behavior that is broken. Not for typos/examples/CI/test but for Optuna itself. label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue/PR about behavior that is broken. Not for typos/examples/CI/test but for Optuna itself.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@not522