Skip to content
This repository has been archived by the owner on Jul 14, 2024. It is now read-only.

Project not found at startup because maxScan reached on model mongo queries #175

Open
mdutoo opened this issue Aug 19, 2016 · 0 comments
Open

Comments

@mdutoo
Copy link
Collaborator

mdutoo commented Aug 19, 2016

(found by @bobeal in preprod, and myself locally in other cases)
19-08-2016 12:05:19 LoadPersistedModelsAtInit [ERROR] Datacore - unknown error initing org.oasis.datacore.model.resource.LoadPersistedModelsAtInit java.lang.RuntimeException: Unexpected Exception reloading project resource from persistence {"@id":"http://data.ozwillo.com/dc/type/dcmp:Project_0/oasis.sandbox" ... Cause by: org.oasis.datacore.core.entity.query.QueryException: Query or sort on collection oasis.meta.dcmi:mixin_0 with non indexed fields has reached maxScan (300) before document limit (found 74<100) , meaning some documents can't be found without prohibitive cost. Use only indexed fields, or if you really want the few documents already found lower limit, or if in Model design mode add indexes. Retry in debug mode to get more information.

Workaround : remove maxScan constraint for metamodel queries (oasis.meta.dcmi:mixin_0, or even oasis.meta.* for also projects).

Solution : maybe prefix existing indexes ex. _p.dcmo:globalFields.dcmf:name (which was allowed by #168 field.isStorage) by _b, but shouldn't they be used anyway ?

mdutoo pushed a commit that referenced this issue Aug 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant