Skip to content

chore: queue-service 다중 EC2 순차 배포 적용 - #19

Merged
LimJinKeon merged 1 commit into
devfrom
chore/deploy-queue-to-multiple-ec2
May 19, 2026
Merged

chore: queue-service 다중 EC2 순차 배포 적용#19
LimJinKeon merged 1 commit into
devfrom
chore/deploy-queue-to-multiple-ec2

Conversation

@kjp0411

@kjp0411 kjp0411 commented May 19, 2026

Copy link
Copy Markdown
Contributor

📎 관련 이슈

📌 작업 내용

  • queue-service CD workflow의 배포 대상을 기존 단일 EC2에서 main-1, main-2 EC2 2대로 확장했습니다.
  • main-1 배포 및 health check 성공 후 main-2를 배포하도록 순차 배포 구조를 적용했습니다.
  • 각 EC2에서 최신 ticketing-system compose 설정을 반영한 뒤 queue-service 컨테이너를 재생성하도록 구성했습니다.

✨ 변경 사항

  • Deploy queue-service to main-1 EC2 step 추가
  • Deploy queue-service to main-2 EC2 step 추가
  • 각 서버 배포 후 http://localhost:20007/actuator/health 기반 health check 추가
  • main-1, main-2 각각 Docker image prune 수행
  • 기존 GHCR image build/push 방식은 유지
  • 기존 테스트 단계의 QUEUE_TOKEN_SECRET 설정은 유지

📝 리뷰 포인트 (선택)

  • EC2_HOST_2 GitHub Actions Secret이 추가되어 있어야 정상 동작합니다.
  • 배포는 main-1 → main-2 순서로 진행됩니다.
  • main-1 배포 또는 health check가 실패하면 main-2 배포로 넘어가지 않도록 구성했습니다.
  • user-service에서 검증한 다중 EC2 순차 배포 패턴을 queue-service에 동일하게 적용했습니다.

🧠 기타 참고 사항

  • 기존 EC2_HOST는 main-1 EC2를 의미합니다.
  • EC2_HOST_2는 main-2 EC2를 의미합니다.
  • ALB 뒤의 두 애플리케이션 서버가 동일한 queue-service 버전을 실행하도록 배포 흐름을 정리했습니다.

@coderabbitai

coderabbitai Bot commented May 19, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@kjp0411 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 27 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 15ba5c2a-8739-41a4-af4b-c59f0742659b

📥 Commits

Reviewing files that changed from the base of the PR and between 52548d8 and f131f45.

📒 Files selected for processing (1)
  • .github/workflows/queue-service-deploy.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/deploy-queue-to-multiple-ec2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@LimJinKeon
LimJinKeon merged commit 9b7a020 into dev May 19, 2026
3 checks passed
@LimJinKeon
LimJinKeon deleted the chore/deploy-queue-to-multiple-ec2 branch May 19, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[chore] queue-service 다중 EC2 순차 배포 적용

2 participants