Better off to just do Replication to the slave using the replication handler.
However, if there is no network connectivity, e.g. this is an offsite cold/warm spare, then here is a solution: The NAS likely supports some Copy-on-write/snapshotting capabilities. If your systems people will work with you, you can use the replication/backup handler to take a NAS snapshot just after hard commit, and then have the snapshot replicated to another volume. I suspect Solr will have to be started on the cold/warm spare when you do a failover to offsite, because I know of no way to have the OS react to events when a snapshot is replicated by the NAS. This kind of solution is what you might see for an Oracle, or any other binary ACID database, so you can look at best practices for integrating these products with Netapp or EMC Celera for more ideas. -----Original Message----- From: Rick Leir [mailto:rl...@leirtech.com] Sent: Friday, May 19, 2017 12:40 PM To: solr-user@lucene.apache.org Subject: Re: Solr in NAS or Network Shared Drive For an experiment, mount the NAS filesystem ro (readonly). Is there any way to tell Solr not to bother with a lockfile? And what happens if an update or add gets requested by mistake, does it take down Solr? Why not do this all the simple way, and just replicate? On May 19, 2017 10:41:19 AM EDT, David Hastings <hastings.recurs...@gmail.com> wrote: >ive always wanted to experiment with this, but you have to be very >careful that only one of the cores, or neither, can do ANY writes, also >if you have a suggester index you need to make sure that each core >builds their own independently. In any case from every thing ive read >the general answer is dont do it. would like to hear other peoples >thoughts on this however. > >On Fri, May 19, 2017 at 10:33 AM, Ravi Kumar Taminidi < >ravi.tamin...@whitepine-st.com> wrote: > >> Hello, Scenario: Currently we have 2 Solr Servers running in 2 >different >> servers (linux), Is there any way can we make the Core to be located >in NAS >> or Network shared Drive so both the solrs using the same Index. >> >> Let me know if any performance issues, our size of Index is appx 1GB. >> >> Thanks >> >> Ravi >> >> -----Original Message----- >> From: biplobbiswas [mailto:revolutionisme+s...@gmail.com] >> Sent: Friday, May 19, 2017 9:23 AM >> To: solr-user@lucene.apache.org >> Subject: Re: Nested Document is flattened even with @Field(child = >true) >> annotation >> >> Hi >> Mikhail Khludnev-2 wrote >> > Hello, >> > >> > You need to use >> > >https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherPa >> > rsers-BlockJoinQueryParsers >> > and >> > >https://cwiki.apache.org/confluence/display/solr/Transforming+Result+D >> > >ocuments#TransformingResultDocuments-[child]-ChildDocTransformerFactor >> > y >> > to get the nested data back. >> > >> > >> > -- >> > Sincerely yours >> > Mikhail Khludnev >> >> I had already gone through those links you posted and they talk about >> retrieving after indexing. My problem is that my documents are not >indexed >> in a nested structure. >> >> Can you please look at the first comment as well where I posted a >sample >> code and sample response which i get back. >> >> Because its creating distinct documents for nested structure >> >> >> >> >> -- >> View this message in context: http://lucene.472066.n3. >> nabble.com/Nested-Document-is-flattened-even-with-Field- >> child-true-annotation-tp4335877p4335891.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> -- Sorry for being brief. Alternate email is rickleir at yahoo dot com
