반응형
노드 재동기화 후 Galera 클러스터 성능 저하
MariaDB 10.4의 Galera 마스터-마스터 클러스터와 복제 lib의 Galera-4를 얻었습니다.일부 노드와 다른 노드 간에 네트워크 문제가 발생할 때까지 완벽하게 실행됩니다.노드를 다시 연결하고 다시 동기화하면 전체 클러스터 성능이 크게 저하됩니다.성능을 복원하는 유일한 방법은 기증자 노드에서 전체 클러스터를 재구성하는 것입니다.
로그에 기록된 내용은 다음과 같습니다.
2023-03-19 1:23:20 0 [Note] WSREP: ####### Adjusting cert position: 61149358 -> 61149359
2023-03-19 1:23:20 0 [Note] WSREP: Service thread queue flushed.
2023-03-19 1:23:20 0 [Note] WSREP: Lowest cert index boundary for CC from ist: 61149189
2023-03-19 1:23:20 0 [Note] WSREP: Min available from gcache for CC from ist: 60988106
2023-03-19 1:23:20 0 [Note] WSREP: Receiving IST...100.0% (545/545 events) complete.
2023-03-19 1:23:21 2 [Note] WSREP:
================================================ View: id: 6caf7137-be5b-11ed-952d-8e2998c314a7:61149359 status: primary protocol_version: 4 capabilities: MULTI-MASTER, CERTIFICATION, PARALLEL_APPLYING, REPLAY, ISOLATION, PAUSE, CAUSAL_READ, INCREMENTAL_WS, UNORDERED, PREORDERED, STREAMING, NBO final: no own_index: 2 members(4):
0: 38ac2156-c3e1-11ed-b954-ba79e6d7687d, DB1
1: 637c05dc-c17f-11ed-b3f2-0e364b289bef, DB3
2: 667386bc-c5db-11ed-ad68-ee03169ac5b9, DB4
3: c9c34048-c3e0-11ed-8cbc-13957f2241e4, DB2
=================================================
2023-03-19 1:23:21 2 [Note] WSREP: Server status change initialized -> joined
2023-03-19 1:23:21 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2023-03-19 1:23:21 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2023-03-19 1:23:21 2 [Note] WSREP: Draining apply monitors after IST up to 61149359
2023-03-19 1:23:21 2 [Note] WSREP: IST received: 6caf7137-be5b-11ed-952d-8e2998c314a7:61149359
2023-03-19 1:23:21 2 [Note] WSREP: Lowest cert index boundary for CC from sst: 61149189
2023-03-19 1:23:21 2 [Note] WSREP: Min available from gcache for CC from sst: 60988107
2023-03-19 1:23:21 0 [Note] WSREP: 2.0 (DB4): State transfer from 3.0 (DB2) complete.
2023-03-19 1:23:21 0 [Note] WSREP: Shifting JOINER -> JOINED (TO: 61149618)
2023-03-19 1:23:21 0 [Note] WSREP: Processing event queue:... 0.0% ( 0/260 events) complete.
2023-03-19 1:23:32 2 [Note] WSREP: Processing event queue:... 56.8% (208/366 events) complete.
2023-03-19 1:23:40 0 [Note] WSREP: Member 2.0 (DB4) synced with group.
2023-03-19 1:23:40 0 [Note] WSREP: Processing event queue:...100.0% (402/402 events) complete.
2023-03-19 1:23:40 0 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 61149756)
2023-03-19 1:23:43 2 [Note] WSREP: Server DB4 synced with group.
2023-03-19 1:23:43 2 [Note] WSREP: Server status change joined -> synced
2023-03-19 1:23:43 2 [Note] WSREP: Synchronized with group, ready for connections
2023-03-19 1:23:43 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2023-03-19 1:23:59 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61150337, -110 (Connection timed out)
2023-03-19 1:24:15 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61151132, -110 (Connection timed out)
2023-03-19 1:24:17 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61151205, -110 (Connection timed out)
2023-03-19 1:24:23 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61151478, -110 (Connection timed out)
2023-03-19 1:24:33 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61151724, -110 (Connection timed out)
2023-03-19 1:24:38 0 [Note] InnoDB: Buffer pool(s) load completed at 230319 1:24:38
2023-03-19 1:24:41 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61152114, -110 (Connection timed out)
2023-03-19 1:24:43 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61152261, -110 (Connection timed out)
2023-03-19 1:24:46 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61152364, -110 (Connection timed out)
2023-03-19 1:27:32 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61158126, -110 (Connection timed out)
2023-03-19 1:27:36 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61158269, -110 (Connection timed out)
2023-03-19 1:27:40 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61158385, -110 (Connection timed out)
2023-03-19 1:27:47 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61158486, -110 (Connection timed out)
2023-03-19 1:28:12 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61159789, -110 (Connection timed out)
2023-03-19 1:28:15 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61159889, -110 (Connection timed out)
2023-03-19 1:28:18 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61160056, -110 (Connection timed out)
2023-03-19 1:28:21 0 [Warning] WSREP: Failed to report last committed 6caf7137-be5b-11ed-952d-8e2998c314a7:61160171, -110 (Connection timed out)
내 wsrep 구성:
[galera]
wsrep_on=ON
wsrep_provider=/usr/lib/libgalera_smm.so
wsrep_cluster_address="gcomm://xx.xx.xx.xxx,xxx.xx.xx.xxx,xx.xxx.xx.xxx,xx.xxx.xxx.xx"
wsrep_sst_method=mariabackup
wsrep_sst_auth=xxxxxxxxx:xxxxxxxxx
binlog_format=row
default_storage_engine=InnoDB
innodb_autoinc_lock_mode=2
wsrep_cluster_name="xxxxxxx"
wsrep_node_address="xx.xxx.xxx.xx"
wsrep_node_name="DBX"
이 성능 문제의 원인과 해결 방법은 무엇입니까?살려주세요.
언급URL : https://stackoverflow.com/questions/75780946/galera-cluster-perfomance-degradation-after-node-resync
반응형
'bestsource' 카테고리의 다른 글
| 파워셸에서 처분하지 않는 것은 얼마나 나쁜 일입니까? (0) | 2023.08.17 |
|---|---|
| Git 소스 제어 하에서 지속적으로 변화하는 IntelliJ IDEA 프로젝트 파일을 처리하는 방법은 무엇입니까? (0) | 2023.08.17 |
| C# IT 유형 정보.VBA 클래스의 라이브 인스턴스를 전달할 때 GetContainingTypeLib가 실패함 (0) | 2023.08.17 |
| 잘못된 구문에 대한 MariaDB에 대한 HeidiSQL 오류 (0) | 2023.08.17 |
| PowerShell: csv 파일에서 행 수를 계산하는 방법은 무엇입니까? (0) | 2023.08.17 |