GitHub user rsmidt added a comment to the discussion: Artifical back pressure on JDBC projections
For others having similar issues: After working on this for a while, I can confidently say that the solution worked out just fine. However, after rolling it out, I've realized a second issue: given that we have 105 tags, filling up the buffer (with a default size of 500 events) for each tagged projector instance results in ~50k rows being fetched more or less simultaneously. This also blocks the DB pool for too long, resulting in throttling in other parts of the application. Coincidentally, this was merged two weeks ago: https://github.com/apache/pekko-persistence-jdbc/commit/6f420d289378c2b80e65861096a2c1feb7a84afe. This configuration property is precisely what we need. We'll keep playing around with it and the `max-buffer-size` to see what our system can tolerate. Again, @pjfanning thanks a lot! GitHub link: https://github.com/apache/pekko/discussions/2431#discussioncomment-15229362 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
