D
Dapeng Wu
Guest
Paul, There was indeed some discussion about a special maintenance mode for database in the past, but it didn't actually get started. This is a bigger project and I'll bring it back to the teams for more inputs. Besides replication, do you have other use cases for this maintenance mode? As to the offline syncRepl case, we also need to consider the time it may take to complete the sync. It can be very long before the database is fully shut down, depending on the transactions to back out. For the online case, there are some technical challenges for what has been described. For example, "ensure all AI notes for a transaction is completely send to all targets but any new transaction started, it's AI notes are send to the AI logs only". This will require changes to our crash recovery mechanism and it will be big. What can be relatively easier to do is to cut a line that no new transactions can be started before the existing ones get replicated.
Continue reading...
Continue reading...