-
Suggestion
-
Resolution: Fixed
-
None
-
None
-
None
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.
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