The problem with that approach is that it assumes that every deployment has a specific number of containers that are required. What about the case where we want the module deployed on every container but no action is required if we lose a container? I think the approach we had decided was to include a set of properties as data of the module name. In your example there would be a single node like this:

`/xd/streams/mystream/source/http`

The `http` node data would contain a property of `count=4` indicating that we need exactly 4 instances. The leader can use this to determine if the right number of ephemeral nodes exist under `http`.