[COUCHDB-3325] Track _replicator/_user shards with LRU

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Assignee: Unassigned
• Reporter: Robert Newson
• Created: 14/Mar/17 21:54
• Updated: 21/Mar/17 10:41
• Resolved: 21/Mar/17 10:41

Description

We excluded _replicator and _users databases from the LRU many years ago, before clustering.

It is now possible to make many _replicator and _users databases (and clustering multiples this effect).

A couchdb cluster can degrade considerably in the presence of many of these databases even when they are empty and idle. They consume resources but are never closed.

Let's include all sys_db databases in the LRU. Any active ones will remain open anyway, that's the point of an LRU.

Issue Links

• links to: GitHub Pull Request #237