The GitHub Actions job "Validate and test" on 
pekko-persistence-r2dbc.git/persistence-journal-batching has failed.
Run started by GitHub user minjibir (triggered by minjibir).

Head commit for run:
ebb063f7230bbca763d1e0776b32937a607faf2d / Jabir Minjibir 
<[email protected]>
feat: add opt-in batched write journal to coalesce concurrent writes (#471)

Motivation:
Under high concurrency across many persistence IDs, the default journal issues
separate statements and commits for each write. This increases database 
round-trips
and connection pool contention.

Modification:
- Add R2dbcBatchJournal to queue writes and flush them in batches.
- Add a separate batched-journal plugin id that inherits from the journal block.
- Add max-queue-size, max-batch-size and max-batch-time configuration settings.
- Reject writes on queue overflow and require the postgres or yugabyte dialect,
  use-app-timestamp and db-timestamp-monotonic-increasing at startup.
- Add R2dbcBatchJournalSpec to verify TCK compliance, plus batching, validation,
  failure isolation, publish timestamp and queue limit specs.
- Add R2dbcBatchJournalPerfSpec and R2dbcBatchJournalPerfManyActorsSpec for
  performance testing.

Result:
Users can opt in to batched writes across persistence IDs for higher write
throughput. The change is additive: no existing class is modified.

Tests:
- sbt "core / Test / testOnly 
org.apache.pekko.persistence.r2dbc.journal.R2dbcBatchJournal*" (75 tests, live 
PostgreSQL)
- sbt "core / Test / testOnly 
org.apache.pekko.persistence.r2dbc.journal.R2dbcBatchJournalSpec"
- sbt +headerCheckAll
- sbt scalafmtCheckAll
- sbt +mimaReportBinaryIssues
- sbt docs/paradox
- validatePullRequest task not present on this branch; equivalents run manually

References:
Fixes #471

Report URL: 
https://github.com/apache/pekko-persistence-r2dbc/actions/runs/34404819386

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to