none
Compatibility HPC Pack 2016 update 3 and HPC SDK update 1 RRS feed

  • Question

  • Hi all,

    We are currently hosting an HPC cluster on HPC Pack 2016 update 1 but we want to upgrade to HPC Pack 2016 update 3.

    Our software uses the HPC SDK version 5.1.6124. Since we also support older versions of our software, it is unaccaptable to update all old versions of the software to HPC SDK version 5.3.6437. Only newer versions of the software will be updated to the HPC SDK version 5.3.6437. In addition, hosting two clusters, one on update 1 and one on update 3, is not a preferred solution due to a slow migration to the new cluster and the unavailability of resources.

    To analyze the compatibility between update 1 and update 3 we created an additional HPC cluster on HPC Pack 2016 update 3. Running a calculation on the update 3 cluster with the update 1 SDK seems to work fine but when the result of the calculation comes back to our software we run into an exception:

    'Could not load type 'Microsoft.Hpc.Scheduler.Session.SessionFault' from assembly 'Microsoft.Hpc.Scheduler.Session, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.'

    Apparently some namespaces in the Microsoft.Hpc.Scheduler.Session assembly have changed between update 1 and update 3. After inspecting the assemblies of update 1 and update 3, I noticed the following:
    - HPC SDK 5.1.6124 Microsoft.Hpc.Scheduler.Session contains Microsoft.Hpc.Scheduler.Session.Internal.SessionFault.
    - HPC SDK 5.3.6437 Microsoft.Hpc.Scheduler.Session contains Microsoft.Hpc.Scheduler.Session.SessionFault.
    This explains the exception.

    Blindly changing the Microsoft.Hpc.Scheduler.Session assembly to the update 3 version while keeping all other assemblies on the update 1 version doesn't seem like a preferable solution since this might introduce other unforeseen issues. 

    Are you familiar with this issue and how to solve it or is it not supported to use the update 1 SDK while the cluster is running update 3?

    Please let me know if more information is needed.

    Kind regards,
    Lisette

    Thursday, February 20, 2020 11:55 AM

Answers

  • Hi Lisette,

    Right, we made the namespace changes in Update 2 which breaks the back compatibility for SOA clients. If you are using HPC Pack 2016 Update 3 cluster, please upgrade the SOA client on Update 3 SDK as well. It's not recommended to redirect the session binary for it may not work properly.

    Regards,

    Yutong Sun

    • Marked as answer by LisetteL Friday, February 28, 2020 3:21 PM
    Friday, February 28, 2020 10:10 AM
    Moderator