Corrupted badger databases

Node Operators FAQ
1

Corrupted badger databases prevent node from starting after a file check.

There is still non way to repair those, correct? Only solution is to delete and re-create?

2

Yep. They didn’t work on badger anymore when hashstore launched. The only work I see is done for the hashstore in the recent versions. Stop the node and delete the badger db. And activate startup piece scan, of course.

4 Likes
3

That’s what I have thought… :unamused_face:

4

Can someone explain to me why badger is now no longer in production?
is hashstore the new?
what should be done in regards to that?

5

But why did it get corrupted? Unsafe shutdown? Don’t you use UPS?

6

Yes. Server stopped functioning properly.

7

Badger is still there and works and supported, but no extra development effort is being spent on it.

You can optionally migrate a node to new setups like the hashtable and memtable, which is where all the effort is going:
[Tech Preview] Hashstore backend for storage nodes - Product Discussions / STORJLINGS - Storj Community Forum (official)

Still considered preview mode. Personally I’ve stuck with the old setup since it’s been fine under relatively low loads of traffic. (+I use badger on three nodes that have really slow storage and it helps on them).

2 Likes
8

Thanks. I got badger on all my nodes, been running just fine. On many many 10’s for nodes on each machines :slight_smile: so won’t do hashstore right now.