BTW, is there a better strategy to this instead of brute forcing the limit to be larger? It seems to be a bad idea to keep over 1000 files open if I don’t even need to replicate them until a change occurs. It this a limitation of internal continuous replication? Should I be triggering one time replications using the database update notifications?
> On Jan 11, 2015, at 3:44 PM, Paul Okstad <[email protected]> wrote: > > Thank you for the quick reply. I am indeed using Ubuntu and indeed using SSL > so this is extremely relevant. I’ll try out the fixes and get back. > >> On Jan 11, 2015, at 3:35 PM, Alexander Shorin <[email protected]> wrote: >> >> On Mon, Jan 12, 2015 at 2:24 AM, Paul Okstad <[email protected]> wrote: >>> {error,emfile} >> >> emfile - too many open files. For thousand databases you might likely >> hit default ulimit for 1024 file handlers. >> See also this thread: >> http://erlang.org/pipermail/erlang-questions/2015-January/082446.html >> about other ways to solve this. For instance, on Ubuntu with upstart >> there is a bit different way to set process limits. >> >> -- >> ,,,^..^,,, >
