i trying set solr collection extends across multiple servers. if correct in understanding things, able set collection, consists of shards. shards consist of replicas, correspond cores. please correct holes in understanding of this.
ok.
so i've got solr set , able create collection on machine 1 doing this.
bin/solr create_collection -c test_collection -shards 2 -replicationfactor 2 -d server/solr/configsets/basic_configs/conf this appears right, able check health , see something. input
bin/solr healthcheck -c test_collection and see shard information.
now want do, , part stuck on, take collection have created, , extend across multiple servers. i'm not sure if understand how works correctly, think want put shard1 on machine1, , shard2 on machine2.
i can't figure out how based on documentation, although pretty sure solrcloud meant solve. can give me nudge in right direction this...? either way extend collection across multiple servers or reason not doing so.
when -shards 2, you're saying want collection split across 2 servers already. -replicationfactor 2 says want shards present on @ least 2 servers well.
a shard piece of collection - without shard, won't have access documents. replicationfactor indicates how many copies should made available of same shard (or "partition" times used represent piece of index) in collection, 2 shards 2 replicas end 4 "cores" distributed across available servers (these "cores" managed internally solr).
start set of new solrcloud instances in same cluster , should see documents spread across nodes expected.
Comments
Post a Comment