MySQL process stuck in commit state












0















We recently noticed an issue on our MyCluster DB which is comprised of 2 instances hosted on AWS.



Our website grinds to halt in terms of performance and we noticed that there 2 processes that are stuck in commit state as shown below.



Id  User    Host    db  Command Time    State   Info
49 rdsadmin localhost:56378 mysql Sleep 1 n
938 dbadmin 10.0.11.242:57130 REDACTED Query 1 init COMMIT
942 dbadmin 10.0.1.114:49236 REDACTED Query 1 init COMMIT


We are in the process of getting performance_schema enabled. How should we go about find the root cause of the performance bottleneck?










share|improve this question














bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    We recently noticed an issue on our MyCluster DB which is comprised of 2 instances hosted on AWS.



    Our website grinds to halt in terms of performance and we noticed that there 2 processes that are stuck in commit state as shown below.



    Id  User    Host    db  Command Time    State   Info
    49 rdsadmin localhost:56378 mysql Sleep 1 n
    938 dbadmin 10.0.11.242:57130 REDACTED Query 1 init COMMIT
    942 dbadmin 10.0.1.114:49236 REDACTED Query 1 init COMMIT


    We are in the process of getting performance_schema enabled. How should we go about find the root cause of the performance bottleneck?










    share|improve this question














    bumped to the homepage by Community 2 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      We recently noticed an issue on our MyCluster DB which is comprised of 2 instances hosted on AWS.



      Our website grinds to halt in terms of performance and we noticed that there 2 processes that are stuck in commit state as shown below.



      Id  User    Host    db  Command Time    State   Info
      49 rdsadmin localhost:56378 mysql Sleep 1 n
      938 dbadmin 10.0.11.242:57130 REDACTED Query 1 init COMMIT
      942 dbadmin 10.0.1.114:49236 REDACTED Query 1 init COMMIT


      We are in the process of getting performance_schema enabled. How should we go about find the root cause of the performance bottleneck?










      share|improve this question














      We recently noticed an issue on our MyCluster DB which is comprised of 2 instances hosted on AWS.



      Our website grinds to halt in terms of performance and we noticed that there 2 processes that are stuck in commit state as shown below.



      Id  User    Host    db  Command Time    State   Info
      49 rdsadmin localhost:56378 mysql Sleep 1 n
      938 dbadmin 10.0.11.242:57130 REDACTED Query 1 init COMMIT
      942 dbadmin 10.0.1.114:49236 REDACTED Query 1 init COMMIT


      We are in the process of getting performance_schema enabled. How should we go about find the root cause of the performance bottleneck?







      mysql performance






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 18 '18 at 16:56









      HadidAliHadidAli

      1091




      1091





      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          We noticed that there were large number of inserts into the error log table coupled with info logging. This put a lot of stress on the database and resulted in significant performance issues. We disabled info logging at the application level which eliminated the performance bottleneck.






          share|improve this answer























            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f207213%2fmysql-process-stuck-in-commit-state%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            We noticed that there were large number of inserts into the error log table coupled with info logging. This put a lot of stress on the database and resulted in significant performance issues. We disabled info logging at the application level which eliminated the performance bottleneck.






            share|improve this answer




























              0














              We noticed that there were large number of inserts into the error log table coupled with info logging. This put a lot of stress on the database and resulted in significant performance issues. We disabled info logging at the application level which eliminated the performance bottleneck.






              share|improve this answer


























                0












                0








                0







                We noticed that there were large number of inserts into the error log table coupled with info logging. This put a lot of stress on the database and resulted in significant performance issues. We disabled info logging at the application level which eliminated the performance bottleneck.






                share|improve this answer













                We noticed that there were large number of inserts into the error log table coupled with info logging. This put a lot of stress on the database and resulted in significant performance issues. We disabled info logging at the application level which eliminated the performance bottleneck.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 21 '18 at 13:18









                HadidAliHadidAli

                1091




                1091






























                    draft saved

                    draft discarded




















































                    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%2f207213%2fmysql-process-stuck-in-commit-state%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

                    Liste der Baudenkmale in Friedland (Mecklenburg)

                    Single-Malt-Whisky

                    Czorneboh