THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Every role also has a list of modes under which a node can be. For certain roles (e.g. overseer) it is useful for potentially finer grained control of how strictly or loosely that role applies for that node.
- Most roles would just have two modes (on, off)
- In special cases a role might have more modes, e.g. "overseer" role to have (allowed, disallowed, preferred) modes.
- For every role, one of the modes is assumed to be a defaultIfAbsent (see below in roles API section, supported GET call), i.e. a node that doesn't specify that role, the mode that is assumed for the functionality for that role. For example, if a node starts with "-Dsolr.node.roles=data:on", then it will be assumed that the node has overseer has mode "disallowed" (i.e. the defaultIfAbsent mode of the overseer role).
...