On 3/23/2016 9:43 AM, Robert Brown wrote: > When going to the admin UI on this new server I can see the > shards/replica's of the existing collection, and can even query it, > even tho this new server has no cores on it itself. > > Is this all expected behaviour? >
Yes. There were some bugs early on in the 4.x versions where this *didn't* work, but those were fixed. This functionality was fully intentional. > Is there any performance gain with what I have at this precise stage? > The extra server certainly makes it appear i could balance more > load/requests, but I guess the queries are just being forwarded on to > the servers with the actual data? As Erick said, the requests are being handled by the servers that actually host the data. The new node is just acting as a data ferry. There is no performance gain unless you use the ADDREPLICA feature of the collections API to add replicas of your existing shards to the new node, so some of the query load is transferred. > Am I correct in thinking I can now create a new collection on this > host, and begin to build up a new cluster? and they won't interfere > with each other at all? > > Also, that I'll be able to see both collections when using the admin > UI Cloud page on any of the servers in either collection? You're still mixing up "collection" and "cluster" in your terminology. This is somewhat understandable ... the concepts do have some similarity. Within a single cluster (servers sharing a particular database/chroot in zookeeper), all collections (logical indexes) in the entire cluster will be usable on any machine in the cluster. Thanks, Shawn
