> And in some future version it may read an additional property > solr.overseer.priority=3 to give some priority to it, or it could read some > solr.overseer.strict=true to refuse to place overseer strictly on nodes with > the role
This sysProp example was just an example, and maybe a bad example for this particular case since a local sysprop would not automatically be available to the election code. So the node-roles/<role> hierarchy in zk would be a better fit. However, my point was to let the feature behind a role handle this as for now, and gradually evolve the roles framework as needed. Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
