-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 10.10
-
Fix Version/s: 10.10-HF38, 11.4, 2021.0
-
Component/s: Bulk
-
Release Notes Summary:The Bulk scroller writes records downstream when the number of documents reaches a configured threshold.
-
Epic Link:
-
Tags:
-
Upgrade notes:
-
Team:PLATFORM
-
Sprint:nxplatform #21
-
Story Points:3
The default configuration for the scroller is to be atomic, which means that if the scroll fails there is no downstream activity,
The downstream records that contain the document ids are kept in memory and pushed downstream only when scrolling is completed.
It is possible to handles millions of records this way but it will cost few GB of memory.
This can turn into OOM for larger repository, in this case the configuration should be adapted:
<extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <property name="nuxeo.core.bulk.scroller.produceImmediate">true</property> ...
where records are produced downstream while the scroll continues, in the case of failure during scroll the action is partially processed.
We can alleviate the problem using a limit: use an atomic behavior unless we have more than 100k docs.
- is required by
-
NXP-29959 Have a way to limit the documents of a Bulk command (10.10)
- Resolved
- Is referenced in