docs: added info. regarding nvme_core.multipath #514
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added information about nvme_core.multipath as an optional prerequisite in the Replicated PV Mayastor Installation documentation and included it in the High Availability (HA) document.
This update explains the current behavior where, if the application is constrained to nodes with the io-engine label (openebs.io/engine=mayastor), the nexus is preferably placed on the same node as the application. Additionally, it highlights scenarios where the nexus may be placed on a different node if the io-engine pod on the preferred node is in a bad state. The use of nvme_core.multipath is emphasized as essential for enabling HA functionality.