swarm: say "no queue coordinates", never "a hive with no queue"
The swarm always has exactly one queue; a hive can only lack its address. Reworded every prose site this PR added that stated or implied the opposite, to name what is actually absent (coordinates, credential, or address) instead of the queue itself. Refs #3805
This commit is contained in:
parent
86652f051a
commit
2989c5ccdb
8 changed files with 31 additions and 26 deletions
|
|
@ -38,10 +38,10 @@ in
|
|||
which is the bridge address rather than a loopback one — inside this
|
||||
container `127.0.0.1` is the agent itself.
|
||||
|
||||
`null` means this hive has no queue, and the harness then declares no
|
||||
credential and logs that it has none. It is deliberately not defaulted
|
||||
to anything: a guessed address builds fine and talks to the wrong
|
||||
machine.
|
||||
`null` means this hive has not been given the queue's address for its
|
||||
agents, and the harness then declares no credential and logs that it
|
||||
has none. It is deliberately not defaulted to anything: a guessed
|
||||
address builds fine and talks to the wrong machine.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ in
|
|||
|
||||
Set together with {option}`hyperhive.queue.natsUrl` or not at all —
|
||||
the harness treats a half-set pair as a deployment bug rather than as
|
||||
"no queue".
|
||||
"no queue coordinates".
|
||||
'';
|
||||
};
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue