chore: documentation for database path configuration

[cody-littley]

Why are these changes needed?

Create more detailed documentation on configuring database paths.

[rootwarp]

As you mentioned I can see directories like below,

${NODE_DB_PATH}
.
├── chunk
└── chunk_v2_litt
    └── chunks
        ├── keymap
        │   └── data
        └── segments

Do you think it would help clarify things if you point out the chunk directory, which appears to be used for V1?

[cody-littley]

This is described in the section above titled ## V1 Protocol.

## V1 Protocol

The V1 protocol's disk footprint looks something like this:

${NODE_DB_PATH}
├── chunk
│   ├── 000001.log
│   ├── CURRENT
│   ├── LOCK
│   ├── LOG
│   └── MANIFEST-000000

The `chunk` directory is created by the V1 software inside the directory specified by `NODE_DB_PATH`. Inside
the `chunk` directory are files maintained by the V1 data storage engine (i.e. `LevelDB`).

[litt3]

This might be useful if you want

[cody-littley]

fixed

[dmanc]

Wouldn't the validator get ejected if this procedure took longer than the SLA for signing (how likely is that)?

[cody-littley]

Yes. I'm not sure how long the window is. Presumably operators will need to restart their nodes every once in a while for maintenance purposes, so we should have a little bit of a grace period baked into ejection.

LittDB doesn't take long to load from disk, so hopefully it's possible to do this sort of restart very rapidly. Although this is something I don't think we've specifically measured yet.