vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/modelarts/umn/modelarts_21_0070.html
Beibei edf86a8ae7
ModelArts GA UMN 06052022 from R&D (#5) 
ModelArts GA UMN 06052022 from R&D

R&D provided a new version of the ModelArts User Manual in May 2022.
Depends-On: #11

Reviewed-by: Artem Goncharov <Artem.goncharov@gmail.com>
2022-05-23 08:19:57 +00:00

3.0 KiB
Raw Permalink Blame History

What Do I Do If a Notebook Instance Fails to Execute Code?

If a notebook instance fails to execute code, you can locate and rectify the fault based on the following scenarios:

  1. If the execution of a cell is suspended or lasts for a long time (for example, the execution of the second and third cells in Figure 1 is suspended or lasts for a long time, causing execution failure of the fourth cell) but the notebook page still responds and other cells can be selected, click interrupt the kernel highlighted in a red box in the following figure to stop the execution of all cells. The notebook instance retains all variable spaces.
    Figure 1 Stopping all cells
  2. If the notebook page does not respond, close the notebook page and the ModelArts management console. Then, open the ModelArts management console and access the notebook instance again. The notebook instance retains all the variable spaces that exist when the notebook instance is unavailable.
    Figure 2 Accessing the notebook instance again
  3. If the notebook instance still cannot be used, access the Notebook page on the ModelArts management console and stop the notebook instance. After the notebook instance is stopped, click Start to restart the notebook instance and open it. In this case, the notebook instance retains all the variable spaces that exist when the notebook instance is unavailable.

Parent topic: Notebook