Dear John
To overcome this issue what parameters I have to add in consumer side??
Please tell me if settings required I'll put it in that ..
Thanks..
Sent from Outlook
Hi Ashok,
In general, what Ryanne said is correct. For example, if you send an
email, and the send times out (but the email actually did get sent),
your app cannot distinguish this from a failure in which the send
times out before the email makes it out. Therefore, your only option
would be to ret
Kafka only supports exactly-once and idempotency within the context of
streams apps where records are consumed and produced within the same
cluster. As soon as you touch the outside world in a non-idempotent way,
e.g. by sending an email, these guarantees fall away. It is essentially
impossible to
> On May 10, 2019, at 8:26 AM, ASHOK MACHERLA wrote:
>
> Dear Team
>
> In our project, for SMS/Email purpose we are using Kafka cluster and
> Real-time Notification which is our custom application.
>
> We are sending to messages from Kafka to Real-time Notification, and then
> SMTP Gateway
Dear Team
In our project, for SMS/Email purpose we are using Kafka cluster and Real-time
Notification which is our custom application.
We are sending to messages from Kafka to Real-time Notification, and then SMTP
Gateway servers.
Our problem is ,sometimes customers are getting same email for
