Merge lp:~seuis398/mysql-mmm/reliable_virtual_ip into lp:mysql-mmm
Status: | Needs review |
---|---|
Proposed branch: | lp:~seuis398/mysql-mmm/reliable_virtual_ip |
Merge into: | lp:mysql-mmm |
Diff against target: |
61 lines (+19/-4) 2 files modified
lib/Agent/Helpers/Network.pm (+2/-2) lib/Monitor/Agents.pm (+17/-2) |
To merge this branch: | bzr merge lp:~seuis398/mysql-mmm/reliable_virtual_ip |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
mysql-mmm-core | Pending | ||
Review via email: mp+91789@code.launchpad.net |
Description of the change
Because there is a limit to the number of arp packet a switch can handle simultaneously, MMM arp packets can be ignored sometimes.
In that case, client host cannot access mysql db through virtual ip, because of wrong arp cache.
So, arp packet send interval need to be increased.
And... to make sure virtual ip is assigned exactly,
mmm_control executes "vip ping test" and displays the result. ("Net::Ping" is required.)
(Ex.) $ mmm_control show
db01(
db02(
Unmerged revisions
- 149. By SeWoong Jeon
-
To make sure vip is assigned exactly,
mmm_control executes "vip ping test" and displays the result.
"Net::Ping" is required.(Ex.) $ mmm_control show
db01(192.168. 56.10) master/ONLINE. Roles: writer( 192.168. 56.20)/ Ping_OK
db02(192.168. 56.11) master/ONLINE. Roles: reader( 192.168. 56.21)/ Ping_Error - 148. By SeWoong Jeon
-
Because there is a limit to the number of arp packet switch can handle simultaneously,
MMM arp packets can be ignored sometimes.
In that case, client host cannot access mysql db through virtual ip, because of wrong arp cache.