{
  "id": 286995,
  "title": "[Question to Kaggle Team] GPU Session cap reached, but there no Active Events ",
  "url": "/competitions/sartorius-cell-instance-segmentation/discussion/286995",
  "author_name": "",
  "post_date": "2021-11-11T15:19:59.839319600Z",
  "votes": 2,
  "comment_count": 9,
  "views": 0,
  "content": "<p>Hi Kaggle Team!<br>\nI am trying to <code>Save and Run</code> my notebook in order to make a submission. And I do not have any <code>Active Events</code>. But I get a message </p>\n<pre><code>GPU Session cap reached\nMaximum batch GPU session count of 2 reached. Stop one of your other GPU notebook sessions to continue editing.\n</code></pre>\n<p>The only thing, which helps - Deleting Notebook completely and creating it from scratch. Can you, please, help to resolve an issue </p>",
  "messages": [
    {
      "id": "1579139",
      "postDate": "11/11/2021 15:19:59",
      "content": "<p>Hi Kaggle Team!<br>\nI am trying to <code>Save and Run</code> my notebook in order to make a submission. And I do not have any <code>Active Events</code>. But I get a message </p>\n<pre><code>GPU Session cap reached\nMaximum batch GPU session count of 2 reached. Stop one of your other GPU notebook sessions to continue editing.\n</code></pre>\n<p>The only thing, which helps - Deleting Notebook completely and creating it from scratch. Can you, please, help to resolve an issue </p>",
      "rawMarkdown": "Hi Kaggle Team!\nI am trying to `Save and Run` my notebook in order to make a submission. And I do not have any `Active Events`. But I get a message \n\n```\nGPU Session cap reached\nMaximum batch GPU session count of 2 reached. Stop one of your other GPU notebook sessions to continue editing.\n```\n\nThe only thing, which helps - Deleting Notebook completely and creating it from scratch. Can you, please, help to resolve an issue",
      "votes": null
    },
    {
      "id": "1579220",
      "postDate": "11/11/2021 16:48:00",
      "content": "<p>Thanks for reporting, I'll file a bug with our engineering team.</p>",
      "rawMarkdown": "Thanks for reporting, I'll file a bug with our engineering team.",
      "votes": null
    },
    {
      "id": "1579289",
      "postDate": "11/11/2021 17:44:49",
      "content": "<p><a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> Is this happening on all notebooks for you, or a particular one? You're correct that I don't see any running GPU sessions and I'm unable to reproduce the issue so far.</p>",
      "rawMarkdown": "vladimirsydor Is this happening on all notebooks for you, or a particular one? You're correct that I don't see any running GPU sessions and I'm unable to reproduce the issue so far.",
      "votes": null
    },
    {
      "id": "1584566",
      "postDate": "11/16/2021 15:45:44",
      "content": "<p><a href=\"https://www.kaggle.com/herbison\" target=\"_blank\">@herbison</a>  , <a href=\"https://www.kaggle.com/sohier\" target=\"_blank\">@sohier</a>  here is an <img src=\"https://ibb.co/3vZc4ch\" alt=\"example\"></p>",
      "rawMarkdown": "herbison  , @sohier  here is an ![example](https://ibb.co/3vZc4ch)",
      "votes": null
    },
    {
      "id": "1584582",
      "postDate": "11/16/2021 15:51:33",
      "content": "<p>Thanks <a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> I'll check the data before you delete the problem notebook this time.</p>",
      "rawMarkdown": "Thanks @vladimirsydor I'll check the data before you delete the problem notebook this time.",
      "votes": null
    },
    {
      "id": "1584589",
      "postDate": "11/16/2021 15:54:26",
      "content": "<p><a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> If you refresh the page does it still show  that kernel as canceled? All the backend systems seem to still show it as running.</p>",
      "rawMarkdown": "vladimirsydor If you refresh the page does it still show  that kernel as canceled? All the backend systems seem to still show it as running.",
      "votes": null
    },
    {
      "id": "1584619",
      "postDate": "11/16/2021 16:26:30",
      "content": "<p>It's showing it as canceled now, are you still unable to start a GPU session?</p>",
      "rawMarkdown": "It's showing it as canceled now, are you still unable to start a GPU session?",
      "votes": null
    },
    {
      "id": "1584948",
      "postDate": "11/16/2021 22:36:01",
      "content": "<p>I actually encountered the \"GPU session cap reached\" error few times having only 1 interactive session opened in a different scenario. I noticed that it happened when I quickly execute 2 cells at the start, when no session has created yet. I guess in my case, it was just some front-end concurrency issue. Will take screenshots next time seeing it.</p>",
      "rawMarkdown": "I actually encountered the \"GPU session cap reached\" error few times having only 1 interactive session opened in a different scenario. I noticed that it happened when I quickly execute 2 cells at the start, when no session has created yet. I guess in my case, it was just some front-end concurrency issue. Will take screenshots next time seeing it.",
      "votes": null
    },
    {
      "id": "1585315",
      "postDate": "11/17/2021 08:28:25",
      "content": "<p>Thanks for quick response!<br>\nIt occurs from time to time. I have noticed that when I have active interactive session and push submit button from this session it works fine </p>",
      "rawMarkdown": "Thanks for quick response!\nIt occurs from time to time. I have noticed that when I have active interactive session and push submit button from this session it works fine",
      "votes": null
    },
    {
      "id": "1586192",
      "postDate": "11/17/2021 21:36:36",
      "content": "<p><a href=\"https://www.kaggle.com/chankhavu\" target=\"_blank\">@chankhavu</a> Thanks for this info! I <em>think</em> I fixed it. Your message made me realize I introduced a subtle race during notebook startup last week which could have caused this. Now this has been corrected let me know if you run into it again (requires a page refresh if you're still running old FE code).</p>",
      "rawMarkdown": "chankhavu Thanks for this info! I *think* I fixed it. Your message made me realize I introduced a subtle race during notebook startup last week which could have caused this. Now this has been corrected let me know if you run into it again (requires a page refresh if you're still running old FE code).",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1579220,
      "author_name": "sohier",
      "author_url": "",
      "post_date": "11/11/2021 16:48:00",
      "content": "<p>Thanks for reporting, I'll file a bug with our engineering team.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 1579289,
      "author_name": "herbison",
      "author_url": "",
      "post_date": "11/11/2021 17:44:49",
      "content": "<p><a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> Is this happening on all notebooks for you, or a particular one? You're correct that I don't see any running GPU sessions and I'm unable to reproduce the issue so far.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 1584566,
      "author_name": "vladimirsydor",
      "author_url": "",
      "post_date": "11/16/2021 15:45:44",
      "content": "<p><a href=\"https://www.kaggle.com/herbison\" target=\"_blank\">@herbison</a>  , <a href=\"https://www.kaggle.com/sohier\" target=\"_blank\">@sohier</a>  here is an <img src=\"https://ibb.co/3vZc4ch\" alt=\"example\"></p>",
      "votes": null,
      "replies": [
        {
          "id": 1584582,
          "author_name": "herbison",
          "author_url": "",
          "post_date": "11/16/2021 15:51:33",
          "content": "<p>Thanks <a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> I'll check the data before you delete the problem notebook this time.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1584589,
          "author_name": "herbison",
          "author_url": "",
          "post_date": "11/16/2021 15:54:26",
          "content": "<p><a href=\"https://www.kaggle.com/vladimirsydor\" target=\"_blank\">@vladimirsydor</a> If you refresh the page does it still show  that kernel as canceled? All the backend systems seem to still show it as running.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1584619,
          "author_name": "herbison",
          "author_url": "",
          "post_date": "11/16/2021 16:26:30",
          "content": "<p>It's showing it as canceled now, are you still unable to start a GPU session?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1585315,
          "author_name": "vladimirsydor",
          "author_url": "",
          "post_date": "11/17/2021 08:28:25",
          "content": "<p>Thanks for quick response!<br>\nIt occurs from time to time. I have noticed that when I have active interactive session and push submit button from this session it works fine </p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 1584948,
      "author_name": "chankhavu",
      "author_url": "",
      "post_date": "11/16/2021 22:36:01",
      "content": "<p>I actually encountered the \"GPU session cap reached\" error few times having only 1 interactive session opened in a different scenario. I noticed that it happened when I quickly execute 2 cells at the start, when no session has created yet. I guess in my case, it was just some front-end concurrency issue. Will take screenshots next time seeing it.</p>",
      "votes": null,
      "replies": [
        {
          "id": 1586192,
          "author_name": "herbison",
          "author_url": "",
          "post_date": "11/17/2021 21:36:36",
          "content": "<p><a href=\"https://www.kaggle.com/chankhavu\" target=\"_blank\">@chankhavu</a> Thanks for this info! I <em>think</em> I fixed it. Your message made me realize I introduced a subtle race during notebook startup last week which could have caused this. Now this has been corrected let me know if you run into it again (requires a page refresh if you're still running old FE code).</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "1579139": "Hi Kaggle Team!\nI am trying to `Save and Run` my notebook in order to make a submission. And I do not have any `Active Events`. But I get a message \n\n```\nGPU Session cap reached\nMaximum batch GPU session count of 2 reached. Stop one of your other GPU notebook sessions to continue editing.\n```\n\nThe only thing, which helps - Deleting Notebook completely and creating it from scratch. Can you, please, help to resolve an issue",
    "1579220": "Thanks for reporting, I'll file a bug with our engineering team.",
    "1579289": "vladimirsydor Is this happening on all notebooks for you, or a particular one? You're correct that I don't see any running GPU sessions and I'm unable to reproduce the issue so far.",
    "1584566": "herbison  , @sohier  here is an ![example](https://ibb.co/3vZc4ch)",
    "1584582": "Thanks @vladimirsydor I'll check the data before you delete the problem notebook this time.",
    "1584589": "vladimirsydor If you refresh the page does it still show  that kernel as canceled? All the backend systems seem to still show it as running.",
    "1584619": "It's showing it as canceled now, are you still unable to start a GPU session?",
    "1584948": "I actually encountered the \"GPU session cap reached\" error few times having only 1 interactive session opened in a different scenario. I noticed that it happened when I quickly execute 2 cells at the start, when no session has created yet. I guess in my case, it was just some front-end concurrency issue. Will take screenshots next time seeing it.",
    "1585315": "Thanks for quick response!\nIt occurs from time to time. I have noticed that when I have active interactive session and push submit button from this session it works fine",
    "1586192": "chankhavu Thanks for this info! I *think* I fixed it. Your message made me realize I introduced a subtle race during notebook startup last week which could have caused this. Now this has been corrected let me know if you run into it again (requires a page refresh if you're still running old FE code)."
  },
  "source": "meta"
}