Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-3102

The xxx_config_listener doesn't restart after a failure

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      The config_listener_mon monitors the caller.
      However in lots of places we use following pattern

      handle_config_terminate(_Server, _Reason, State) ->
          spawn(fun() ->
              timer:sleep(5000),
              config:listen_for_changes(?MODULE, State)
          end).
      

      In this case the spawned fun exits right after the monitor has been established.
      Which means config_listener_mon would terminate. Effectively removing event handler from config_event process (gen_event event manager).
      When this happen any further configuration changes get unnoticed by processes.

      Attachments

        Activity

          People

            Unassigned Unassigned
            iilyak Ilya Khlopotov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: