[Bug] The eventMesh server delivers messages to multiple node consumers through grpc, and manually kills the listening process, resulting in message loss

[linyf-B]

Search before asking

• I had searched in the issues and found no similar issues.

Environment

Linux

EventMesh version

1.10.0

What happened

Problem description: The server executes updateOffset, and the client ReceiveMsgHook.handle() does not receive the data on the stream.

Code link: On the gRPC stream push path, the runtime is after the server emitter.onNext succeeds in updateOffset (in StreamPushRequest). In the client, ReceiveMsgHook.handle() is executed after receiving the data on the gRPC stream, and is not included in the updateOffset decision condition.

Test scenario: version 1.10.0;
The scenario is dual consumer + Eventmesh pushed by gRPC; One of the processes was manually killed and restarted about a minute; The phenomenon is that the sum of the two consumers received < the number of Eventmesh sent, which is manifested as a lost message.

How to reproduce

Debug logs

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *

[github-actions]

Welcome to the Apache EventMesh community!!
We are glad that you are contributing by opening this issue. :D

Please make sure to include all the relevant context.
We will be here shortly.

If you are interested in contributing to our project, please let us know!
You can check out our contributing guide on contributing to EventMesh.

Want to get closer to the community?

WeChat Assistant	WeChat Public Account	Slack
		Join Slack Chat

Mailing Lists:

Name	Description	Subscribe	Unsubscribe	Archive
Users	User support and questions mailing list	Subscribe	Unsubscribe	Mail Archives
Development	Development related discussions	Subscribe	Unsubscribe	Mail Archives
Commits	All commits to repositories	Subscribe	Unsubscribe	Mail Archives
Issues	Issues or PRs comments and reviews	Subscribe	Unsubscribe	Mail Archives