You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: