After downgrading a Multi Server hubs cloud running on 4 AWS c5.12xlarge instances via the cloudformation template back to t3.small ec2-instances clients get instant 502 Bad Gateway errors.
Cloud Formation update didn't report any errors.
for my 4 ec2 instances there may be an imbalance with how the traffic is being routed to each one, for two of them there is a frequent high CPUUtilization load from examining my CloudWatch logs while on the two other instances there seems to have been a traffic drop-off. This may confirm that the AutoScaling groups are not configured as expected.
Does anyone have an idea what could be the root cause to this problem?
Hi,
After downgrading a Multi Server hubs cloud running on 4 AWS c5.12xlarge instances via the cloudformation template back to t3.small ec2-instances clients get instant 502 Bad Gateway errors. Cloud Formation update didn't report any errors.
for my 4 ec2 instances there may be an imbalance with how the traffic is being routed to each one, for two of them there is a frequent high CPUUtilization load from examining my CloudWatch logs while on the two other instances there seems to have been a traffic drop-off. This may confirm that the AutoScaling groups are not configured as expected.
Does anyone have an idea what could be the root cause to this problem?
best regards
┆Issue is synchronized with this Jira Task