Tried vacuum.
| File | Node 1 | Node 1 After | Change |
|---|---|---|---|
| bandwidth.db | 1,912,053,760 | 1,821,536,256 | -4.73% |
| bandwidth.db-shm | 1,245,184 | -100.00% | |
| bandwidth.db-wal | 638,212,752 | -100.00% | |
| heldamount.db | 53,248 | 53,248 | 0.00% |
| info.db | 16,384 | 16,384 | 0.00% |
| notifications.db | 24,576 | 24,576 | 0.00% |
| orders.db | 32,768 | 24,576 | -25.00% |
| orders.db-shm | 32,768 | -100.00% | |
| orders.db-wal | 0 | ||
| piece_expiration.db | 284,540,928 | 264,638,464 | -6.99% |
| piece_expiration.db-shm | 32,768 | -100.00% | |
| piece_expiration.db-wal | 4,120,032 | -100.00% | |
| piece_spaced_used.db | 24,576 | 24,576 | 0.00% |
| piece_spaced_used.db-shm | 32,768 | -100.00% | |
| piece_spaced_used.db-wal | 20,632 | -100.00% | |
| pieceinfo.db | 24,576 | 24,576 | 0.00% |
| pricing.db | 24,576 | 16,384 | -33.33% |
| pricing.db-shm | 32,768 | -100.00% | |
| pricing.db-wal | 0 | ||
| reputation.db | 36,864 | 24,576 | -33.33% |
| reputation.db-shm | 32,768 | -100.00% | |
| reputation.db-wal | 0 | ||
| satellites.db | 32,768 | 20,480 | -37.50% |
| satellites.db-shm | 32,768 | -100.00% | |
| satellites.db-wal | 0 | ||
| secret.db | 24,576 | 24,576 | 0.00% |
| storage_usage.db | 299,008 | 253,952 | -15.07% |
| storage_usage.db-shm | 32,768 | -100.00% | |
| storage_usage.db-wal | 0 | ||
| used_serial.db | 20,480 | 20,480 | 0.00% |
Logs look fine with no errors too.
I’m guessing at this point it’s probably worth just deleting the database and having a new one get re-created. - Followed the instructions here: FATAL Unrecoverable error {"error": "Error during preflight check for storagenode databases "bandwidth" - #3 by BrightSilence
and now the storj node is back online and API is much quicker to resolve. I’m curious to see if this has any impact on node performance (eg. node1 vs node2). I may report back on any differences I see.
Thanks y’all.