: #1 is a trade off against being possibly more available to writes in the case
: of a single down node. In the cloud case, you're still open for business. In
: the classical replication case, you're no longer available for writes if the
: downed node is the master.
or to put it another way: clas
The downsides that come to mind:
1. Every write gets amplified by the number of nodes in the cloud. 1000
write requests end up creating 1000*N HTTP calls as the leader forwards
those writes individually to all of the followers in the cloud. Contrast
that with classical replication where only c
Hi all,
We have a smallish index that performs well for searches and are
considering using solrcloud --but just for high availability/redundancy,
i.e. without any sharding.
The indexes would be replicated, but not distributed.
I know that "there are no stupid questions..Only stupid people"...but
