Need to define OVSDB Clustering/Data Persistence Behavior

I’m facing some problems with clustering in SFC and stumbled on an issue with OVSDB

The access pattern is the following:

OpenvSwitch connects to ODL
OVSDB creates data in config datastore
SouthBound OVDSDB creates data in operational datastore
SFC listens to OVSDB operational store changes
SFC creates corresponding switch in SFC
Now let’s add clustering to the mix.

If ODL reboots:

OVSDB and SFC will have data for a switch that does not exist (yet) until it connects
Now, let’s suppose the OVS switch never reconnects. What then?

Will OVSDB keep this stale data around? How long will it wait until the switch reconnects?
If switch reconnects, will data in the OVSDB operational datastore be overwritten? One could assume switch configuration changed between ODL reboots.

All this is unclear to me and have profound impacts on how SFC works and need to be defined if clustering is going to be enabled.