various questions (mainly around zebra config & stuff)
~#perl -e 'print "Hello world\n"; Investigating liblime recent or less recent commits I have some questions : ==== 1 ==== - the koha-conf.xml now contains <listen id="biblioserver" >unix:__ZEBRA_RUN_DIR__/bibliosocket</listen> so, no more tcp@blabla:port iirc, unix sockets are much more faster than tcp. but : - does that means we "loose" the z3950 public server in the process ? - Is it replaced by the SRU/SRW that is just after ? (ie : can we query the SRU/SRW server with PQF queries ?) ==== 2 ==== How to check that the SRU/SRW works fine ? I tried a yaz-client @:9998/Biblios and get : Connecting...error = System (lower-layer) error: Connection refused ==== 3 ==== The opensearch & unapi things uses SRU/SRW, but the port is hardcoded to 9998, were it can be changed in the install process. can we consider that as a bug ? ==== 4 ==== misc/zebraqueue_start.pl & misc/update_items.pl afaik : - zebraqueue_start was written to update the zebra DB when a biblio is updated/added/deleted - update_items was written to update on a daily basis all items that have been updated (to update issuing status of the item) now that zebra is quick, a line is added into zebraqueue and the "position status" of each item is updated everytime zebraqueue_start is run. so do we still need misc/update_items.pl ? ==== 5 ==== It seems that issuing a book results in 2 lines in zebraque. Isn't this a bug ? ==== 6 ==== Now that zebra indexes quickly, do we still need zebraqueue_start ? couldn't we update in real time ? (that wouldn't solve the multiple access problem joshua faced 2 years ago, when updating the DB from 2 processes resulted in a DB crash. But myabe this issue is solved as well now.) ==== 7 ==== couldn't we transform zebraqueue_start to a daemon, and not let is as cronjob ? having to wait for 1mn in the worst case seems very long to most librarians (when they add an authority and have to wait for 1mn to be able to find it in the biblio) would that daemon-ization be a problem for MS-windows servers ? -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19
Hi, Regarding questions 5,6,7: Q5. issuing a book should not produce 2 lines in zebraqueue so yes we shuld consider it as a minor bug. Q6. updating in realtime is now possible but I am not quite sure whether DB crash still occurs so we use zebraqueue with 5 second waits. i even tried with 0 seconds and works fine. Q7. We have it running as a Windows service(daemon).No problem. We have also recently ported everything to a linux server and it runs as a daemon there as well with no problem Tumer ________________________________ Kimden: koha-devel-bounces+tgarip=neu.edu.tr@nongnu.org bu kişinin yerine: Paul POULAIN Gönderilmiş: Cum 04.01.2008 12:48 Kime: Koha-devel@nongnu.org Konu: [Koha-devel] various questions (mainly around zebra config & stuff) ~#perl -e 'print "Hello world\n"; Investigating liblime recent or less recent commits I have some questions : ==== 1 ==== - the koha-conf.xml now contains <listen id="biblioserver" >unix:__ZEBRA_RUN_DIR__/bibliosocket</listen> so, no more tcp@blabla:port iirc, unix sockets are much more faster than tcp. but : - does that means we "loose" the z3950 public server in the process ? - Is it replaced by the SRU/SRW that is just after ? (ie : can we query the SRU/SRW server with PQF queries ?) ==== 2 ==== How to check that the SRU/SRW works fine ? I tried a yaz-client @:9998/Biblios and get : Connecting...error = System (lower-layer) error: Connection refused ==== 3 ==== The opensearch & unapi things uses SRU/SRW, but the port is hardcoded to 9998, were it can be changed in the install process. can we consider that as a bug ? ==== 4 ==== misc/zebraqueue_start.pl & misc/update_items.pl afaik : - zebraqueue_start was written to update the zebra DB when a biblio is updated/added/deleted - update_items was written to update on a daily basis all items that have been updated (to update issuing status of the item) now that zebra is quick, a line is added into zebraqueue and the "position status" of each item is updated everytime zebraqueue_start is run. so do we still need misc/update_items.pl ? ==== 5 ==== It seems that issuing a book results in 2 lines in zebraque. Isn't this a bug ? ==== 6 ==== Now that zebra indexes quickly, do we still need zebraqueue_start ? couldn't we update in real time ? (that wouldn't solve the multiple access problem joshua faced 2 years ago, when updating the DB from 2 processes resulted in a DB crash. But myabe this issue is solved as well now.) ==== 7 ==== couldn't we transform zebraqueue_start to a daemon, and not let is as cronjob ? having to wait for 1mn in the worst case seems very long to most librarians (when they add an authority and have to wait for 1mn to be able to find it in the biblio) would that daemon-ization be a problem for MS-windows servers ? -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19 _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
Hi Tümer, Just a couple of quick questions for you: On 1/4/08, Tümer garip <tgarip@neu.edu.tr> wrote:
Hi, Regarding questions 5,6,7:
Q5. issuing a book should not produce 2 lines in zebraqueue so yes we shuld consider it as a minor bug. Q6. updating in realtime is now possible but I am not quite sure whether DB crash still occurs so we use zebraqueue with 5 second waits. i even tried with 0 seconds and works fine.
Q7. We have it running as a Windows service(daemon).No problem. We have also recently ported everything to a linux server and it runs as a daemon there as well with no problem Can you also contribute your windows service daemon? Ideally we could get
Do you have a script that simulates updates? If so, would you be willing to contribute it? this into the beta release on Feb 1st. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
~#perl -e 'print "Hello world\n";
Investigating liblime recent or less recent commits I have some questions : ==== 1 ==== - the koha-conf.xml now contains <listen id="biblioserver" >unix:__ZEBRA_RUN_DIR__/bibliosocket</listen> so, no more tcp@blabla:port
iirc, unix sockets are much more faster than tcp. but : - does that means we "loose" the z3950 public server in the process ? - Is it replaced by the SRU/SRW that is just after ? (ie : can we query the SRU/SRW server with PQF queries ?) The default is to run on sockets, and not on a public TCP port. All
Hi Paul, Here are some answers, I'm sure you'll like :-) On 1/4/08, Paul POULAIN <paul.poulain@free.fr> wrote: that's necessary to adjust this is a modification of two lines in your koha-conf.xml. Perhaps instead we should make a new install option for whether to run on a port or on a socket, you cannot run on both with Zebra as of 2.0.22, although Index Data as said this could be an enhancement if someone wanted to sponsor it, and LibLime may be in a position to do that later this year.
==== 2 ==== How to check that the SRU/SRW works fine ? I tried a yaz-client @:9998/Biblios and get : Connecting...error = System (lower-layer) error: Connection refused SRU/W is accessible via HTTP, and I've added some brief instructions here, we definitely need more detailed documentation on all of the options (this is a big topic!):
==== 3 ==== The opensearch & unapi things uses SRU/SRW, but the port is hardcoded to 9998, were it can be changed in the install process. can we consider that as a bug ? The port is no longer hardcoded, it's now an option you select via the installer. Note that you still have to edit the koha-conf.xml in the alpha release (which I'm about to package up as I write this), but I hope to have it a config
==== 4 ==== misc/zebraqueue_start.pl & misc/update_items.pl afaik : - zebraqueue_start was written to update the zebra DB when a biblio is updated/added/deleted - update_items was written to update on a daily basis all items that have been updated (to update issuing status of the item)
now that zebra is quick, a line is added into zebraqueue and the "position status" of each item is updated everytime zebraqueue_start is run. so do we still need misc/update_items.pl ? We don't, and I've removed it. Also note, we have a zebraqueue_daemon.pl, and a zebraqueue cronjob, it's up to the library which they want to use. The documentation in the INSTALL.debian gives instructions for how to set up
http://wiki.koha.org/doku.php?id=en:development:z3950sru option by the Beta. the daemon, add to startup profile, etc.
==== 5 ==== It seems that issuing a book results in 2 lines in zebraque. Isn't this a bug ? Yes, this is a minor bug, I've filed it on bugzilla as bug 1745.
==== 6 ==== Now that zebra indexes quickly, do we still need zebraqueue_start ? couldn't we update in real time ? (that wouldn't solve the multiple access problem joshua faced 2 years ago, when updating the DB from 2 processes resulted in a DB crash. But myabe this issue is solved as well now.) First, we have both zebraqueue_start and bin/zebraqueue_daemon.pl.
Zebra's updating has improved drastically, and we should consider the possibility of direct updates. But testing is in order here, we need to create a test suite for simulating a team of a few hundred catalogers, circ staff, etc. to put zebra through a workout :-)
==== 7 ==== couldn't we transform zebraqueue_start to a daemon, and not let is as cronjob ? having to wait for 1mn in the worst case seems very long to most librarians (when they add an authority and have to wait for 1mn to be able to find it in the biblio) would that daemon-ization be a problem for MS-windows servers ? Yes, in fact, we already have a daemon. Please see the INSTALL.debian file, and the daemon itself, bin/zebraqueue_daemon.pl.
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
participants (3)
-
Joshua Ferraro -
Paul POULAIN -
Tümer garip