AlexanderKaraberov edited a comment on issue #2493: couch_auth_cache creates millions of monitors to _users.couch database which introduces a performance drop URL: https://github.com/apache/couchdb/issues/2493#issuecomment-579693850 Apparently this change breaks `cluster_setup` when I start the database from `/dev/run`. It tries to call `POST /_cluster_setup` on port `15984` and crashes here: ``` [error] 2020-01-29T09:25:04.211584Z node1@127.0.0.1 <0.406.0> 29e1339bd9 req_err(4046274191) unknown_error : badarg [<<"ets:lookup/2">>,<<"couch_auth_cache:exec_if_auth_db/2 L409">>,<<"couch_auth_cache:get_user_creds/2 L63">>,<<"couch_httpd_auth:default_authentication_handler/2 L96">>,<<"chttpd:authenticate_request/2 L531">>,<<"chttpd:process_request/1 L301">>,<<"chttpd:handle_request_int/1 L243">>,<<"mochiweb_http:headers/6 L128">>] ``` From what I see `default_authentication_handler` uses [couch_auth_cache here](https://github.com/apache/couchdb/blob/master/src/couch/src/couch_httpd_auth.erl#L89). I can workaround this but just curious whether this is some sort of a regression or an expected behaviour? `/cluster_setup` request is sent not to the `backend_port` (5986) but to a cluster port so I would expect `couch_auth_cache` to not be used in this particular case. *UPD:* This my fault. I had a wrong `local.ini` config. All works good.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services