You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is a fact that a job can die in a unrecoverable way (server shutdown, database dies, disk full, network down...). In this situations, it may happen that the database has some pending operations, and can't start a new operation. To fix this, we have 2 solutions:
Add a param --resume for continue this operations
A way of detect automatically if the previous operation has died and it needs to be resumed.
The resume parameter exists internally, but not in the CLI. Despite we are working on the second point (where resuming manually is not needed) is interesting to have this param.
It is a fact that a job can die in a unrecoverable way (server shutdown, database dies, disk full, network down...). In this situations, it may happen that the database has some pending operations, and can't start a new operation. To fix this, we have 2 solutions:
The resume parameter exists internally, but not in the CLI. Despite we are working on the second point (where resuming manually is not needed) is interesting to have this param.
The text was updated successfully, but these errors were encountered: