Almost everyone thinks the current maintenance_mode does something more
consequential than removing the node from round-robin. +1 to using the name
we intuitively expect it to be. We can move the current maintenance_mode to
something else like hide_from_load_balancer (or whatever).

B.


On Mon, Apr 22, 2013 at 5:45 PM, Paul J. Davis <notifications@github.com>wrote:

> In src/fabric_db_update_listener.erl:
>
> > @@ -62,11 +62,12 @@ start_update_notifiers(DbName) ->
> >
> >  % rexi endpoint
> >  start_update_notifier(DbNames) ->
> > +    Notify = config:get("cloudant", "non_interactive_mode", "false") == "true",
>
> I thought about it but was unclear whether we should start mucking about
> with the current meaning of maintenance mode. I did think for awhile about
> renaming the whole bit to have something like: [maintenance_modes] http =
> true | false interactive = true | false etc... But then we get into a dance
> for upgrades so we don't accidentally pull things out of maintenance mode.
> Plus you get into a whole truth table effect if you try and get more
> granular.
> … <#13e33b5b6067a99a_>
> On Mon, Apr 22, 2013 at 4:09 PM, Adam Kocoloski <notifications@github.com>wrote:
> In src/fabric_db_update_listener.erl: > @@ -62,11 +62,12 @@
> start_update_notifiers(DbName) -> > > % rexi endpoint >
> start_update_notifier(DbNames) -> > + Notify = config:get("cloudant",
> "non_interactive_mode", "false") == "true", maintenance_mode? — Reply to
> this email directly or view it on GitHub<
> https://github.com/cloudant/fabric/pull/86/files#r3904819> .
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cloudant/fabric/pull/86/files#r3905585>
> .
>