gus-asf edited a comment on pull request #1694:
URL: https://github.com/apache/lucene-solr/pull/1694#issuecomment-664018065
These interfaces look like a good way to begin. Thoughts: This is an
excellent point at which to consider and then stick to a preferred set of
terminology. My favorites are:
- **Machines** are the operating system level container or hardware and have
- **Nodes** which are running solr processes on machines which have
portions of
- **Collections** which are logical indexes associated with a particular
schema and have
- **Shards** which split a collection on a routing value to allow
scaling and have
- **Replicas** which are duplicate copies implementing a shard often
hosted on separate nodes.
We should strive to apply only ONE word for each level throughout the
interfaces to make them as simple and easy to understand as possible.
These 5 terms all have nice clear english words that communicate their
function to some extent. Core however only really means "central thing" and I
have always thought it was a very confusing word to use here since it has
almost no memnonic value. Slice is also good for the shard level, but I think
shard is no worse and more commonly used in documentation. Although core has
been used many times in the past, I don't think anyone is going to have trouble
finding what they want via the terms I'm suggesting.
The Cluster level concept usually ignores Machines and speaks only of
nodes... I could be convinced either way on whether or not that's a good thing.
For fun I drew a near worst case diagaram (omitting back references) :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
