eZFind: How do I specify an individual Solr core for each site?

Next topic

Author	Message
Bayron Guevara	Tuesday 28 December 2010 7:40:34 pm I'm using an unique eZP installation to host two websites each one composed by three site access that share the same database. And I'd like to know how I can setup eZFind in order to use a different Solr core for each site. I already have running two cores and I've tried unsuccessfully tweaking the parameter solr.ini[SolrBase]SearchServerURI inside the respective siteaccess overrides, but appears that eZFind only accepts configuration files located under the override directory and those inside the extension. So this is limiting me to use only one core for all sites. Any suggestions? Maybe it can be accomplished through the use of Solr Shards? Web Developer & Modern Philosopher Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn
Bertrand Dunogier	Wednesday 29 December 2010 1:18:27 am I'm a bit surprised by this. The solr URI should be configurable at any level. I'll give this setup a try, and I'll let you know. On the other hand, remember that you can by default index completely different sites in the same solr index, as the (site specific) site ID will by default be used to filter out search results. On a more generic note, we usually recommend not to use the same ezp setup for multiple sites unless they're actually related (common design items, for instance). If the websites are related, being able to run cross-site searches is actually a good option. If no relation exists, it is much easier to maintain the sites separately. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Bayron Guevara	Wednesday 29 December 2010 7:23:35 am Thanks for your suggestions Bertrand. Yes, in my case the websites are related and for this reason I chose the same ezp setup. Now that I know than eZFind adds the SiteID in the search query, I prefer use the same Solr core. But, still remains the issue related to the per siteaccess configuration of the solr.ini file. Please, update this ticket when you confirm this is true and I'll post a new issue in the eZ Publish tracker system. Web Developer & Modern Philosopher Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn

Author

Message

Tuesday 28 December 2010 7:40:34 pm

I'm using an unique eZP installation to host two websites each one composed by three site access that share the same database. And I'd like to know how I can setup eZFind in order to use a different Solr core for each site. I already have running two cores and I've tried unsuccessfully tweaking the parameter solr.ini[SolrBase]SearchServerURI inside the respective siteaccess overrides, but appears that eZFind only accepts configuration files located under the override directory and those inside the extension. So this is limiting me to use only one core for all sites.

Any suggestions? Maybe it can be accomplished through the use of Solr Shards?

Web Developer & Modern Philosopher
Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn

Bertrand Dunogier

Wednesday 29 December 2010 1:18:27 am

I'm a bit surprised by this. The solr URI should be configurable at any level.

I'll give this setup a try, and I'll let you know.

On the other hand, remember that you can by default index completely different sites in the same solr index, as the (site specific) site ID will by default be used to filter out search results.

On a more generic note, we usually recommend not to use the same ezp setup for multiple sites unless they're actually related (common design items, for instance). If the websites are related, being able to run cross-site searches is actually a good option. If no relation exists, it is much easier to maintain the sites separately.

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Bayron Guevara

Wednesday 29 December 2010 7:23:35 am

Thanks for your suggestions Bertrand. Yes, in my case the websites are related and for this reason I chose the same ezp setup. Now that I know than eZFind adds the SiteID in the search query, I prefer use the same Solr core.
But, still remains the issue related to the per siteaccess configuration of the solr.ini file. Please, update this ticket when you confirm this is true and I'll post a new issue in the eZ Publish tracker system.

Web Developer & Modern Philosopher
Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn

eZ debug

Timing:	Jan 18 2025 02:16:32
Script start
Timing:	Jan 18 2025 02:16:32
Module start 'layout'
Timing:	Jan 18 2025 02:16:32
Module start 'content'
Timing:	Jan 18 2025 02:16:33
Module end 'content'
Timing:	Jan 18 2025 02:16:33
Script end

Main resources:

Total runtime	1.1594 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0060	588.1719	152.6563
Module start 'layout'	0.0060	0.0033	740.8281	39.5156
Module start 'content'	0.0093	1.1487	780.3438	552.0703
Module end 'content'	1.1580	0.0013	1,332.4141	12.0938
Script end	1.1593		1,344.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.2820	16	0.0002
Check MTime	0.0014	0.1168	16	0.0001
Mysql Total
Database connection	0.0006	0.0518	1	0.0006
Mysqli_queries	1.1082	95.5905	57	0.0194
Looping result	0.0008	0.0681	55	0.0000
Template Total	1.1248	97.0	2	0.5624
Template load	0.0021	0.1783	2	0.0010
Template processing	1.1227	96.8393	2	0.5614
Template load and register function	0.0001	0.0090	1	0.0001
states
state_id_array	0.0013	0.1116	1	0.0013
state_identifier_array	0.0017	0.1443	2	0.0008
Override
Cache load	0.0017	0.1454	19	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.0654	2	0.0004
Fetch class attribute name	0.0011	0.0983	5	0.0002
XML
Image XML parsing	0.0010	0.0856	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0011	6	0.0000
General
dbfile	0.0017	0.1481	23	0.0001
String conversion	0.0000	0.0039	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
1	content/datatype/view/ezxmltags/emphasize.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/emphasize.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs