Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Buildmaster - High CPU database since 6.2.22

    Scheduled Pinned Locked Moved Support
    30 Posts 2 Posters 61 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      philippe.camelio_3885
      last edited by

      Hello @atripp

      I repaired the index, and it seems to help :)
      I let you know what I still have the problem

      Best Regards
      PhilippeC.

      1 Reply Last reply Reply Quote 0
      • P Offline
        philippe.camelio_3885 @atripp
        last edited by

        Hi @atripp
        The problem is stil present.
        Do you have any magic sql scripts to purge my huge tables ?
        Thanks in advance

        1 Reply Last reply Reply Quote 0
        • atrippA Offline
          atripp inedo-engineer
          last edited by

          Typically these are cleaned up via retention policies... but where is the DELETE [Executions] WHERE [Execution_Id] = @Execution_Id being called?

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            philippe.camelio_3885 @atripp
            last edited by philippe.camelio_3885

            Hello @atripp
            This the Manual Execution Cleanup.

            This process is really annoying.

            You have no SQL scripts to cleanup the table ?

            1 Reply Last reply Reply Quote 0
            • atrippA Offline
              atripp inedo-engineer
              last edited by

              We can definitely try to diagnose what's going on. What are the types of Executions in that table? Manual? Build? Etc?

              1 Reply Last reply Reply Quote 0
              • P Offline
                philippe.camelio_3885
                last edited by

                @atripp said in Buildmaster - High CPU database since 6.2.22:

                what are the types of Executions in that table? Manual? Build? Etc?

                Sorry, I am not sure to understand what you expect.
                I guess every log - manual / build / deployement.

                I have setup this in the Administration part:

                • Diagnostics.MinimumLogLevel : 20
                • Retention.KeepLastManualExecutionCount: 1000

                I have 3 Retention policies:

                • Delete deployed release Retain 180 days
                • Delete artifacts for rejected build : Retain 30 days
                • Delete execution logs : retain 30 days

                Therefore, logs haven't been removed for more than 36 month !!!
                I have the same in ScopedExecutionsLogEntries

                SELECT TOP (10) [Execution_Id]
                      ,[LogEntry_Sequence]
                      ,[Scope_Sequence]
                      ,[LogEntry_Level]
                      ,[LogEntry_Date]
                  FROM [Otter].[dbo].[ScopedExecutionLogEntries]
                
                Execution_Id	LogEntry_Sequence	Scope_Sequence	LogEntry_Level	LogEntry_Date
                14	1	1	0	2019-04-02 09:09:23.500
                14	2	1	0	2019-04-02 09:09:23.500
                14	3	1	10	2019-04-02 09:09:23.500
                
                1 Reply Last reply Reply Quote 0
                • atrippA Offline
                  atripp inedo-engineer
                  last edited by

                  Hey @philippe-camelio_3885

                  You may be looking at the wrong database... based on Otter in your query.

                  Here's a way to see executions by execution type: SELECT [ExecutionMode_Code], COUNT(*) FROM [BuildMaster]..[Executions] GROUP BY [ExecutionMode_Code]

                  As for retention policies, you should be able to see the logs of those., and see what's being purged.

                  Anwyays, w'ell figure it out... hang tight!

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    philippe.camelio_3885 @atripp
                    last edited by

                    @atripp
                    Houps ! 😲

                    About the retention policies, when I start them manually, they remove few lines.

                    Here is the result of the SQL:

                    R 91369
                    M 164051
                    S 1560
                    T 377
                    B 999

                    Thanks
                    Philippe

                    1 Reply Last reply Reply Quote 0
                    • atrippA Offline
                      atripp inedo-engineer
                      last edited by

                      Thanks Philippe!! That's helpful.

                      Can you try this sql?

                      USE [BuildMaster]
                      
                      BEGIN TRANSACTION
                      
                      DELETE [Executions]
                       WHERE [ExecutionMode_Code] IN ('R', 'M', 'T')
                         AND ROW_NUMBER() OVER(PARTITION BY [ExecutionMode_Code] ORDER BY [Execution_Id] DESC) > 1000
                      
                      SELECT [ExecutionMode_Code], COUNT(*) FROM [Executions] GROUP BY [ExecutionMode_Code]
                      
                      ROLLBACK
                      

                      You should then see results like this:

                      R 1000
                      M 1000
                      S 1560
                      T 377
                      B 999
                      

                      You can further inspect the tables, but this should do the trick. If the results look okay, then please run only the DELETE statement and then it will be fine.

                      Can you let me know if it works? we will incorporate this logic in BM-3659

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        philippe.camelio_3885
                        last edited by

                        I have this error msg from SQL Management Studio or from osql

                        Msg 4108, Level 15, State 1, Line 7
                        Les fonctions fenêtrées peuvent uniquement apparaître dans les clauses SELECT ou ORDER BY
                        

                        I am not good enough in SQL to overcome this. Any tricks ?

                        1 Reply Last reply Reply Quote 0
                        • atrippA Offline
                          atripp inedo-engineer
                          last edited by

                          My bad, can you try this instead? Basically we are trying to delete all "R, M, T" executions except the most recent 1000 of each type.

                          This is what the code is doing now, just really inefficiently for some reason -- and the inefficiency seems to have caused a "backlog" of sorts.

                          USE [BuildMaster]
                          
                          BEGIN TRANSACTION
                          
                          DELETE [Executions]
                            FROM [Executions] E,
                               (SELECT [Execution_Id], 
                                       ROW_NUMBER() OVER(PARTITION BY [ExecutionMode_Code] ORDER BY [Execution_Id] DESC) [Row]
                                 FROM [Executions]
                                WHERE [ExecutionMode_Code] IN ('R', 'M', 'T')) EE
                          WHERE E.[Execution_Id] = EE.[Execution_Id]
                            AND EE.[Row] > 1000
                          
                          SELECT [ExecutionMode_Code], COUNT(*) FROM [Executions] GROUP BY [ExecutionMode_Code]
                          
                          ROLLBACK
                          
                          1 Reply Last reply Reply Quote 0
                          • P Offline
                            philippe.camelio_3885
                            last edited by philippe.camelio_3885

                            Buildmaster is broken 😥
                            Time out when I try to get an access to BM.

                            I reboot unsuccessfully

                            but the Database is clean

                            R	1000
                            M	1000
                            S	1586
                            T	380
                            B	1025
                            1 Reply Last reply Reply Quote 0
                            • P Offline
                              philippe.camelio_3885
                              last edited by

                              I had to stop SQL Instance, Restart BM Service
                              Everything looks fine

                              1 Reply Last reply Reply Quote 0
                              • P Offline
                                philippe.camelio_3885
                                last edited by

                                The request still eating all my CPU :(

                                5a911e99-e65c-4b19-bbd8-272be81ded0b-image.png

                                1 Reply Last reply Reply Quote 0
                                • atrippA Offline
                                  atripp inedo-engineer
                                  last edited by

                                  How often is this happening? It shows 102 executions were purged, and based on the I/O there was a lot of logs deleted... this can be actually quite resource-intensive, as there are a lot of log data.

                                  But this usually happen during off-hours, etc., so it shouldn't be disturbing.

                                  P 1 Reply Last reply Reply Quote 0
                                  • P Offline
                                    philippe.camelio_3885 @atripp
                                    last edited by philippe.camelio_3885

                                    @atripp
                                    Unfortunately, it is disturbing.

                                    I join 2 screenshoot about the impact of the delete sql and it is happening during working hours.

                                    I find that deleting several hours of CPU and IO for only 102 purged executions take too long

                                    As I said, the problem exists since release 6.2.22.

                                    I stopped all retention policies,

                                    The problem occurs when the Manual Execution Cleanup is running

                                    ae5596e6-3bd1-446f-ad18-819b1b59a11f-image.png

                                    ==============

                                    40cb28d8-4c5b-43f5-9e00-19f262b07049-image.png

                                    f5e93e31-d3df-449a-a846-8a931122ac1a-image.png

                                    I ran again your code:
                                    Before the execution:

                                    b536a5c6-f9f9-4e3a-917e-4888440fd129-image.png

                                    After

                                    (255268 rows affected)
                                    
                                    Completion time: 2021-01-30T22:06:02.9603752+01:00
                                    

                                    21f5c092-4ba4-4616-bdf7-f5254701b24c-image.png

                                    SELECT [ExecutionMode_Code], COUNT(*) FROM [Executions] GROUP BY [ExecutionMode_Code]
                                    

                                    29644d1e-092e-444a-b1d8-40921129c6a6-image.png

                                    I set Retention.KeepLastManualExecutionCount to 50.

                                    I will see what is going on

                                    Best Regards
                                    Philippe

                                    PS - Thanks for the help

                                    P 1 Reply Last reply Reply Quote 0
                                    • P Offline
                                      philippe.camelio_3885 @philippe.camelio_3885
                                      last edited by philippe.camelio_3885

                                      This is what is happening if I force Manual Execution Cleanup to run.
                                      The stop of the BuildMaster Service solved the problem, but BM is down :(

                                      d53e43a7-39f9-46a0-a71e-8233c85c8dd0-image.png

                                      To be more complete, here is the steps I followed

                                      1 Execution of the delete script
                                      2 Restart buildmaster
                                      4 Start Manual Execution Cleanup ==> Problem occurs
                                      4 Start Manual Execution Cleanup ==> Problem occurs

                                      1 Reply Last reply Reply Quote 0
                                      • atrippA Offline
                                        atripp inedo-engineer
                                        last edited by

                                        If I'm understanding correctly, did your the Manual Execution records go from 1000 to 164,000 in just a few days? If so, that would explain a lot....

                                        These are the types of so-called Manual Executions:

                                        • Importing or Exporting Applications
                                        • Cloning and Applying Template to Applications
                                        • Sync of Issue Sources
                                        • Deploying Configuration file
                                        • Upgrading Inedo Agents
                                        • Sync infrastructure

                                        They are supposed to only occur on a manual basis, like when you trigger something from the UI so you can get logs. Or, in the case of sync infrastructure, whenever infrastructure changes.

                                        Any idea what all the manual executions could be?

                                        P 1 Reply Last reply Reply Quote 0
                                        • P Offline
                                          philippe.camelio_3885 @atripp
                                          last edited by

                                          @atripp said in Buildmaster - High CPU database since 6.2.22:

                                          Importing or Exporting Applications **==> ** never done this **
                                          Cloning and Applying Template to Applications **==> ** one time a month maximum ****
                                          Sync of Issue Sources ==> Not sure what this is about ???
                                          Deploying Configuration file **==> ** No ****
                                          Upgrading Inedo Agents ==> done by Otter in my case
                                          Sync infrastructure ==> Used to sync every 2 hours from Otter. I increased since the last post to one day

                                          I have about 100-110 servers (Linux / windows) sync from Otter, whereas I am using a just a few for deploying application (about 25 actually).
                                          I have plenty of Role

                                          It could be Sync infrastructure, any way to check ?

                                          1 Reply Last reply Reply Quote 0
                                          • atrippA Offline
                                            atripp inedo-engineer
                                            last edited by

                                            The Execution_Configuration column of the ManualExecutions table will give a clue; it's XML but if you expand the coluumn, you'll see the name of the manual execution.

                                            It's only supposed to log if something changed, however...

                                            If there's a bug, one way to check would be to disable infrastructure sync, for the time being.

                                            P 1 Reply Last reply Reply Quote 0

                                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                            With your input, this post could be even better 💗

                                            Register Login
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post
                                            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation