|
|
Reporter | KnightMB | Assigned To | KnightMB | |
---|
Priority | high | Severity | major | Reproducibility | random |
---|
Status | resolved | Resolution | fixed | |
---|
Product Version | 2.41 | |
---|
Target Version | 2.42 | Fixed in Version | 2.42 | |
---|
|
|
Summary | 0000068: Transaction Foundation Manager can get stuck in a repair loop |
---|
Description | The Transaction Foundation Manager can get stuck in a loop that tries to repair past foundations that are not damaged. |
---|
Steps To Reproduce | It is very hard to replicate, but the circumstances requires that a peer is doing a routine transaction foundation compare with peers and mistakes a certain foundation block as "bad" and wipes/repairs it afterwards. |
---|
Additional Information | This can happen with a database error, but once it happens, it starts kind of a never ending cycle of repair that keeps the peer from being in sync with all other peers until all the server software is stopped and then restarted. |
---|
Tags | No tags attached. |
---|
|
|