They do flow along the route at all times. However, without static
ports the orted has to start by directly connecting to the HNP and
sending the orted's contact info to the HNP. Then the HNP includes
that info in the launch msg, allowing the orteds to wireup their routes.
So the difference is that the static ports allow us to avoid that
initial HNP-direct connection, which is what causes the flood.
The other thing that hasn't been done yet is to have the "procs-
launched" messages rollup in the collective - the HNP gets one/daemon
right now, even though it comes down the routed path. Hope to have
that done next week. That will be in operation regardless of static vs
On Jun 25, 2009, at 8:44 AM, Iain Bason wrote:
> On Jun 23, 2009, at 7:17 PM, Ralph Castain wrote:
>> Not any more, when using regex - the only message that comes back
>> is one/node telling the HNP that the procs have been launched.
>> These messages flow along the route, not direct to the HNP -
>> assuming you use the static port option.
> Is there any prospect of doing the same without requiring the static
> port option?
> devel mailing list