In a Distributor Scenario, What Happens to the Message if a Worker Goes Down? about docs.particular.net HOT 8 CLOSED

I was about to open an issue on this, but appearantly you guys were already working on it. Any update on this issue? The doco could use some more clarity on this topic.

Specifically I think it would be useful to have a clear understanding of where the data (messages) for the worker is once it has been dispatched to the worker by the distributor. What if the worker goes down, where is that data? Can the distributor re-assign that message to another worker? Is the message lost? Etc.

from docs.particular.net.

@pablocastilla -

1. please review http://docs.particular.net/nservicebus/in-a-distributor-scenario-what-happens-to-the-message-if-a-worker-goes-down
2. Propose updates / enhancements

from docs.particular.net.

I see the article correct, at least I understand what it is saying. I suppose that with a few diagrams about how the distributor works and how a SAN works it would be clearer.

If you want I can write a new version of it.

from docs.particular.net.

Yes. Invest a few hours making improvements and submit a PR for review by
the team. Thanks!

from docs.particular.net.

+1 for the diagrams. Also the effect that a message could get lost if the worker node is not virtualized as described, is somewhat left implicit to the reader.

The document is now described as a FAQ. Will it also be linked to or duplicated in the Master/Distributor documentation?

from docs.particular.net.

The document is now described as a FAQ. Will it also be linked to or duplicated in the Master/Distributor documentation?

@pablocastilla - what do you say ?

from docs.particular.net.

Although it is a question I think it is better just in the Scaling Out section, out of FAQ. That way it is easier to find because scaling out only has 5 topics and FAQ has a lot.

from docs.particular.net.

the initial issue here seems to be done. feel free to raise new, more specific, issues if you feel something is outstanding

from docs.particular.net.