On 1/29/2014 12:48 PM, Jeff Wartes wrote:
And that, I think, is my misunderstanding. I had assumed that the link
between a node and the collections it belongs to would be the (possibly
chroot¹ed) zookeeper reference *itself*, not the node¹s directory
structure. Instead, it appears that ZK is
Work is underway towards a new mode where zookeeper is the ultimate
source of truth, and each node will behave accordingly to implement and
maintain that truth. I can't seem to locate a Jira issue for it,
unfortunately. It's possible that one doesn't exist yet, or that it has
an obscure title.
Found it. In case anyone else cares, this appears to be the root issue:
https://issues.apache.org/jira/browse/SOLR-5128
Thanks again.
On 1/30/14, 9:01 AM, Jeff Wartes jwar...@whitepages.com wrote:
Work is underway towards a new mode where zookeeper is the ultimate
source of truth, and each
...the differnce between that example and what you are doing here is that
in that example, because both of nodes already had collection1 instance
dirs, they expected to be part of collection1 when they joined the
cluster.
And that, I think, is my misunderstanding. I had assumed that the link
It was my hope that storing solr.xml would mean I could spin up a Solr node
pointing it to a properly configured zookeeper ensamble, and that no further
local configuration or knowledge would be necessary.
However, I’m beginning to wonder if that’s sufficient. It’s looking like I may
also
Maybe i'm mising something, but everything you are describing sounds
correct and working properly -- the disconnect between what i think is
suppose to happen and what you seem to be expecting seems to be right
arround here
: essentially used empty directories for the solr home. Although
