Open bookshelfdave opened 10 years ago
Either 1) All things that use repl2_leader events (like the cluster manager) need to die when the repl2_leader dies 2) the notification hooks need to be stored somewhere that can tolerate a repl2_leader death (ETS table that gets passed back to some supervisor) 3) Things that use repl2_leader events need to monitor it and re-register on restart. 4) repl2 leader events could be converted to use gen_event and reuse the riak_core_guarded_event_handler.
I'm tending to favor 4 as it uses existing otp behaviors. It also models what we want most closely. I was unable to find riak_core_guarded_event_handler.
Moving to 2.1.