Skip to content
This repository was archived by the owner on Jul 19, 2020. It is now read-only.
This repository was archived by the owner on Jul 19, 2020. It is now read-only.

check if we need to take measures to check for redis db corruption #33

@GlenDC

Description

@GlenDC

I'm no Redis DB expert, so I'm not aware of what measures it takes already by itself in order to prevent redis DB corruption. That would be a first thing to look at.

But if such measures do not exist, or are not sufficient, it would be great to investigate and implement measures ourself, as to give lose guarantees that our data is not corrupt. Such measures would be checked at startup time, and for long running instances at regular intervals as well.

Most corruption will trigger a panic already:

  • our values are in a specific format, so random corruption will most likely break that format;
  • outputs which would disappear (most likely because an entire wallet suddenly drops because of a data corruption), would trigger a panic in case it is being reverted or spend (if it is an inactive wallet though that might never happen or take a very long time before it does happen);

For now I'm not too worried about this, but ensuring that all the proper measures are in place to immediately detect this, wouldn't be such a bad thing.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions