feat: MySQL Replication 수행 #420
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test Results64 tests 64 ✅ 2s ⏱️ Results for commit 63357ef. ♻️ This comment has been updated with latest results. |
penrose15
reviewed
Sep 12, 2024
module-infrastructure/persistence-database/src/main/java/com/depromeet/config/JpaConfig.java
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🌱 관련 이슈
📌 작업 내용 및 특이사항
MySQL 이중화를 위한 어플리케이션 설정 변경을 수행하였습니다.Master, Slave 대신
Primary, Secondary라는 명칭을 사용하였습니다.Primary노드는INSERT, UPDATE, DELETE를 수행합니다.Secondary노드는 오로지 쿼리GET만을 수행합니다.Primary에 새로운 레코드나 수정 사항이 생기면
Primary 노드의바이너리 로그에 쓰여집니다.바이너리 로그에 쓰여지면 Primary 노드의 덤프 쓰레드가 변경 사항을
Secondary 노드의 I/O 쓰레드에 이를 전달합니다.Secondary I/O 노드는 변경 사항을 받아 이를
릴레이 로그에 씁니다.릴레이 로그에 쓰여진 이후
Secondary 노드에SQL 쓰레드가 변경 사항에 대해 이를기록합니다.📝 참고사항