Orchestrations failing due to session being in the kill state.

Legacy Contributor

I am trying to recover some of our non-prod spaces for our CSF 11.0.9.0 model that were inadvertently corrupted by some unknown Actor/Action. Part of that recover included doing a purge of our data lake, and a purge of all processed data in the model so as to fully load our recovered data model. 

However, I continue to have problems getting my orchestration to complete. The logs usually give an Error such as this below. 

2022-08-12 01:03:22,786-0500 ERROR - SQLException during LoadWarehouse load method com.microsoft.sqlserver.jdbc.SQLServerException: Cannot continue the execution because the session is in the kill state.

This was approximately after 20 hours running on this publishing group. The orchestration had been running for approximately 14 hours before it reached this publishing group. We expect long load times when completely purging, but these constant failures are making it almost impossible to recover our spaces. 

Anyone else having Orchestrations going in the Kill State? and any idea on how it reaches that state? 

Thanks,

Harry

Diane McElhiney

The appropriate direction is to create an incident ticket for Support to triage. The full publish log needs to be provided as well as the TOE ID listed under the Publish section for the space under Monitoring. Support has access to more detailed logs to show events occurring around the time the kill reported.

There could be multiple factors to review such as what scripted source and how is it processing, etc.