Hi Hoss,
Yes I know that, but I want to have a proper dummy backup (something that
could be kept in a very controlled environment). I thought about using this
approach (a slave just for this purpose), but if I'm using it just as a
backup node there is no reason I don't use a proper backup structur
: I'm setting up a backup task to keep a copy of my master index, just to
: avoid having to re-build my index from scratch. And other important issue is
every slave is a backup of the master, so you don't usually need a
seperate backup mechanism.
re-building hte index is more about peace of mind
OK, I'll define it as a procedure in my disaster recovery plan.
That would be great. I'm looking forward to it.
Thanks,
Daniel
On 8/10/07 18:07, "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> On 10/8/07, Daniel Alheiros <[EMAIL PROTECTED]> wrote:
>> Hmm, is there any exception thrown in case the i
On 10/8/07, Daniel Alheiros <[EMAIL PROTECTED]> wrote:
> Hmm, is there any exception thrown in case the index get corrupted (if it's
> not caused by OOM and the JVM crashes)? The document uniqueness SOLR offers
> is one of the many reasons I'm using it and should be excellent to know when
> it's go
Hi Yonik.
It looks pretty good.
I hope I'm not the one who will post a very odd crash after a while. :)
OK, so is very unlikely that a OOM it's going to happen, as I've set my JVM
heap size to 1.5G.
Hmm, is there any exception thrown in case the index get corrupted (if it's
not caused by OOM and
On 10/8/07, Daniel Alheiros <[EMAIL PROTECTED]> wrote:
> Well I believe I can live with some staleness at certain moments, but it's
> not good as users are supposed to need it 24x7. So the common practice is to
> make one of the slaves as the new master and switch things over to it and
> after the
Hi YoniK.
I'll check if I comment about it at this level and if it's OK I'll bring
other details. Sorry if I can't do it right now, but I don't want to brake
my company's policies.
Well I believe I can live with some staleness at certain moments, but it's
not good as users are supposed to need it
We run multiple, identical, independent copies. No master/slave
dependencies. Yes, we run indexing N times for N servers, but
that's what CPU is for and I sleep better at night. It makes
testing and deployment trivial, too.
wunder
==
Walter Underwood
Search Guy, Netflix
On 10/8/07 4:05 AM, "Dani
On 10/8/07, Daniel Alheiros <[EMAIL PROTECTED]> wrote:
> I'm about to deploy SOLR in a production environment
Cool, can you share exactly what it will be used for?
> and so far I'm a bit
> concerned about availability.
>
> I have a system that is responsible for fetching data from a database and
Hi
I'm about to deploy SOLR in a production environment and so far I'm a bit
concerned about availability.
I have a system that is responsible for fetching data from a database and
then pushing it to SOLR using its XML/HTTP interface.
So I'm going to deploy N instances of my application so it's
10 matches
Mail list logo
