Currently there is no in-memory value of configOpTime maintained on config servers (unlike shards/mongos), and instead when config servers gossip out configOpTime they just pull the latest commit point value from repl. In order to normalize the handling of configOpTime (mostly in SERVER-46200), relative to other logical/vector clocks in the system, we would like to push the new commit point optime into an in-memory location on config servers when replication notices that it has been updated.