Issue Summary

This is reproducible on Data Center: yes

Steps to Reproduce

1. Trigger full foreground or background re-index on a node 1
2. Start node 2

Expected Results

Node 2 index is healthy after startup and index contains all the changes introduced during full re-index.

Actual Results

The index might not reflect the change in issues indexing configuration for example if indexer of custom field changed.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available