[
https://issues.apache.org/jira/browse/HDDS-17530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devesh Kumar Singh updated HDDS-17530:
--------------------------------------
Description:
Ensure mixed OM binaries share apparent version and no incompatible policy
metadata enters replicated state before finalization. Test leadership changes,
retry, replay, checkpoint and snapshot installation.
*Reason:* OM state-machine correctness cannot rely solely on client checks.
*Acceptance criteria:* Supported mixed-OM upgrade has deterministic state; no
pre-finalization policy persistence; finalization ordering and restart pass.
was:
Audit preprocessing, validation, Ratis submission, request serialization,
state-machine apply, double buffer, DB codecs, replay and checkpoint/snapshot
install. Prove a new OM leader cannot write storage-policy state that an older
peer cannot safely process while pre-finalized. Ensure policy decisions do not
depend on unsynchronized local defaults during replicated apply. Test leader
changes, retries and snapshot finalization state.
*Why:* This is the OM cluster-state server gate. Unknown Protobuf fields or
nondeterministic interpretation can cause divergent OM state even when an RPC
succeeds.
*Acceptance criteria:* No incompatible state before finalization; consistent
replay and snapshots; leader/follower mixed-version test; predictable retry
behavior; no regression for old bucket metadata.
Summary: Validate Storage Policy consistency across OM HA, Ratis
replay, and snapshots (was: Guarantee OM Ratis replay, snapshot and HA
compatibility for Storage Policy)
> Validate Storage Policy consistency across OM HA, Ratis replay, and snapshots
> -----------------------------------------------------------------------------
>
> Key: HDDS-17530
> URL: https://issues.apache.org/jira/browse/HDDS-17530
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> Ensure mixed OM binaries share apparent version and no incompatible policy
> metadata enters replicated state before finalization. Test leadership
> changes, retry, replay, checkpoint and snapshot installation.
> *Reason:* OM state-machine correctness cannot rely solely on client checks.
> *Acceptance criteria:* Supported mixed-OM upgrade has deterministic state; no
> pre-finalization policy persistence; finalization ordering and restart pass.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
