Chris LuandGitHub c438c5ef94 filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427) ...

* filer.replicate: commit the kafka offset after replicating, not on receipt

The partition consumer committed the offset as soon as it handed the message
to the channel, so a sink write that failed was logged and the message was
already behind the committed offset -- never redelivered, permanently missing
from the sink.

Commit in onSuccessFn instead, and hold the committed offset behind the
oldest offset that failed to replicate so a restart redelivers from there.

* filer.replicate: delete the sqs message after replicating, not on receipt

ReceiveMessage deleted the message before the replicator had a chance to run,
so a failed sink write dropped it for good. Move the delete into onSuccessFn
and leave the message in the queue otherwise, letting the visibility timeout
redeliver it.

2026-07-24 10:43:48 -07:00

..

notification_aws_sqs.go

filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427)

2026-07-24 10:43:48 -07:00

notification_gocdk_pub_sub.go

go fix

2026-02-20 18:42:00 -08:00

notification_google_pub_sub.go

move proto package

2022-08-17 12:05:07 -07:00

notification_kafka_test.go

filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427)

2026-07-24 10:43:48 -07:00

notification_kafka.go

filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427)

2026-07-24 10:43:48 -07:00

notifications.go

move to https://github.com/seaweedfs/seaweedfs

2022-07-29 00:17:28 -07:00