You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2021/03/30 15:14:30 UTC

[GitHub] [couchdb] kocolosk commented on pull request #3468: Improve search for FDB cluster files

kocolosk commented on pull request #3468:
URL: https://github.com/apache/couchdb/pull/3468#issuecomment-810344773


   I would be open to downgrading the permissions check to a non-fatal error message. I suspect we could end up with a lot of situations where CouchDB refuses to start but the ability to modify the cluster file is a non-issue; e.g. it's a single-server deployment, or a cluster where the FDB server nodes are co-located with the CouchDB nodes (and likely able to modify the cluster file themselves).
   
   The situation we're concerned about is where CouchDB is running as a stateless node and only using the local FDB client to communicate with a remote FDB cluster, _and_ that cluster's coordinators end up changing over time, _and_ there's no out-of-band mechanism to ensure the cluster file gets updated on the CouchDB nodes. It's a fairly sophisticated scenario, and I'd be comfortable with CouchDB logging an error message on startup along with some documentation about the appropriate permissions.


-- 
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