Spread Shared Multi Party licenses over Conductor cluster?

[Hes]

Hi there!

I have a Conductor cluster and some Shared Multi Party licenses.
The Conductor admin guide states"If a node within a cluster is removed, the PMP and SMP option keys installed on it will be available on the remaining nodes for 30 days."

So I could installed 100% of the licenses on Conductor1.

But I can imagine that in specific situations such as rebooting nodes during troubleshooting this information might be lost.
Is this a correct assumption or is the license information really copied to the other node and maintained during reboots?

So would it then be a better practice to put 50% of the licenses on Condcutor1 and 50% on Conductor2?

[Patrick Sparkman]

You can either install all SMP licenses on one cluster peer or spread them out across any of the peers in any quantity you want. If a node within the cluster is removed or goes down for any reason, the SMP licenses installed on it will be available on the remaining peers for up to 30 days so that you can have time to bring that peer back online.  This is noted in the "Multiparty License Status" section of the Conductor Admin Guide on pg 122.

Personally, I ended up spreading my SMP licenses across the entire cluster, that way there is no single point of failure with all the licenses on the master peer.  Although a failure is low when speaking in terms of the VM, but it's a worse case scenario.