Skip to content
  • Arnab Ray's avatar
    b2170c1c
    Bug#32004637 MULTIPLE PB2 FAILURES DUE TO NDB DICT TABLE NOT IDENTICAL TO DD TABLE · b2170c1c
    Arnab Ray authored
    Problem:
    --------
    
    The metadata check failed during auto sync of tables restored using
    the ndb_restore tool. This is a timing issue related to indexes
    that show up in 2 scenarios:
    
    1. When the indexes haven't been created in NDB Dictionary and the
       table has been picked up for auto sync.
    2. When the indexes have been created but aren't usable yet and the
       table has been picked up for auto sync.
    
    Fix:
    ----
    
    1. The missing indexes scenario was handled by an earlier fix by
       failing the sync as a temporary error following which the sync
       is retried. This is tweaked to not log an error message since
       it's expected behaviour.
    2. The second scenario is fixed by extending the above check for
       missing indexes by also looking at the state of the indexes
       and treating them as missing if they aren't online at that
       point in time. There's also a possibility that an index is
       created (but not online) in the gap between the initial index
       check and the more comprehensive metadata check that follows
       which also deals with indexes. The comparison of such indexes
       is skipped.
    
    Change-Id: I44e31f43ba4e082743eab59eab6b455d5db923fc
    b2170c1c
    Bug#32004637 MULTIPLE PB2 FAILURES DUE TO NDB DICT TABLE NOT IDENTICAL TO DD TABLE
    Arnab Ray authored
    Problem:
    --------
    
    The metadata check failed during auto sync of tables restored using
    the ndb_restore tool. This is a timing issue related to indexes
    that show up in 2 scenarios:
    
    1. When the indexes haven't been created in NDB Dictionary and the
       table has been picked up for auto sync.
    2. When the indexes have been created but aren't usable yet and the
       table has been picked up for auto sync.
    
    Fix:
    ----
    
    1. The missing indexes scenario was handled by an earlier fix by
       failing the sync as a temporary error following which the sync
       is retried. This is tweaked to not log an error message since
       it's expected behaviour.
    2. The second scenario is fixed by extending the above check for
       missing indexes by also looking at the state of the indexes
       and treating them as missing if they aren't online at that
       point in time. There's also a possibility that an index is
       created (but not online) in the gap between the initial index
       check and the more comprehensive metadata check that follows
       which also deals with indexes. The comparison of such indexes
       is skipped.
    
    Change-Id: I44e31f43ba4e082743eab59eab6b455d5db923fc
Loading