diff options
author | Amar Tumballi <amarts@redhat.com> | 2019-04-20 11:55:12 +0530 |
---|---|---|
committer | Amar Tumballi <amarts@redhat.com> | 2019-04-29 05:29:44 +0000 |
commit | 48d160756813875cf1889b4ce96493d25f96c726 (patch) | |
tree | 92349106820659f831f295e214335a0297a4ba48 /rpc/xdr/src/.gitignore | |
parent | 88418f400507fba109971f169ce0a2c4243a31c9 (diff) |
protocol: remove compound fop
Compound fops are kept on wire as a backward compatibility with
older AFR modules. The AFR module used beyond 4.x releases are
not using compound fops. Hence removing the compound fop in the
protocol code.
Note that, compound-fops was already an 'option' in AFR, and
completely removed since 4.1.x releases.
So, point to note is, with this change, we have 2 ways to upgrade
when clients of 3.x series are present.
i) set 'use-compound-fops' option to 'false' on any volume which
is of replica type. And then upgrade the servers.
ii) Do a two step upgrade. First from current version (which will
already be EOL if it's using compound) to a 4.1..6.x version,
and then an upgrade to 7.x.
Consider the overall code which we are removing for the option
seems quite high, I believe it is worth it.
updates: bz#1693692
Signed-off-by: Amar Tumballi <amarts@redhat.com>
Change-Id: I0a8876d0367a15e1410ec845f251d5d3097ee593
Diffstat (limited to 'rpc/xdr/src/.gitignore')
0 files changed, 0 insertions, 0 deletions