Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restarting stream due to failure very often #463

Open
rmampuzha-aie opened this issue Oct 3, 2023 · 1 comment
Open

Restarting stream due to failure very often #463

rmampuzha-aie opened this issue Oct 3, 2023 · 1 comment

Comments

@rmampuzha-aie
Copy link

Akka version:
val postgresVersion = "42.3.4"
val akkaVersion = "2.8.3"
val akkaManagementVersion = "1.1.3"
val projectionVersion = "1.2.4"
val r2dbcPostgresVersion = "0.9.1.RELEASE"
val r2dbcPoolVersion = "0.9.0.RELEASE"
val r2dbcSpiVersion = "0.9.1.RELEASE"
val r2dbcVersion = "0.7.7"

Expected Behavior

Projection should be synched automatically.

Actual Behavior

Some times we get an error like below.
Restarting stream due to failure [8]: java.lang.IllegalStateException: Rejected envelope from backtracking, persistenceId [CustomerAccountEntity|AB_WEB_CHANNEL_a_616f082d-f21c-4a7d-b676-274c60d17853], seqNr [5] due to unexpected sequence number. Please report this issue at https: //github.com/akka/akka-persistence-r2dbc

The persistenceId, entity and seqnr may vary. In above particular case SeqNr is not in event_journal table but available in akka_projection_timestamp_offset_store. Hence other SEQ numbers are failing to synch.

Other observation is that, if there are any update happens to the same slice of this entity then automatically it get corrected.

@johanandren
Copy link
Member

Try updating to latest Akka Persistence R2DBC (1.1.2) and Akka Projections (1.4.2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants