Trending on MSDN: Multiple Service Fabric Reliable Dictionary Notifications

Question

question

mimckitt asked Oct 29, '19 HananAliIbrahemRoffa-1166 Suspended answered May 6, '22

Trending on MSDN: Multiple Service Fabric Reliable Dictionary Notifications

I have stateful service fabric service where the replica count is 3. In this stateful service, I have a reliable dictionary. I want to track notifications for each CRUD operation which is performed on the reliable dictionary.

I have followed the link to integrate reliable dictionary notifications

If I use a one-node cluster and replica count is 1, I will be getting one notification for each operation (Create, Update, Delete). But If I use five-node cluster and replica count is 3, I will be getting three notifications for each operation, which is causing duplicate records in my business logic, I need only one notification for each operation.

My expectation is to get a notification for each replica when the dictionary has been updated.

Can anyone help me out to resolve this issue?

Sourced from MSDN

azure-service-fabric

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2019-10-29T23:11:44.87Z

olufemiaMSFT answered Oct 29, '19 mimckitt edited Oct 30, '19

Welcome to the Microsoft Q&A (Preview) platform. Happy to answer your questions.

Currently, notifications fire on all replicas when the changes show up.
This means in your code, you can either

Not hook up the notifications on secondary replicas or unhook the notifications when the replicas become secondaries (and rehook them when becoming primary)
Discard the notifications that fire on the secondaries Both would require adding an override to OnChangeRoleAsync

You can follow this document for more information.

Sourced from MSDN

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2022-05-05T22:01:15.817Z

AHMED-BAKIR Suspended answered May 5, '22 50609367 Suspended commented May 7, '22

Not hook up the notifications on secondary replicas or unhook the notifications when the replicas become secondaries (and rehook them when becoming primary)

Discard the notifications that fire on the secondaries Both would require adding an override to OnChangeRoleAsync

You can follow this document for more information.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 3 · 2022-05-06T03:16:52.58Z

HananAliIbrahemRoffa-1166 Suspended answered May 6, '22

Not hook up the notifications on secondary replicas or unhook the notifications when the replicas become secondaries (and rehook them when becoming primary) Discard the notifications that fire on the secondaries Both would require adding an override to OnChangeRoleAsync You can follow this document for more information.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question