Skip to content

fix(cost): add restart policy to mc-cost-optimizer-db - #90

Merged
MZC-CSC merged 1 commit into
developfrom
fix/cost-optimizer-db-restart
Sep 30, 2026
Merged

MZC-CSC merged 1 commit into
developfrom
fix/cost-optimizer-db-restart

Conversation

@dogfootman

Copy link
Copy Markdown
Collaborator

문제

서버 재가동 후 mc-cost-optimizer-db만 다시 올라오지 않았습니다.

  • conf/docker/docker-compose.yaml의 mc-cost-optimizer-db에 restart 설정이 없어 기본값 no가 적용됩니다.
  • BE·collector 등 의존 서비스(restart: on-failure)는 UnknownHostException: mc-cost-optimizer-db로 재시작을 반복하고, BE는 unhealthy 상태가 되어 /api/costopti/be/invoice/getInvoice 등이 실패했습니다.

변경

  • mc-cost-optimizer-db에 restart: always 추가 (같은 파일의 다른 DB 서비스와 동일)

반영

기존 컨테이너는 재생성해야 적용됩니다: docker compose up -d mc-cost-optimizer-db (데이터 볼륨 유지, 이미지 12.3.2 동일)
또는 docker update --restart always mc-cost-optimizer-db

mc-cost-optimizer-db had no restart policy (default: no), so it was not
brought back after a host reboot while the dependent cost services
(restart: on-failure) kept crash-looping on UnknownHostException.
Align with other DB services in the file by using restart: always.
@MZC-CSC
MZC-CSC merged commit b40b9be into develop Sep 30, 2026
1 check passed
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.

3 participants