Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-15843

Misconfigured SQL Server causes severe problems in Bamboo

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      USE [master]
GO
ALTER DATABASE [bambooM1] SET SINGLE_USER WITH ROLLBACK IMMEDIATE 
ALTER DATABASE [bambooM1] SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT
ALTER DATABASE [bambooM1] COLLATE Latin1_General_CS_AS
ALTER DATABASE [bambooM1] SET MULTI_USER
GO

      The lack of those settings can cause EXPIRY to cause the Bamboo service to hang, for example.

      Please, check if the collation/isolation in the upgrade task and refuse to start if they are incorrect.

            [BAM-15843] Misconfigured SQL Server causes severe problems in Bamboo

            Sten Pittet (Inactive) added a comment -

            Hi Brian,

            I'm sorry that you ran into this issue. Your feedback is really useful and I'll forward it to our Tech-writing team to improve our documentation.

            I've opened this issue and added it to our backlog.

            Thanks,

            Sten Pittet
            Bamboo Product Manager

            Sten Pittet (Inactive) added a comment - Hi Brian, I'm sorry that you ran into this issue. Your feedback is really useful and I'll forward it to our Tech-writing team to improve our documentation. I've opened this issue and added it to our backlog. Thanks, Sten Pittet Bamboo Product Manager

            Brian Carr added a comment -

            To duplicate the problem, EXPIRY needs to be scheduled to run at the same time as a complex project / job. In our case we had a project with over a dozen stages which ran on the hour and running EXPIRY at midnight (the default) caused the service hang while running it at 8:35PM prevented the hang (as long as no repo scheduled jobs happened to be started at 8:35PM).

            Brian Carr added a comment - To duplicate the problem, EXPIRY needs to be scheduled to run at the same time as a complex project / job. In our case we had a project with over a dozen stages which ran on the hour and running EXPIRY at midnight (the default) caused the service hang while running it at 8:35PM prevented the hang (as long as no repo scheduled jobs happened to be started at 8:35PM).

            Brian Carr added a comment -

            Also, those steps were included in the Bamboo 4.4 documentation for MS SQL Server, but not listed in 5.7. They should either be completed by the DB creation / upgrade process or documented as required steps for this environment (some DBA commands can not be executed via JDBC). We started at 5.0 and so never had those steps suggested or completed.

            Also, all background processes should default to logging their start and stop times. EXPIRY should log its start and stop time unless the user has explicitly turned off all logging. Similarly indexing, backups, exports,... should all be logged to aid in identification of what is causing problems.

            Brian Carr added a comment - Also, those steps were included in the Bamboo 4.4 documentation for MS SQL Server, but not listed in 5.7. They should either be completed by the DB creation / upgrade process or documented as required steps for this environment (some DBA commands can not be executed via JDBC). We started at 5.0 and so never had those steps suggested or completed. Also, all background processes should default to logging their start and stop times. EXPIRY should log its start and stop time unless the user has explicitly turned off all logging. Similarly indexing, backups, exports,... should all be logged to aid in identification of what is causing problems.

              Unassigned Unassigned
              rsperafico Rafael Sperafico (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: