[
https://issues.apache.org/jira/browse/HDDS-17702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-17702:
------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Run optimized snapshot diff in xcompat test
> -------------------------------------------
>
> Key: HDDS-17702
> URL: https://issues.apache.org/jira/browse/HDDS-17702
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Snapshot, test
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> The xcompat test exercises only the legacy snapshot diff path on the current
> cluster, because {{ozone.om.snapshot.diff.optimized.enabled}} defaults to
> false. Old clients never read a report produced by the optimized path,
> including the {{--ordered}} (dependency ordered) report written by 2.3.0
> clients.
> Also, the check in {{compatibility/read.robot}} that legacy clients do not
> see "Report is dependency" cannot fail: clients before 2.3.0 print the reason
> of a snapshot diff response only for FAILED jobs, never for DONE reports.
> Proposed change:
> * Enable the optimized snapshot diff for the current cluster's OM in xcompat
> {{new-cluster.yaml}}, together with
> {{ozone.om.snapshot.force.full.diff=true}}, so OM does not fall back to the
> legacy diff when the {{ozone_rocksdb_tools}} native library is not available.
> Old clusters keep their default diff path.
> * Let legacy clients (before 2.2.0) read the {{--ordered}} diff of
> {{snapshot-1}} to {{snapshot-3}} written by 2.3.0 clients.
> * Check that 2.3.0 clients on a 2.3.0 cluster get "Report is dependency
> ordered." for that diff, so the test fails if xcompat silently falls back to
> the legacy diff.
> * Remove the legacy "Report is dependency" check.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
