• Julien Muchembled's avatar
    master: fix possibly wrong knowledge of cells' backup_tid when resuming backup · 17af3b47
    Julien Muchembled authored
    The issue happens when there were commits while the backup cluster was down.
    In this case, the master thinks that these commits are already replicated,
    reporting wrong backup_tid to neoctl. It solved by itself once:
    - there are new commits triggering replication for all partitions;
    - all storage nodes have really replicated.
    
    This also resulted in an inconsistent database when leaving backup mode during
    this period.
    17af3b47
Name
Last commit
Last update
neo Loading commit data...
tools Loading commit data...
.coveragerc Loading commit data...
.gitignore Loading commit data...
BUGS.rst Loading commit data...
CHANGELOG.rst Loading commit data...
COPYING Loading commit data...
MANIFEST.in Loading commit data...
README.rst Loading commit data...
TODO Loading commit data...
UPGRADE.rst Loading commit data...
ZODB3.patch Loading commit data...
importer.conf Loading commit data...
neo.conf Loading commit data...
neoadmin Loading commit data...
neoctl Loading commit data...
neolog Loading commit data...
neomaster Loading commit data...
neomigrate Loading commit data...
neostorage Loading commit data...
setup.py Loading commit data...