[GitHub] [couchdb-documentation] nickva edited a comment on pull request #617: [rfc] Fair Share Replication Scheduler

[GitBox <gi...@apache.org>]

nickva edited a comment on pull request #617:
URL: https://github.com/apache/couchdb-documentation/pull/617#issuecomment-768421797


   > For the configuration: have you considered doing this perhaps via design docs (or something like that)? I think that would be closer in "online-ness" to the databases.
   
   Interesting idea. Would it be, say, any design document which has a "replicator_config" field in it and we'd merge those, or have a single (special) doc id like "_design/replicator_config"?  That might work, but I am also thinking this is for a 3.x branch and I would be hesitant to add a whole new configuration mechanism.
   
   > Ie. I can create-update-delete replicator databases, but to configure shares for them, I'd have to edit config (files and/or via the HTTP API - which is then either lost or gets splatted on restart unless I do some double booking).
   
   We do have precedent of configuring per-db settings in other application such as in [ken](https://github.com/apache/couchdb/blob/3.x/src/ken/src/ken_server.erl#L264)  and [smoosh](https://github.com/apache/couchdb/blob/3.x/src/smoosh/src/smoosh_utils.erl#L54). Settings applied via HTTP should not get lost, if they do it's a bug. They get written to the config files on disk. Where you thinking about needing to set it on every node perhaps? Yeah we'd have call config on very node if the setting is set via HTTP, and that's not ideal but probably too late to change in 3.x at this point.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org