[ 
https://issues.apache.org/jira/browse/SOLR-17192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844710#comment-17844710
 ] 

ASF subversion and git services commented on SOLR-17192:
--------------------------------------------------------

Commit a7769e9cd9d01473eb28a5d557f487c438888134 in solr's branch 
refs/heads/branch_9x from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a7769e9cd9d ]

SOLR-17192: Add "field-limiting" URP to catch ill-designed schemas (#2395)

The URPF, `NumFieldLimitingUpdateRequestProcessorFactory`, blocks all
update requests that go through `processAdd` if the core exceeds a
configurable threshold of fields.

The factory accepts two parameters: `maxFields` is a required integer
representing the maximum field threshold,  and `warnOnly` is an optional
boolean that (when enabled) has the URP chain log warnings instead of
blocking updates.

The factory is included in the default configset, with warnOnly=true and
maxFields=1000.  ('warnOnly' will be false starting in the 10.0 release)

---------

Co-authored-by: David Smiley <dsmi...@apache.org>


> Maximum-fields-per-core soft limit
> ----------------------------------
>
>                 Key: SOLR-17192
>                 URL: https://issues.apache.org/jira/browse/SOLR-17192
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Schema and Analysis
>    Affects Versions: main (10.0), 9.5.0
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> Solr isn't infinitely scalable when it comes to the number of fields in each 
> core/collection.  Most deployments start to experience problems any time a 
> core has upwards of a few hundred fields.  Usually this doesn't exhibit 
> itself right away. instead waiting until segment-merge or some other time to 
> rear its head.
> Sometimes users hit this through intentional schema design.  Often however, 
> it happens "accidentally" due to (mis-)use of Solr's "dynamic fields" feature.
> We should add a configurable soft-limit, of the type described in SOLR-17191, 
> to prevent users from unknowingly getting into this state.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to