[LU-6349] remove old protocol compatibility Created: 07/Mar/15 Updated: 19/Dec/18 Resolved: 29/May/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.8.0, Lustre 2.11.0, Lustre 2.12.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Dilger | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 17771 | ||||||||
| Description |
|
It seems that there are some old protocol compatibility workarounds that are still present in master that should have been removed when LUSTRE_MSG_MAGIC_V1 was removed. In particular, the process for upgrading LUSTRE_MSG_MAGIC_V1 to LUSTRE_MSG_MAGIC_V2 required the client to connect to the server using the V1 protocol first with the MSG_CONNECT_NEXT_VER op_flag set, and if the server supported the V2 protocol it would reply with LUSTRE_MSG_MAGIC_V2. However, even with V1 protocol support removed, the 2.x clients are still always connecting with NEXT_VER set. In b1_8 this flag was contingent on LUSTRE_MSG_MAGIC_V1 being used. A few other cleanups can be done at the same time:
There are also a lot of places that pretend to allow LUSTRE_MSG_MAGIC_V1 RPCs, but they don't do anything but print an error. They can be cleaned up in a second patch, but i don't want them mixed in with the MSG_CONNECT_NEXT_VER cleanup, since that is important and would prevent us from using this functionality again in the future should we need to upgrade the protocol again. |
| Comments |
| Comment by Gerrit Updater [ 07/Mar/15 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: http://review.whamcloud.com/14006 |
| Comment by Gerrit Updater [ 07/Mar/15 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: http://review.whamcloud.com/14007 |
| Comment by Gerrit Updater [ 28/Apr/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/14006/ |
| Comment by Gerrit Updater [ 28/Apr/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/14007/ |
| Comment by Andreas Dilger [ 29/May/15 ] |
|
Patches landed to master for 2.8.0. |
| Comment by Gerrit Updater [ 06/Jan/16 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: http://review.whamcloud.com/17830 |
| Comment by Gerrit Updater [ 06/Jan/16 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: http://review.whamcloud.com/17831 |
| Comment by Gerrit Updater [ 17/Dec/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/17830/ |
| Comment by Gerrit Updater [ 17/Dec/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/17831/ |
| Comment by Gerrit Updater [ 21/Jan/18 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: https://review.whamcloud.com/30958 |
| Comment by Gerrit Updater [ 06/Feb/18 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30958/ |
| Comment by Gerrit Updater [ 13/Apr/18 ] |
|
Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: https://review.whamcloud.com/31984 |
| Comment by Gerrit Updater [ 06/May/18 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/31984/ |