On 12/4/2012 1:55 AM, Andy D'Arcy Jewell wrote:
Is there an easy way to tell (say from a shell script) when "all
commits and merges [are] complete"?
One important bit of information I just thought of: A default Solr 4
config uses a new directory implementation called NRTCachingDirectory,
whic
On 03/12/12 18:04, Shawn Heisey wrote:
Serious production Solr installs require at least two copies of your
index. Failures *will* happen, and sometimes they'll be the kind of
failures that will take down an entire machine. You can plan for some
failures -- redundant power supply and RAID a
On 12/3/2012 9:47 AM, Andy D'Arcy Jewell wrote:
However, wouldn't re-creating the index on a large dataset take an
inordinate amount of time? The system I will be backing up is likely
to undergo rapid development and thus schema changes, so I need some
kind of insurance against corruption if we
On 03/12/12 16:39, Erick Erickson wrote:
There's no real need to do what you ask.
First thing is that you should always be prepared, in the worst-case
scenario, to regenerate your entire index.
That said, perhaps the easiest way to back up Solr is just to use
master/slave replication. Consider
There's no real need to do what you ask.
First thing is that you should always be prepared, in the worst-case
scenario, to regenerate your entire index.
That said, perhaps the easiest way to back up Solr is just to use
master/slave replication. Consider having a machine that's a slave to the
mast
