THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
There will just one supported way to use the roles functionality:
Startup
...
parameter (sysprop)
Parameter | Value | Required? | Default |
solr.node.roles |
...
Comma separated list of |
...
roles for this node, with each role in lowercase, and no repetitions in the list. | No | data
|
Examples:
- Preferred overseer node with no data (dedicated overseer):
-Dsolr.node.roles=overseer - Preferred overseer with data:
-Dsolr.node.roles=overseer,data - Coordinator node (preview for upcoming feature):
-Dsolr.node.roles=coordinator
...
- a) Yes: If configured roles are found in ZK, overwrite them with roles specified with sysprops. If no configured roles are present, just add the roles in ZK.
- b) If no sysprops are present, roles are No: Roles are configured to export the default set of roles (at the time of this SIP, that’s [“data”])
...
Ishan,Noble: Sysprops
Jan: SIP-11
- "Capable vs currently providing"
Gus: Exact quote: "... a way in which roles could be made to express both "I can perform this role if required" and "I am presently performing this role" in zookeeper. The basic idea was that some config in zookeeper that lists the nodes and information about each node has an attribute declaring that it capable of a given set of roles"
Ishan: No need to complicate this current design, we can take this up later, if needed.