El 28/05/16 a las 08:57, Nikhil escribió: > Once the node which was down is brought back the replication slot is not > turned active. The reason being replication slot is trying to create a > partition table which already exists. Because of this error replication > slot is stuck in inactive mode. Is there any way to ignore this error?
BTW, how did you end up in such a state? Did you create the partition table skipping ddl locking?
Nik>> skip_ddl_locking is set to True in my configuration. As this was preventing single
node from doing DDL operation (if one is down majority is not there for doing DDL on available node)
At this point the easiest way out is to drop the table on the node where it's trying to get applied with bdr_replication off or skip_ddl_replication on, so the table is dropped locally but not replicated, and the create table from the slot can be consumed.
The other option is to consume the create table statement from the slot directly.
Be aware of the dangers of changing the default values for such parameters, (bdr_replication, skip_ddl_replication, skip_ddl_locking) and when needed they should be used with special care.
Nik>>. The DDL replay is started once the node join back to bdr group. I think its started from an old check point causing partition already exists error. Is there any way to ignore replay error ? or ignore DDL errors while replay ?
