There was a long standing loop bug which posed this as a workaround. This was fixed with 2.11 and as such, the docs and workaround being updated/removed.
Security rationale, same as accept_commands. By default, no-one should be trusted, even with the endpoint/zone relationship is established. A more concrete scenario would be e.g. when an agent shouldn’t receive synced check commands or alike. Users don’t use that much, but enabling these flags by default would cause trouble since this was the default behavior since 2.0 and everyone knows about it.
If the entire package was copied, this should be fine. Stage names are auto-generated UUIDs, previous older versions had to use a custom schema due to el5 not supporting UUIDs. Since 2.7 or so, these names are a random string being persistent on disk.
Yes, exactly. One side decides which feature config object remains running, the other one is paused.
There’s no harm with e.g. sending commands to the first master, all actions are replicated. Thus requiring accept_config at least then. accept_commands is solely for command_endpoint checks as target.
Cheers,
Michael