Make it Easy to restart a parallel ingest
Bug #1989252 reported by
Jason Stephenson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
New
|
Wishlist
|
Unassigned | ||
Bug Description
The pingest process currently has no option to restart and does not store anyt state as it runs.
Given that bug 1989251 could possibly lead to database crashes or an ingest could cause other perfomance issues on an active Evergreen database, it would be useful if a user could stop or suspend an ingest and restart it later, possibly with different options.
I imagine that pingest would need to store and maintain some kind of runtime state for this to be possible.
It is almost possible to do this now with record ids fed to pingest from files on disk. However, recovering from a stopped ingest is still a bit too clunky with this method.
| tags: | added: cat-importexport |
To post a comment you must log in.
