bedrock-kv / bedrock
82%

DEFAULT BRANCH: develop
Repo Added
Token s5ZhiY9p3BKcBOY6Au8fohhCDmrp89s9W regen
Build 582 Last
Files 216
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH develop
branch: develop
CHANGE BRANCH
x
Sync Branches

coverage: 81.661% (+0.06%) from 81.603%
153a2b626a39a3f370c0bdbbefd8db745a41324d

push

github

web-flow 
bedrock-3t9: seed a fresh cluster's sizing from the node config the durability check validates (#323)

Tracks bedrock-3t9.

## Why

Strict durability mode is supposed to refuse to start a cluster that
can't meet the durability profile — three logs, replication factor
three. The guides tell you to satisfy it with node config:

```elixir
config :my_app, MyCluster,
  durability_mode: :strict,
  durability: [desired_logs: 3, desired_replication_factor: 3]
```

`ClusterSupervisor.init/1` checks exactly that node config, and it
passes. But nothing ever *applied* it: a fresh cluster's parameters come
from `Config.new/1` → `Parameters.new/1`, which hardcodes `desired_logs:
1, desired_replication_factor: 1`. In a three-node harness cluster
configured as above, every node started cleanly in strict mode and the
cluster ran with a single log. `Bedrock.Durability.profile(MyCluster)` —
which prefers the live cluster config — reported `:failed`, and nothing
acted on it. The guardrail was checking a number the cluster ignored,
and there was no configuration path to more than one log at all.

## What changed

When a coordinator starts the first recovery of a fresh cluster (no
bootstrap record in object storage),
`DirectorManagement.maybe_put_default_config/1` now seeds `desired_logs`
and `desired_replication_factor` from the same evaluation the startup
check performs — `Profile.evaluate(node_config).checks.*.actual` —
instead of leaving `Config.new/1`'s hardcoded ones. Those parameters are
persisted in the first cluster bootstrap, so later boots and recoveries
keep them.

Existing clusters are untouched: once a bootstrap exists its parameters
win, and editing node config afterwards does not resize the cluster
(that needs an operator write path — bedrock-q67.51).
`guides/durability-profile.md` now says so, and that `durability:` must
be identical across coordinator nodes, since the seed comes from
whichever coordinator leads the first recovery.

## How it works

Readin... (continued)

7 of 7 new or added lines in 1 file covered. (100.0%)

2 existing lines in 2 files now uncovered.

7187 of 8801 relevant lines covered (81.66%)

1138.58 hits per line

Relevant lines Covered
8801 RELEVANT LINES 7187 COVERED LINES
1138.58 HITS PER LINE
Source Files on develop

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
153a2b62... develop bedrock-3t9: seed a fresh cluster's sizing from the node config the durability check validates (#323) Tracks bedrock-3t9. ## Why Strict durability mode is supposed to refuse to start a cluster that can't meet the durability profile — three logs... push web-flow github
81.66
3af051c2... develop Bumped dependencies to clear CVEs push jallum github
81.6
35ae854a... develop bedrock-q67.21.14: Rename components to match their clarified purposes (#304) The q67.21.9 to .13 stack changed what several recovery and distributor components do, and their names kept describing the old behaviour. This is the deferred rename pa... push web-flow github
81.6
ced5317a... develop Route fresh prior core states to InitializationPhase, not LockingPhase (#321) ## Why Recovery keeps two different views of "the previous transaction system": a `CoreState` (durable — just `logs` and `system_materializers`, the minimum needed to ... push web-flow github
81.42
96683d05... develop Start Foreman before Link; route Foreman lookups through the safe call wrapper (#320) ## Summary Fixes the first of two defects in #319: a fresh strict cluster can fail startup with `:noproc`. - `ClusterSupervisor` started `Link` before the capa... push web-flow github
81.25
b0167d2e... develop bedrock-gmf: release 0.7.2 push jallum github
80.76
d49e4834... develop Eliminate strict test-suite warnings (#318) ## Summary - remove unused test bindings and an unused telemetry import - remove an unused private helper and its dead setup - remove an optional default that no call site used This is test-only clean... push web-flow github
80.79
83b2f308... develop Hide LocalFilesystem internal files from object listings (#317) ## Summary - reserve `.bedrock-` basenames for LocalFilesystem backend metadata - filter backend-owned files before sorting and applying listing limits - add a regression proving sn... push web-flow github
80.74
ff70421e... develop bedrock-9v1: ignore local agent skills push jallum github
80.79
15266d0e... develop bedrock-m0v: correct 0.7.1 non-native release notes push jallum github
80.79
See All Builds (582)

Badge your Repo: bedrock

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

Refresh