The reason why gpmetrics.gpcc_alert_history records segment down during rebalance.

Products

• VMware Tanzu Greenplum

Issue/Introduction

A record about segment down will be inserted into gpmetrics.gpcc_alert_history(replaces gpcc_alert_log starting from gpcc 6.6) whenever segment failure is dectected. Someone may find that when doing a rebalance operation(gprecoverseg -r), some new records will be inserted into this table.

Environment

Product Version: 6.20

Resolution

It's an expected behavior. That's because the unbalanced mirror(temporarily active as primary) will be stopped during the rebalance, and gpmetrics.gpcc_alert_history will also record such kind of segment failure.