[
https://issues.apache.org/jira/browse/HDDS-17531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devesh Kumar Singh updated HDDS-17531:
--------------------------------------
Description:
Audit OMVersionManager.getVersionForClient(), service discovery, and HA client
version refresh against the new feature. Ensure the client sees the apparent
enabled behavior, not merely the new binary.
*Reason:* New external clients may contact old/pre-finalized OM and cannot
assume deployment order.
*Acceptance criteria:* Pre-finalized OM does not advertise enabled policy
semantics; finalized OM does; correct behavior after failover; test clients
against old OM.
was:
Verify OMVersionManager.getVersionForClient(), OzoneManager.getServiceList()
and RPC-client version caching advertise the usable apparent capability, not
merely compiled software support. Handle failover to peers with different
versions and stale service-list information. Reuse upstream ZDU behavior rather
than inventing independent advertisement state.
*Why:* This is the server-to-client capability contract used by all client-side
gates. A client must not be told Storage Policy is usable before OM
finalization.
*Acceptance criteria:* Pre-finalized server advertises a capability below
Storage Policy; finalized server advertises it; failover refresh/recheck is
safe; legacy service discovery is unchanged. Use cases:
Summary: Verify advertised OM Storage Policy capability and failover
semantics (was: Advertise correct OM Storage Policy capability across ZDU and
HA failover)
> Verify advertised OM Storage Policy capability and failover semantics
> ---------------------------------------------------------------------
>
> Key: HDDS-17531
> URL: https://issues.apache.org/jira/browse/HDDS-17531
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> Audit OMVersionManager.getVersionForClient(), service discovery, and HA
> client version refresh against the new feature. Ensure the client sees the
> apparent enabled behavior, not merely the new binary.
> *Reason:* New external clients may contact old/pre-finalized OM and cannot
> assume deployment order.
> *Acceptance criteria:* Pre-finalized OM does not advertise enabled policy
> semantics; finalized OM does; correct behavior after failover; test clients
> against old OM.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
