FYI, i checked to code and it's indeed the host or domain limit that's
responsible for the OOM. The score is ok as it's not being accumulated
anyway. Anyone can work around the problem by either increasing the heap
space allocated to the reducers or, significantly increase the number of
reducer
Hi,
We sometimes see the generator running OOM. This happens because we
either have a too high topN value or too many segments to generate. In
any case, a very large amount of records is being generated with the
same (lowest) score and end up in a single reducer. We limit the
generator by dom
2 matches
Mail list logo