-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Atlas Streams
-
ALL
-
Sprint 59, Sprint 62
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We want to avoid cases where $lookup or the new $externalAPI takes 10s of minutes to process a single DataMsg. We decided to change DataMsg size from 50000 docs / 16 MB to 100 docs / 1MB to address this issue. Basically, we want to re-commit this change which got needed to be reverted due to some test failures.
- duplicates
-
SERVER-96157 Decouple $merge batch size from kDataMsgMaxDocSize.
-
- Closed
-
- has to be done after
-
SERVER-96157 Decouple $merge batch size from kDataMsgMaxDocSize.
-
- Closed
-
- is related to
-
SERVER-96157 Decouple $merge batch size from kDataMsgMaxDocSize.
-
- Closed
-
- mentioned in
-
Page Loading...