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

Add heroku scaling commands to publication process #1295

Merged
merged 1 commit into from
Mar 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -365,14 +365,21 @@ Publication Review - Publish)
[DSS repo](https://github.com/MITLibraries/dspace-submission-service#run-stage))
4. ETD processes output queue to update records and send email to stakeholders with summary data and list
of any error records. As of now this is a manual process, but can be triggered via rake task using the following
Heroku run command:
sequence of heroku-cli commands:

```shell
# scale the worker dyno to ensure we have enough memory
heroku ps:scale worker=1:standard-2x --app TARGET-HEROKU-APP

# run the output queue processing job
heroku run -s standard-2x rails dss:process_output_queue --app TARGET-HEROKU-APP

# wait for all ETD emails to be received (the preservation email is the final one to look for)
# scale the worker back down so we do not pay for more CPU/memory than we need
heroku ps:scale worker=1:standard-1x --app TARGET-HEROKU-APP
```

Note the `-s` option, which sets the dyno size for the run command. We are scaling to the larger '2X' dyno because
this job is very memory-intensive.
Note the `-s` option on the second command, which sets the dyno size for the run command. We are scaling to the larger '2X' dyno because this job is very memory-intensive. We also first scale the worker dyno to 2x and then set it back to 1x when we are done for the same reason (preservation takes a lot of memory).

### Publishing a single thesis

Expand Down
Loading