Skip to content
  • Nuno Carvalho's avatar
    b4a7d68a
    BUG#26770576: ALL MEMBERS ARE EXITED FROM GR WHEN 1/3 NODE TRIED TO REJOIN AFTER SHUTDOWN · b4a7d68a
    Nuno Carvalho authored
    Problem: All members in group goes in ERROR STATE when new member joins and
    certification database is big
    
    Scenario (slow machine with heavy load):
    1. Start 3 server (MEMBER_1, MEMBER_2, MEMBER_3)
    2. Wait for all members to be ONLINE
    3. Start heavy load on MEMBER_1 (wait for 5 to 10 minutes) (MEMBER_2 and MEMBER_3 receives data slowly.)
    4. STOP, START MEMBER_3
    5. MEMBER_1 and MEMBER_2 goes offline
    
    Description: When new member joins server, certification database can be big.
    Certification database is transferred with View_change.
    If packet size(View_change) is greater then 4MB, GR stops and goes in error state.
    
    Resolution:
    Applier thread will be initialized with slave_max_allowed_packet, which default
    size is 1GB.
    b4a7d68a
    BUG#26770576: ALL MEMBERS ARE EXITED FROM GR WHEN 1/3 NODE TRIED TO REJOIN AFTER SHUTDOWN
    Nuno Carvalho authored
    Problem: All members in group goes in ERROR STATE when new member joins and
    certification database is big
    
    Scenario (slow machine with heavy load):
    1. Start 3 server (MEMBER_1, MEMBER_2, MEMBER_3)
    2. Wait for all members to be ONLINE
    3. Start heavy load on MEMBER_1 (wait for 5 to 10 minutes) (MEMBER_2 and MEMBER_3 receives data slowly.)
    4. STOP, START MEMBER_3
    5. MEMBER_1 and MEMBER_2 goes offline
    
    Description: When new member joins server, certification database can be big.
    Certification database is transferred with View_change.
    If packet size(View_change) is greater then 4MB, GR stops and goes in error state.
    
    Resolution:
    Applier thread will be initialized with slave_max_allowed_packet, which default
    size is 1GB.
Loading