Jiva Overview

Jiva Sparse File Layout

The following content is modified with some architectural change as compared to Rancher’s LongHorn .

Replica Operations of Jiva

Longhorn read index

The read index table is kept in memory and consumes two bytes for each 4K block. A maximum of 512 auto-generated snapshots can be created for each volume. The read index table consumes a certain amount of in-memory space for each replica. A 1TB volume, for example, consumes 512MB of in-memory space.

Replica Rebuild

When the controller detects failures in one of its replicas, it marks the replica as being in an error state and the rebuilding process is triggered.

Note: If REPLICATION_FACTOR is still met even after a replica is marked faulty, the controller will continue to serve R/W IOs. Else, it will wait for satisfying REPLICATION_FACTOR((n/2)+1; where n is the number of replicas).

Feedback

Was this page helpful?

Thanks for the feedback. Open an issue in the if you want to report a problem or suggest an improvement. Engage and get additional help on https://kubernetes.slack.com/messages/openebs/.