revert: restore blocking await for sequential CDC consumption
The previous change was wrong - running sequential consumption in background defeats its purpose. The whole point is to ensure data dependency order (users -> referrals -> adoptions) before any other operations can proceed. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
a01fd3aa86
commit
22523aba14
|
|
@ -297,12 +297,10 @@ export class CDCConsumerService implements OnModuleInit, OnModuleDestroy {
|
|||
this.sequentialMode = true;
|
||||
this.isRunning = true;
|
||||
|
||||
// 开始顺序消费(后台运行,不阻塞服务启动)
|
||||
this.startSequentialConsumption().catch((error) => {
|
||||
this.logger.error('Sequential consumption failed', error);
|
||||
});
|
||||
// 开始顺序消费(阻塞直到完成,确保数据依赖顺序正确)
|
||||
await this.startSequentialConsumption();
|
||||
|
||||
this.logger.log('CDC consumer started with sequential phase consumption (running in background)');
|
||||
this.logger.log('CDC consumer started with sequential phase consumption');
|
||||
} catch (error) {
|
||||
this.logger.error('Failed to start CDC consumer', error);
|
||||
// 不抛出错误,允许服务在没有 Kafka 的情况下启动(用于本地开发)
|
||||
|
|
|
|||
Loading…
Reference in New Issue