SAN vendors make high-priced super-fast shared file system hardware.
They don't use NFS, usually they have a kernel drop-in file system.
On 4/14/11, Parker Johnson wrote:
>
> Otis and Erick,
>
> Thanks for the responses and for thinking over my potential scenarios.
>
> The big draw for me on 2 r
Otis and Erick,
Thanks for the responses and for thinking over my potential scenarios.
The big draw for me on 2 repeaters idea is that I can:
1. Maximize my hardware. I don't need a standby master. Instead, I can
use the "second" repeater to field customer requests.
2. After the primary repea
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: Parker Johnson
> To: "solr-user@lucene.apache.org"
> Sent: Tue, April 12, 2011 6:33:08 PM
> Subject: Vetting Our Architect
I think the repeaters are misleading you a bit here. The purpose of a
repeater is
usually to replicate across a slow network, say in a remote data
center, then slaves at that center can get more timely updates. I don't
think
they add anything to your disaster recovery scenario.
So I'll ignore repe
I am hoping to get some feedback on the architecture I've been planning
for a medium to high volume site. This is my first time working
with Solr, so I want to be sure what I'm planning isn't totally weird,
unsupported, etc.
We've got a a pair of F5 loadbalancers and 4 hosts. 2 of those hosts
