[LU-6086] verify MDTs are running the same Lustre version Created: 07/Jan/15 Updated: 16/Mar/16 Resolved: 16/Mar/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0, Lustre 2.5.5 |
| Fix Version/s: | Lustre 2.7.0, Lustre 2.5.5 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Andreas Dilger | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Rank (Obsolete): | 16936 | ||||||||
| Description |
|
We require that MDTs and OSTs be running the same version of Lustre (i.e. no interoperability between MDTs) for DNE and LFSCK. While we always test this way and know this requirement ourselves, I know that there will be users who don't know this in the future, and I don't think this is actually checked or enforced anywhere. The MDTs and OSTs should check at connect time via ocd_version that the connecting server is running the same major version of Lustre (e.g. 2.5.x or 2.7.x). Otherwise we may run into interoperability issues if someone is trying to run different versions of Lustre on the MDTs (e.g. DNE1 2.5 - DNE2 2.6 , or DNE2 2.6 - DNE2 2.8 async_commit, or LFSCK changes like http://review.whamcloud.com/13172 or similar). |
| Comments |
| Comment by nasf (Inactive) [ 08/Jan/15 ] |
|
If the OST found that the MDT is running different version, should we forbid the connection? or forbid some LFSCK operations? Or just print some warning message on console? On the other hand, I am not sure whether it is part of the roll upgrade/downgrade among servers. |
| Comment by Gerrit Updater [ 08/Jan/15 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13285 |
| Comment by Gerrit Updater [ 08/Jan/15 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13287 |
| Comment by Oleg Drokin [ 19/Jan/15 ] |
|
I worry about rolling upgrades that could be one mds or one ost at a time |
| Comment by nasf (Inactive) [ 04/Feb/15 ] |
|
I would say that we will only support the rolling upgrade between small versions, such as the patch version difference is within 3. But if rolling upgrade happens between major versions, such as from Lustre-2.6 to Lustre-2.7, it will get failure. Andreas, what's your thought for that? |
| Comment by Gerrit Updater [ 10/Feb/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13285/ |
| Comment by Joseph Gmitter (Inactive) [ 16/Mar/16 ] |
|
Reopening/resolving to be able to adjust the Fix Version. This was entirely landed for 2.7. There is nothing landed here that was addressed in 2.8. |