Has anyone tried access Zebra through a network socket instead of the unix one? I was under the impression that that was possible. I've considered a similar setup to what Michael Kuhn is trying build. I already have a database cluster using active-active replication and IP address fail-over with heartbeat. So that's working for me just fine. I've also played with GlusterFS as a shared upload space to serve other applications, so that's also a possibility. It really is Zebra that is the biggest question for me. My hope is that accessing Zebra over the network is possible, then I just dedicate a worker to running and maintaining Zebra, and point the other workers at it. That way worst case is searching doesn't work for the hour or so it would take to spin up Zebra somewhere else if it's server goes down. On Mon, Nov 7, 2016 at 1:19 PM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
If you allow people to upload files sure.
We usually don't that is what a CMS is for. (Uploaded images are stored in the db)
And yes talking to a DB is a solved problem, thousands of applications around the world do that already. The only thing that is unique to Koha is Zebra
Chris
Chris,
What about the uploaded files? You will need to replicate them to the other server.
What about the cross connection of the DB, you will use mysql proxy in
On 8 November 2016 at 09:17, Rodrigo Santellan <rsantellan@gmail.com> wrote: the
middle?
I'm really curious about those answers.
Regards.
On Mon, Nov 7, 2016 at 5:05 PM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 8 November 2016 at 08:50, Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi,
We are looking for a solution to build a redundant infrastructure for Koha.
What we want to do is shown in the diagram http://adminkuhn.ch/download/Redundant.png
The main objective of such a solution is: If one of the Application Servers goes down the other will take over the job without losing any time. If the DB-Server Master goes down we will be able to build the Master out of the Slave and create a new Slave next to the new Master.
Has anyone ever built such an infrastructure with Koha and can give us some advice how to proceed? Is this possible with Koha anyway?
Will shift this to Koha-devel
Yes this is possible and quite easy to do. What makes it tricky is Zebra, which you have left out of your diagram. You either need to have the full zebra index on both your application servers (which means modifying rebuild_zebraqueue to make sure it gets built by each machine) Or you need to use something like nfs or another distributed filesystem. Or use rsync etc.
It becomes a lot easier with elasticsearch of course, because you just have your elastic cluster and they talk to that.
Hope this helps
Chris
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg.
Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Michael Hafen Washington County School District Technology Department Systems Analyst