Jira AWS Add/Remove Nodes

Jira on AWS

Jira AWS Lifecycle

Add/Remove nodes via AWS Console

Select the Stack you used to deploy Jira.
Click the Update button.
On the Select Template page, leave Use current template selected and click Next.
On the Specify Details page, in the Cluster Node section of Parameters update the Minimum number of cluster nodes and the Maximum number of cluster nodes. If you set Minimum to 2 and Maximum to 2 this will cause the creation of a second Jira node in the other AZ to the first node. This may take some time. Wait for the operation to complete before continuing.
Check the Cluster nodes section of the Jira System Info page. You should see that the nodes now form a cluster.

Add nodes via AWS CLI

aws cloudformation describe-stacks --output yaml | grep StackName

To help identify your stack name if you don't remember it

mystack=mystackname

ClusterNodeMin=2

ClusterNodeMax=2

Set variables

aws cloudformation describe-stacks --stack-name ${mystack}

Parameter list was correct on 13-Jul-2020; newer versions of the Quick Start may affect the parameter list

aws cloudformation update-stack --stack-name ${mystack} --use-previous-template --parameters \

ParameterKey=ClusterNodeMin,ParameterValue=${ClusterNodeMin} \

ParameterKey=ClusterNodeMax,ParameterValue=${ClusterNodeMax} \

ParameterKey=JiraProduct,UsePreviousValue=true \

ParameterKey=JiraVersion,UsePreviousValue=true \

ParameterKey=PrivateSubnet2CIDR,UsePreviousValue=true \

ParameterKey=TomcatEnableLookups,UsePreviousValue=true \

ParameterKey=DBIops,UsePreviousValue=true \

ParameterKey=SSLCertificateARN,UsePreviousValue=true \

ParameterKey=QSS3KeyPrefix,UsePreviousValue=true \

ParameterKey=TomcatMinSpareThreads,UsePreviousValue=true \

ParameterKey=DBMaxWaitMillis,UsePreviousValue=true \

ParameterKey=DBStorageEncrypted,UsePreviousValue=true \

ParameterKey=BastionHostRequired,UsePreviousValue=true \

ParameterKey=DBTestOnBorrow,UsePreviousValue=true \

ParameterKey=VPCCIDR,UsePreviousValue=true \

ParameterKey=DeploymentAutomationPlaybook,UsePreviousValue=true \

ParameterKey=PublicSubnet1CIDR,UsePreviousValue=true \

ParameterKey=MailEnabled,UsePreviousValue=true \

ParameterKey=DBMultiAZ,UsePreviousValue=true \

ParameterKey=JvmHeapOverride,UsePreviousValue=true \

ParameterKey=QSS3BucketName,UsePreviousValue=true \

ParameterKey=DBRemoveAbandoned,UsePreviousValue=true \

ParameterKey=DBInstanceClass,UsePreviousValue=true \

ParameterKey=DBMasterUserPassword,UsePreviousValue=true \

ParameterKey=CloudWatchIntegration,UsePreviousValue=true \

ParameterKey=ClusterNodeInstanceType,UsePreviousValue=true \

ParameterKey=DBMinIdle,UsePreviousValue=true \

ParameterKey=PublicSubnet2CIDR,UsePreviousValue=true \

ParameterKey=DBPassword,UsePreviousValue=true \

ParameterKey=DeploymentAutomationCustomParams,UsePreviousValue=true \

ParameterKey=DBStorage,UsePreviousValue=true \

ParameterKey=TomcatMaxThreads,UsePreviousValue=true \

ParameterKey=InternetFacingLoadBalancer,UsePreviousValue=true \

ParameterKey=DeploymentAutomationBranch,UsePreviousValue=true \

ParameterKey=DBMaxIdle,UsePreviousValue=true \

ParameterKey=TomcatAcceptCount,UsePreviousValue=true \

ParameterKey=DBStorageType,UsePreviousValue=true \

ParameterKey=DBEngine,UsePreviousValue=true \

ParameterKey=AccessCIDR,UsePreviousValue=true \

ParameterKey=TomcatDefaultConnectorPort,UsePreviousValue=true \

ParameterKey=DBMinEvictableIdleTimeMillis,UsePreviousValue=true \

ParameterKey=DeploymentAutomationKeyName,UsePreviousValue=true \

ParameterKey=TomcatRedirectPort,UsePreviousValue=true \

ParameterKey=DBTestWhileIdle,UsePreviousValue=true \

ParameterKey=HostedZone,UsePreviousValue=true \

ParameterKey=CatalinaOpts,UsePreviousValue=true \

ParameterKey=KeyPairName,UsePreviousValue=true \

ParameterKey=CustomDnsName,UsePreviousValue=true \

ParameterKey=AvailabilityZones,UsePreviousValue=true \

ParameterKey=TomcatContextPath,UsePreviousValue=true \

ParameterKey=DBRemoveAbandonedTimeout,UsePreviousValue=true \

ParameterKey=ClusterNodeVolumeSize,UsePreviousValue=true \

ParameterKey=DBPoolMinSize,UsePreviousValue=true \

ParameterKey=DBTimeBetweenEvictionRunsMillis,UsePreviousValue=true \

ParameterKey=PrivateSubnet1CIDR,UsePreviousValue=true \

ParameterKey=DBEngineVersion,UsePreviousValue=true \

ParameterKey=ExportPrefix,UsePreviousValue=true \

ParameterKey=DBPoolMaxSize,UsePreviousValue=true \

ParameterKey=DeploymentAutomationRepository,UsePreviousValue=true \

ParameterKey=TomcatProtocol,UsePreviousValue=true

Wait for new node to be provisioned.

for iid in $(aws ec2 describe-instance-status --output yaml | grep InstanceId | tr -d ' ' | awk -F: '{ print $2 }')do echo -------------------------------------------------------------------------------------------- str=aws:cloudformation:logical-id aws ec2 describe-instances --instance-ids ${iid} --output table | grep "${str}" | sed 's/|//g' | tr -d ' ' | eval sed 's/${str}//' echo ---------------- aws ec2 describe-instances --instance-ids ${iid} --output table | grep PrivateIpAddress | head -1 | sed 's/|//g' | tr -d ' ' | sed 's/ss/ss /' aws ec2 describe-instances --instance-ids ${iid} --output table | grep PublicIp | head -1 | sed 's/|//g' | tr -d ' ' | sed 's/ss/ss /'done && echo --------------------------------------------------------------------------------------------

Check the Cluster nodes section of the Jira System Info page. You should see that the nodes now form a cluster.

Remove old nodes from Jira Cluster

NOTE: This should happen automatically from Jira 8.10

Bibliography

https://aws-quickstart.s3.amazonaws.com/quickstart-atlassian-jira/doc/jira-software-data-center-on-the-aws-cloud.pdf https://confluence.atlassian.com/jirakb/remove-abandoned-or-offline-nodes-in-jira-data-center-946616137.html

Page updated

Google Sites

Report abuse