Hi Michael,

if losing statistical data isn't critical i think the first solution would
be enough. The second solution would work, as a tweak to achieve solr
server redundancy, however with very bad performance. It's possible to
implement a better redundant solution using the SolrReplication feature
with a couple of code & configuration changes, but i think that it wouldn't
worth the effort.

It would be better to focus the effort upgrading DSpace in order to use the
most recent Solr Cloud feature (Solr 4.1 -
http://wiki.apache.org/solr/SolrCloud). About the upgrade, from what i
know, Solr 3.5 indexes are readable from 4.1, however DSpace uses SolrJ
Client v3.6 which is incompatible with the newly Solr Cloud features,
basically it will only require code changes (and minor schema changes) -
indexes will not require upgrade.



On 25 January 2013 01:37, helix84 <heli...@centrum.sk> wrote:

> Hi Michael,
>
> I'm glad you managed to get it working and that you reported back on your
> progress. Also, when you feel you have added something extra that others
> could use, you're welcome send the patch to our Jira. Howtos are also very
> welcome for our wiki! I don't think we have anything on redundancy yet. And
> the Solr page I wrote could use improvements in many places!
>
> Regarding the best solution for Solr availability, I would recommend you
> to run a separate Solr server if you can. There's nothing specific about
> the embedded Solr in DSpace - just copy over the statistics core (both conf
> and data), point DSpace(s) to it and you're good to go. The DSpace specific
> things are described by schema.xml, which lives in the core's conf
> directory. Just mind Solr versions, DSpace 3.0 contains Solr 3.5.0.
>
> Even if you don't have a machine to spare, you could always run 2 tomcat
> instances on one server to keep Solr safe in case DSpace crashes or locks
> up its Tomcat instance (usually because of memory exhaustion). If you want
> to go even further, Solr is designed so that it can be made redundant (see
> eg. [1] or [2]).
>
> [1] http://wiki.apache.org/solr/CollectionDistribution
> [2] http://wiki.apache.org/solr/SolrReplication
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>



-- 
Thanks, João Melo (My Portfolio <http://www.lyncode.com/m/jmelo/>)
DSpace Department
*Lyncode*: Official
website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
[image: Follow us on
Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
<http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to