| Re: [smila-user] smila-user Digest, Vol 51, Issue 1 |
|
Hallo Marco. I tried to resolve the problems using a specific user for SMILA on both machines. This seems to work! I can see something indexed in solr after having crawled some resources. However it seems that I have many differences in results, working in stand alone or in cluster mode. Thank for your support! Il 02/01/2014 18.00,
smila-user-request@xxxxxxxxxxx ha scritto:
Send smila-user mailing list submissions to smila-user@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/smila-user or, via email, send a message with subject or body 'help' to smila-user-request@xxxxxxxxxxx You can reach the person managing the list at smila-user-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of smila-user digest..." Today's Topics: 1. Re: SMILA in a Cluster (Marco Strack) ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Jan 2014 16:26:45 +0100 From: Marco Strack <marco.strack@xxxxxxxxxxx> To: Smila project user mailing list <smila-user@xxxxxxxxxxx> Subject: Re: [smila-user] SMILA in a Cluster Message-ID: <91CA34BBD67F4B41BE7264BD3E5703C103CBFED7B17E@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Hello Lorenzo, at first look, with the information you provided, your way of clustering with smila looks fine. Regarding the problems you're experiencing, I'd recommend you first check if the objectstore access is working as expected. Start the system and then put some objects into any store. Try this on both nodes (LinuxA + LinuxB or LinuxA + Win): PUT http://<hostname>:8080/smila/store/store2/object1/ { "id": "object1", "content": "my content." } If the calls succeed, try to list the store contents. Also do this via calls to both nodes. If this succeeds, you should be able to import. If not successful, please provide the relevant parts from smila.log for further analysis. -- Since LinuxA is creating objects and nothing is indexed in solr, you may also check your solr.serverUrl=http://<SOLR-HOST>:8983/solr setting. Regards Marco Von: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-bounces@xxxxxxxxxxx] Im Auftrag von Lorenzo Eccher Gesendet: Montag, 23. Dezember 2013 18:40 An: smila-user@xxxxxxxxxxx; Andreas Weber Cc: Vincenzo Croce Betreff: [smila-user] SMILA in a Cluster Hallo. I tried the clustering of SMILA as described in the wiki http://wiki.eclipse.org/SMILA/Documentation/HowTo/How_to_setup_SMILA_in_a_cluster I configure the cluster as described in the wiki page and in order to test I use the same process as described in 5 minutes to Success. Because I am behind a proxy I decided to crawl the java API html pages (downloaded from oracle and exported in local apache). I test it on 2 linux (LinuxA, LinuxB) and 1 windows (Win). My "master" is one linux (linux A) that hosts the solr 3.6 installation and share the objectstore using samba 3. That is what I got: 1. Testing Cluster LinuxA+LinuxB I see that the LinuxB has problem writing and reading the shared folder (even if the user running SMILA has no problems there). I created the user "smila" both on LinuxA and LinuxB with same UID and same GID to avoid problem with authorization and SAMBA is also configured to export the folder for "smila" user. 2. Testing Cluster as LinusA+Win The cluster seems working. The LinuxA create lots of objects in objectstore and the smila in Win sees them. However I did not understood what the windows SMILA has been doing :). Nothing is indexed, after 15 minutes. Some errors about socket exceptions and time out exception appeared. Is that the right way to test the clustering or did you suggest something more specific? Is there any more specific description on how smila manage the process in a cluster? Thank you -- ________________________________ Lorenzo Eccher lorenzo.eccher@xxxxxx<mailto:lorenzo.eccher@xxxxxx> (+39) 0461 312 306 Engineering Ingegneria informatica s.p.a www.eng.it<http://www.eng.it> ENGINEERING Society and Territory Trento Research Office EIT-ITC Labs<http://eit.ictlabs.eu>, Trento node ESTRO Lab at FBK building via Sommarive, 18 Povo - 38123 Trento Le informazioni trasmesse sono destinate esclusivamente alla persona o alla societ? in indirizzo e sono da intendersi confidenziali e riservate. Ogni trasmissione, inoltro, diffusione o altro uso di queste informazioni a persone o societ? differenti dal destinatario ? proibita. Se ricevete questa comunicazione per errore, contattate il mittente e cancellate le informazioni da ogni computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Die Informationen in dieser E-Mail-Mitteilung sind vertraulich und deren Verbreitung in jeglicher Art oder Form ist untersagt. Sollten Sie diese Nachricht irrt?mlich erhalten haben, ersuchen wir Sie, sofort den Absender dar?ber zu informieren und die Mail zu l?schen. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/smila-user/attachments/20140102/1ce1833f/attachment.html> ------------------------------ _______________________________________________ smila-user mailing list smila-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-user End of smila-user Digest, Vol 51, Issue 1 ***************************************** --
Lorenzo Eccher
Le informazioni trasmesse sono destinate esclusivamente alla
persona o alla società in indirizzo e sono da intendersi
confidenziali e riservate. Ogni trasmissione, inoltro,
diffusione o altro uso di queste informazioni a persone o
società differenti dal destinatario è proibita. Se ricevete
questa comunicazione per errore, contattate il mittente e
cancellate le informazioni da ogni computer. |