Thanks Chris.
To be clear, the following manual reconfiguration sequence for the offline secondary node is required to keep the change stream going?
cfg = rs.conf();
cfg["members"][<array_index>]["votes"] = 0;
cfg["members"][<array_index>]["priority"] = 0;
rs.reconfig(cfg);
This is similar to how you would implement a manual failover for a two-node Primary-Secondary (no arbiter) replicaSet, correct?
Also, is there any server or client side configuration, such as enableMajorityReadConcern (from older MongoDB releases) that would allow the change stream listener to automatically recover from this condition?