Server currently uses jRaft 1.3.11, while PD and Store use 1.3.13. PR #2871 preserves those production versions and only aligns Store tests with the version already used by Store. Consolidating version declarations must not silently upgrade Server or alter another component's resolved dependencies.
Track any move to a single jRaft version separately from the apply-error fix. Compatibility has not been established by the PD/Store fault tests. There is already a source-compatibility difference between the old Store test dependency (1.3.9) and 1.3.13: its custom Iterator needs commit() and commitAndSnapshotSync(). This is not evidence of a production regression, but patch-version numbering alone is insufficient assurance.
Before proposing a shared runtime version:
- Compare the affected core APIs and resolved transitive dependencies for Server, PD and Store.
- Validate each component's actual Raft apply, callback and snapshot paths.
- Check existing log/snapshot restart compatibility and supported mixed-version upgrade behavior.
- Document any incompatible behavior and the upgrade/rollback constraints before changing production versions.
No runtime version upgrade is requested as part of #2871.
Server currently uses jRaft 1.3.11, while PD and Store use 1.3.13. PR #2871 preserves those production versions and only aligns Store tests with the version already used by Store. Consolidating version declarations must not silently upgrade Server or alter another component's resolved dependencies.
Track any move to a single jRaft version separately from the apply-error fix. Compatibility has not been established by the PD/Store fault tests. There is already a source-compatibility difference between the old Store test dependency (1.3.9) and 1.3.13: its custom Iterator needs commit() and commitAndSnapshotSync(). This is not evidence of a production regression, but patch-version numbering alone is insufficient assurance.
Before proposing a shared runtime version:
No runtime version upgrade is requested as part of #2871.