-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
engine: Do not ignore+detach shards with failed Open/Init ops
Previously, storage engine ignored configured shards if they failed to open/init (with at least one successful). This behavior is unclear: if engine is configured to work with N shards, then all N shards must work, otherwise, the whole engine is broken and needs to be reconfigured. Immediately fail engine's `Open`/`Init` methods on any shard failure. With this, it's redundant to open/init shard concurrently, so they are processed one-by-one now. In the future, possibly, optional config flag will be added to ignore problem shards, but default behavior will be kept strict. Signed-off-by: Leonard Lyubich <[email protected]>
- Loading branch information
1 parent
cd628f7
commit 896f36f
Showing
4 changed files
with
8 additions
and
96 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters