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.

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

Session expired on file inventory jobs #1268

Open
hectorcorrea opened this issue Jan 30, 2025 · 1 comment
Open

Session expired on file inventory jobs #1268

hectorcorrea opened this issue Jan 30, 2025 · 1 comment

Comments

@hectorcorrea
Copy link
Member

We got a Mediaflux::SessionExpired exception as part of the FileInventoryJob#perform

[PROJECT_ROOT]/app/models/mediaflux/request.rb:77 :in `response_xml`
[PROJECT_ROOT]/app/models/mediaflux/iterator_request.rb:23 :in `result`
[PROJECT_ROOT]/app/models/project.rb:284 :in `block (2 levels) in file_list_to_file`
[PROJECT_ROOT]/app/models/project.rb:282 :in `block in file_list_to_file`
[PROJECT_ROOT]/app/models/project.rb:279 :in `open`
[PROJECT_ROOT]/app/models/project.rb:279 :in `file_list_to_file`
[PROJECT_ROOT]/app/jobs/file_inventory_job.rb:34 :in `perform` 

More details in HoneyBadger https://app.honeybadger.io/projects/113559/faults/115552704

In this case, this was a job that Sidekiq kept retrying because of a SQL connection issue (see details here #1263) and we have a fix for it.

Matt started the original job about 10 AM and eventually at 4 PM his session expired and this exception was raised. Not a big deal.

However, it does raise the question of what will happen if a legitimate job does take 6 hrs (or whatever time frame our sessions are valid)?

@hectorcorrea
Copy link
Member Author

This might become a problem in the future and from our MediaFlux trainings we think when we hit that wall we might need to switch to use MF background jobs (whatever they are called)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant