Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
5.3
-
None
-
None
Description
Some actions can be very expensive for some specific fields. For example, in my test, a facet query on a text field blow up a few servers in minutes. The reason is probably Solr does 'uninversion' on this field for facet which uses large amount of field cache. Several Solr servers in turn go into back to back full GC cycles and eventually OOM. To prevent scenarios like this, it's useful to add an option to allow user to decide if some action is allowed for a specific field, particularly for actions using field cache.
There are two ways to design the switch. It can be either for specific action, such as facet, statistic, sorting or for a group of actions, such as all actions doing 'uninversion'.
Some more details about my test. It is a 33-node Solr cluster There is one collection on HDFS with 2.6 billion documents in 30 shards.
Attachments
Issue Links
- relates to
-
SOLR-8273 deprecate implicitly uninverted fields, force people to either use docValues, or be explicit that they want query time uninversion
- Open