I see that by default in SolrCloud that my collections are
replicating. Should this be disabled in SolrCloud as this is already
handled by it?
From the documentation:
The Replication screen shows you the current replication state for
the named core you have specified. In Solr, replication is for
On 3/25/2014 10:42 AM, Software Dev wrote:
I see that by default in SolrCloud that my collections are
replicating. Should this be disabled in SolrCloud as this is already
handled by it?
From the documentation:
The Replication screen shows you the current replication state for
the named core
No, don't disable replication!
The way shards ordinarily keep up with updates is by sending every document
to each member of the shard. However, if a shard goes offline for a period
of time and comes back, replication is used to catch up that shard. So
you really need it on.
If you created your
Thanks for the reply. Ill make sure NOT to disable it.
One other question. If I optimize a collection on one node, does this
get replicated to all others when finished?
On Tue, Mar 25, 2014 at 10:13 AM, Software Dev
static.void@gmail.com wrote:
Thanks for the reply. Ill make sure NOT to disable it.
Ehh.. found out the hard way. I optimized the collection on 1 machine
and when it was completed it replicated to the others and took my
cluster down. Shitty
On Tue, Mar 25, 2014 at 10:46 AM, Software Dev
static.void@gmail.com wrote:
One other question. If I optimize a collection on one node,
On 3/25/2014 11:59 AM, Software Dev wrote:
Ehh.. found out the hard way. I optimized the collection on 1 machine
and when it was completed it replicated to the others and took my
cluster down. Shitty
It doesn't get replicated -- each core in the collection will be
optimized. In older
So its generally a bad idea to optimize I gather?
- In older versions it might have done them all at once, but I believe
that newer versions only do one core at a time.
On Tue, Mar 25, 2014 at 11:16 AM, Shawn Heisey s...@elyograg.org wrote:
On 3/25/2014 11:59 AM, Software Dev wrote:
Ehh..
In older versions it might have done them all at once, but I believe
that newer versions only do one core at a time.
It looks like it did it all at once and I'm on the latest (4.7)
On Tue, Mar 25, 2014 at 11:27 AM, Software Dev
static.void@gmail.com wrote:
So its generally a bad idea to
Yes, it is generally a bad idea to optimize.
The system continually does merges as needed. You generally do not need to
force a full merge.
wunder
On Mar 25, 2014, at 11:27 AM, Software Dev static.void@gmail.com wrote:
So its generally a bad idea to optimize I gather?
- In older
10 matches
Mail list logo
