none
Migrating to a new HPC Cluster but need to keep JobId in sync

    Question

  • Hi,

    We're upgrading our HPC Cluster, including upgrading to new hardware, not just the HPC Pack.

    Various bits of MI we generate rely on the JobId and we'd like to sync up the latest/new JobId on the new system with that on the old system (i.e. If the current cluster's latest JobId on decomissioning is 999, we'd like the new cluster's next JobId to be 1000 or greater). Is this possible?

    A suggested workaround is just to generate (empty) jobs until the new system's next JobId is at the appropriate value - but this seems a bit ungraceful.

    Cheers, Matt

    Thursday, September 06, 2018 10:42 AM

Answers

  • Hi Matt,

      You can do:

    CreateJob to generate a configuring job, then use below API to delete the job:

     public interface ISchedulerStore : IDisposable

        {

            int DeleteJob(int jobId);

     

    which is in Microsoft.Hpc.Scheduler.Store.dll

    You can use below for store connect

    public static Microsoft.Hpc.Scheduler.Store.ISchedulerStore Connect(string server)

        Member of Microsoft.Hpc.Scheduler.Store.SchedulerStore

    This should be very fast.


    Qiufang Shi

    Tuesday, September 11, 2018 9:19 AM

All replies

  • Hi Matt,

      You can do:

    CreateJob to generate a configuring job, then use below API to delete the job:

     public interface ISchedulerStore : IDisposable

        {

            int DeleteJob(int jobId);

     

    which is in Microsoft.Hpc.Scheduler.Store.dll

    You can use below for store connect

    public static Microsoft.Hpc.Scheduler.Store.ISchedulerStore Connect(string server)

        Member of Microsoft.Hpc.Scheduler.Store.SchedulerStore

    This should be very fast.


    Qiufang Shi

    Tuesday, September 11, 2018 9:19 AM
  • Thanks Qiufang, this is basically what I ended up doing.
    Tuesday, September 11, 2018 9:24 AM