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

Records missing in table with pg source after recovery: ERROR: cannot advance replication slot to BBD/75A6E068, minimum is BBD/7C5604E8 #16758

Closed
kwannoel opened this issue May 14, 2024 · 4 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@kwannoel
Copy link
Contributor

ERROR: cannot advance replication slot to BBD/75A6E068, minimum is BBD/7C5604E8
	
{
  "timestamp": "2024-05-14T18:57:05.23244688Z",
  "level": "WARN",
  "fields": {
    "message": "Cannot seek to the last known offset 'BBD/75A6E068' on replication slot '...'. Error from server: 'ERROR: cannot advance replication slot to BBD/75A6E068, minimum is BBD/7C5604E8': org.postgresql.util.PSQLException: ERROR: cannot advance replication slot to BBD/75A6E068, minimum is BBD/7C5604E8\n\tat org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2676)\n\tat org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2366)\n\tat org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:356)\n\tat org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:496)\n\tat org.postgresql.jdbc.PgStatement.execute(PgStatement.java:413)\n\tat org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:333)\n\tat org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:319)\n\tat org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:295)\n\tat org.postgresql.jdbc.PgStatement.execute(PgStatement.java:290)\n\tat io.debezium.connector.postgresql.connection.PostgresReplicationConnection.validateSlotIsInExpectedState(PostgresReplicationConnection.java:438)\n\tat io.debezium.connector.postgresql.connection.PostgresReplicationConnection.startStreaming(PostgresReplicationConnection.java:407)\n\tat io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:143)\n\tat io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:42)\n\tat io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:272)\n\tat io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:197)\n\tat io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:137)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:829)\n",
    "thread": "debezium-postgresconnector-RW_CDC_210002-change-event-source-coordinator",
    "class": "io.debezium.connector.postgresql.connection.PostgresReplicationConnection"
  },
  "target": "risingwave_connector_node"
}
@kwannoel kwannoel added the type/bug Something isn't working label May 14, 2024
@github-actions github-actions bot added this to the release-1.10 milestone May 14, 2024
@tabVersion
Copy link
Contributor

tabVersion commented May 14, 2024

Seems the position BBD/75A6E068 has been released, ie. we are resetting reading position to a committed one, please update the root cause in this issue. I wonder if the case applies to other sources.

@StrikeW
Copy link
Contributor

StrikeW commented May 15, 2024

v1.8.1 doesn't include the patch of #16321, we reverted the patch from v1.8.1 before. So it is expected this cluster encounter this problem.

@kwannoel
Copy link
Contributor Author

v1.8.1 doesn't include the patch of #16321, we reverted the patch from v1.8.1 before. So it is expected this cluster encounter this problem.

Which version will this be fixed?

@StrikeW
Copy link
Contributor

StrikeW commented May 15, 2024

v1.8.1 doesn't include the patch of #16321, we reverted the patch from v1.8.1 before. So it is expected this cluster encounter this problem.

Which version will this be fixed?

v1.9.0 will fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants