Improve behavior when killing process abruptly / machine dying #309

New issue

Closed

opened 2019-08-27 19:43:26 +02:00 by tzarebczan · 2 comments

tzarebczan commented

2019-08-27 19:43:26 +02:00

(Migrated from github.com)

Today, if you kill lbrycrd without using the stop command or if the machine crashes, you'll get an error about reindexing and reindexing chainstate. Per @BrannonKing , reindex-chainstate may not work well in all instances and should be avoided.

We should also somehow store the state better so it's able to recover from these types of crashes.

BrannonKing commented

2019-08-27 21:44:56 +02:00

(Migrated from github.com)

Also "kill" is somewhat ambiguous. Ctrl+C will give you a clean shutdown in the current release.

I've already modified the current codebase to sync to disk every block (within the last two-hour time window). That will come out with the next release, ensuring that if you die in between block processing you should be fine. Also "kill" is somewhat ambiguous. Ctrl+C will give you a clean shutdown in the current release.

BrannonKing commented

2019-09-06 22:25:00 +02:00

(Migrated from github.com)

Merged via https://github.com/lbryio/lbrycrd/pull/308

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#309

No description provided.

Rows
Columns