[LU-19700] Reliable way to keep MGS NID tables in-sync with targets

• Type: Improvement
• Resolution: Unresolved
• Priority: Medium
• Severity: 3
• Assignee: Mikhail Pershin
• Reporter: Mikhail Pershin

Description

this is continuation of LU-19692 and is related to LU-10360/LU-10359. Right now IR itself is not reliable, it might improve recovery but not must and that is by design. If we are going to rely on IR to discover target NIDs then it should be improved to keep NID tables on MGS in valid state all the time. Right now NID tables are built when target starts and registers with MGS and when target network is changed. If MGS itself restarts all NID tables are gone and must be restored, which is solved by LU-19692, but it is still one time event at target side.

MGS itself should check that NID tables instances are consistent with its own instance after restart and ask targets for update if needed, especially when NID tables are read by client

Issue Links

• is related to: LU-19692 MGS NID tables are lost after failover and need to be rebuilt
• is related to: LU-10359 remove NIDs from config llogs