Setting connection retry property in HPC RRS feed

  • Question

  • Dear all,

    In our production environment, there is network connectivity issues time to time. Network goes out for few seconds and comes back. So we would like to enable HPC to retry the SQL commands if they fail the first time.

    Is there any way I can configure my SQL connection settings so that the SQL command can be retried. For an example, we have below exception while updating the job properties, and we believe this is due to the network issue. can we provide some retry option here?

    Server stack trace: 
       at Microsoft.Hpc.Scheduler.Store.TransactionProcessor.RunTransaction(Boolean shouldRetry)
       at Microsoft.Hpc.Scheduler.Store.SchedulerStoreInternal.Object_SetProps(ConnectionToken& token, ObjectType obType, Int32 obId, StoreProperty[] props)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Hpc.Scheduler.Store.ISchedulerStoreInternal.Object_SetProps(ConnectionToken& token, ObjectType obType, Int32 obId, StoreProperty[] props)
       at Microsoft.Hpc.Scheduler.Store.StoreServer.Object_SetProps(ObjectType obType, Int32 obId, StoreProperty[] props)
       at Microsoft.Hpc.Scheduler.Store.SchedulerStoreSvc.SetPropsOnServer(ObjectType obType, Int32 itemId, StoreProperty[] props)
       at Microsoft.Hpc.Scheduler.SchedulerJob.Commit()
       at HPC.JobManager.JobManager.UpdateJobProperties(String jobId, Dictionary`2 changedProperties) in C:\RST_Deploy\TempDeployPkg\SourceCode\RstSvn\src\BatchExecution\WindowsHPC\HPC.JobManager\JobManager.cs:line 382 

    Puneet Sharma

    Monday, August 28, 2017 9:19 PM

All replies

  • Hi Puneet,

      Most of the cases, transaction timeout at our scheduler service side to the SQL will be automatically retried. If in your situation it is not retried, we need take an investigation while it is not retried. We might reach you to collect more information.


    Qiufang Shi

    Tuesday, August 29, 2017 1:33 AM