MySQL RDS - Unable to Kill Hung Queries












0















I have a MySQL RDS instance that's got 100+ queries all stuck waiting for a table metadata lock.



The good news



I have permission to kill all of the sessions, and have 0 concern for data loss as this database is completely reloaded as needed.



The bad news



It's a MySQL instance running as a hosted RDS instance in AWS AND while I have access to the "root" MySQL account, I don't have access to the AWS console that this RDS instance is hosted in.



What I've tried



When this has happened previously, I look through the connections and run CALL mysql.rds_kill(_each_and_every_process_id_one_at_a_time). However, this time, when I try run one of these kill statements, it simply hangs. (I'm doing this through MySQL workbench)



What options do I have? Is there someway to "escalate" my mysql.rds_kill call so that it's handled right away? Do I try executing this outside of workbench somehow?









share







New contributor




Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I have a MySQL RDS instance that's got 100+ queries all stuck waiting for a table metadata lock.



    The good news



    I have permission to kill all of the sessions, and have 0 concern for data loss as this database is completely reloaded as needed.



    The bad news



    It's a MySQL instance running as a hosted RDS instance in AWS AND while I have access to the "root" MySQL account, I don't have access to the AWS console that this RDS instance is hosted in.



    What I've tried



    When this has happened previously, I look through the connections and run CALL mysql.rds_kill(_each_and_every_process_id_one_at_a_time). However, this time, when I try run one of these kill statements, it simply hangs. (I'm doing this through MySQL workbench)



    What options do I have? Is there someway to "escalate" my mysql.rds_kill call so that it's handled right away? Do I try executing this outside of workbench somehow?









    share







    New contributor




    Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I have a MySQL RDS instance that's got 100+ queries all stuck waiting for a table metadata lock.



      The good news



      I have permission to kill all of the sessions, and have 0 concern for data loss as this database is completely reloaded as needed.



      The bad news



      It's a MySQL instance running as a hosted RDS instance in AWS AND while I have access to the "root" MySQL account, I don't have access to the AWS console that this RDS instance is hosted in.



      What I've tried



      When this has happened previously, I look through the connections and run CALL mysql.rds_kill(_each_and_every_process_id_one_at_a_time). However, this time, when I try run one of these kill statements, it simply hangs. (I'm doing this through MySQL workbench)



      What options do I have? Is there someway to "escalate" my mysql.rds_kill call so that it's handled right away? Do I try executing this outside of workbench somehow?









      share







      New contributor




      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I have a MySQL RDS instance that's got 100+ queries all stuck waiting for a table metadata lock.



      The good news



      I have permission to kill all of the sessions, and have 0 concern for data loss as this database is completely reloaded as needed.



      The bad news



      It's a MySQL instance running as a hosted RDS instance in AWS AND while I have access to the "root" MySQL account, I don't have access to the AWS console that this RDS instance is hosted in.



      What I've tried



      When this has happened previously, I look through the connections and run CALL mysql.rds_kill(_each_and_every_process_id_one_at_a_time). However, this time, when I try run one of these kill statements, it simply hangs. (I'm doing this through MySQL workbench)



      What options do I have? Is there someway to "escalate" my mysql.rds_kill call so that it's handled right away? Do I try executing this outside of workbench somehow?







      mysql amazon-rds





      share







      New contributor




      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 mins ago









      Nick HeidkeNick Heidke

      1012




      1012




      New contributor




      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Nick Heidke is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Nick Heidke is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232309%2fmysql-rds-unable-to-kill-hung-queries%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Nick Heidke is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Nick Heidke is a new contributor. Be nice, and check out our Code of Conduct.













          Nick Heidke is a new contributor. Be nice, and check out our Code of Conduct.












          Nick Heidke is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232309%2fmysql-rds-unable-to-kill-hung-queries%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          SQL Server 17 - Attemping to backup to remote NAS but Access is denied

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          Restoring from pg_dump with foreign key constraints