Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-23

Defining the DC node disk size during the CloudFormation template phase

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • None
    • AWS Quick Start
    • None
    • 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.

      Issue Summary

      The Cloudformation currently default to set the node disk size to 8GB. The log directory Bitbucket_Home/log is stored in the node. The logs size increases drastically causing performance issue with the nodes. Log rotation which able to compress and archive log files is a temporary fix.

      It would be great to see the option is given to increase the node disk size during the CloudFormation template phase.

      Suggestion

      Suggestion from the customer, similar to the additional storage for your repository data feature, having an option to add a secondary ELB to store the log, cache and temp files.

            [SCALE-23] Defining the DC node disk size during the CloudFormation template phase

            Rogier.Timmermans added a comment - - edited

            Thanks for the quick pick-up!

             

            Edit: Fix confirmed! Below a quick lsblk/df against a newly deployed 7.6.0 stack's emerged webnode. Many thanks!

             

            [root@ip-192-168-106-32 log]# lsblk
            NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
            nvme0n1 259:0 0 50G 0 disk
            ├─nvme0n1p1 259:1 0 50G 0 part /
            └─nvme0n1p128 259:2 0 1M 0 part
            [root@ip-192-168-106-32 log]# df -h
            Filesystem Size Used Avail Use% Mounted on
            devtmpfs 3.8G 0 3.8G 0% /dev
            tmpfs 3.8G 0 3.8G 0% /dev/shm
            tmpfs 3.8G 396K 3.8G 1% /run
            tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
            /dev/nvme0n1p1 50G 2.7G 48G 6% /
            192.168.106.23:/media/atl/bitbucket/shared 100G 135M 100G 1% /media/atl/bitbucket/shared
            tmpfs 763M 0 763M 0% /run/user/1000

            Rogier.Timmermans added a comment - - edited Thanks for the quick pick-up!   Edit: Fix confirmed! Below a quick lsblk/df against a newly deployed 7.6.0 stack's emerged webnode. Many thanks!   [root@ip-192-168-106-32 log] # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 50G 0 disk ├─nvme0n1p1 259:1 0 50G 0 part / └─nvme0n1p128 259:2 0 1M 0 part [root@ip-192-168-106-32 log] # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.8G 0 3.8G 0% /dev tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs 3.8G 396K 3.8G 1% /run tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup /dev/nvme0n1p1 50G 2.7G 48G 6% / 192.168.106.23:/media/atl/bitbucket/shared 100G 135M 100G 1% /media/atl/bitbucket/shared tmpfs 763M 0 763M 0% /run/user/1000
            Ben P (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Reviewing [ 11773 ] New: Closed [ 6 ]

            Hi d8d4f7618995 thanks for letting us know. It looks like there was a mistake when we tried to implement this and the volume was added to the Bitbucket NFS node instead of the Bitbucket webapp node. We've corrected that so the parameter should now work as intended and increase the root volume size of the Bitbucket webapp EC2 instance. You can get the latest version of the template here: https://aws.amazon.com/quickstart/architecture/bitbucket/

            Ben P (Inactive) added a comment - Hi d8d4f7618995 thanks for letting us know. It looks like there was a mistake when we tried to implement this and the volume was added to the Bitbucket NFS node instead of the Bitbucket webapp node. We've corrected that so the parameter should now work as intended and increase the root volume size of the Bitbucket webapp EC2 instance. You can get the latest version of the template here: https://aws.amazon.com/quickstart/architecture/bitbucket/
            Ben P (Inactive) made changes -
            Remote Link New: This issue links to "DC Deployments › AWS Quickstart - Bitbucket › SCALE-23-make-bitbucket-node-volume-configurable (server-syd-bamboo)" [ 505521 ]
            Ben P (Inactive) made changes -
            Remote Link New: This issue links to "ZDC Deployments › AWS Quickstart - Bitbucket › SCALE-23-make-bitbucket-node-volume-configurable (server-syd-bamboo)" [ 505520 ]
            Carlos Corredor made changes -
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Reviewing [ 11773 ]

            Rogier.Timmermans added a comment - - edited

            Executed a dry-run test of the AWS Quickstart template on 18-09-2020. The size of webnodes (ClusterNodeVolumeSize) can indeed be indicated in the template, however, the created resources remain at their default 8GB.

            I would expect that a newly spawned node would either init at 50G but they emerge with an 8G disk.

            Fix does not seem effective.

             

             

            Rogier.Timmermans added a comment - - edited Executed a dry-run test of the AWS Quickstart template on 18-09-2020. The size of webnodes (ClusterNodeVolumeSize) can indeed be indicated in the template, however, the created resources remain at their default 8GB. I would expect that a newly spawned node would either init at 50G but they emerge with an 8G disk. Fix does not seem effective.    
            Dylan Rathbone made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Dylan Rathbone added a comment - Fixed via: https://github.com/aws-quickstart/quickstart-atlassian-bitbucket/commit/89cd62a4be68dba385cf6c93b7a3d75b842002dd
            Dylan Rathbone made changes -
            Status Original: Reviewing [ 11773 ] New: In Progress [ 3 ]

              Unassigned Unassigned
              bannamalai Baskar Annamalai (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: