Arne Redlich

The scenario was slightly different: * volume V has MDS master table on node1, slave on node2 * node1 is down: *node3* takes ownership of V (at this point the...

@kvanhijf it's something I was wondering as well. Voldrv / edge don't use the MDS config at the moment for the HA preferences (this might be worth an FR). @saelbrec...

The relevant changes are already present in the ee-6.17.0 release packages (volumedriver-ee-release-ubuntu-16.04 on jenkins). These were not published to the EE apt repos yet due to a fwd compat issue...

Configuring the max tlogs a slave may be behind to make it still eligible for failover was backported to ee-6.16.21, but only the per-volumedriver configurable and *not* the per-volume configuration....

Protobuf descriptions of the events: * https://github.com/openvstorage/volumedriver/blob/dev/src/volumedriver/Events.proto * https://github.com/openvstorage/volumedriver/blob/dev/src/volumedriver/VolumeDriverEvents.proto * https://github.com/openvstorage/volumedriver/blob/dev/src/filesystem/FileSystemEvents.proto The former provides a base message type that is extended by the latter two. The generated code is part...

Some more info on the `VolumeDriverErrorCode`s * `Unknown`: (unused) placeholder * `ReadFromDisposableSCO`: error reading data from a disposable SCO in the SCO cache (I/O error on device?) Will trigger SCO...

Relevant volumedriver configuration (cf. `volumedriver_fs --config-help-markdown`): * `volume_manager` section * `number_of_scos_in_tlog`: A SCO is non-disposable (dirty) while it's not marked as safely stored on the backend. Marking it as disposable...

@khenderick: when preparing maintenance mode, the `volume_router/vrouter_*_threshold`s should be set to 0 to prevent automigration back to that node.

MDS / DTL (unless `DTLConfigMode.Automatic` is configured globally) configuration is completely up to the framework.