Is eZPublish-3 supports failover / redundancy?

Previous topic

Developer

Next topic

Author	Message
Srinivas Rao	Thursday 31 July 2003 10:07:49 pm Hi all, Is eZPublish-3 supports failover / redundancy? What steps would be needed to implement it? --vaasu
Bård Farstad	Friday 01 August 2003 12:19:41 am Yes, you can use eZ publish in a failover / redundancy environment. There are several ways of setting up this. You need to use the clustering functionality in MySQL and e.g. Linux Virtual server. Some information about this is found here: http://ez.no/developer/ez_publish_3/articles/ez_publish_3_enterprise_setup_test We don't have a full tutorial on this yet. --bård Documentation: http://ez.no/doc
Tony Wood	Friday 01 August 2003 6:51:10 am Hi, Our environment has failover capabilities. As long as you follow the standard failover rules for hardware, software in our case Linux, Apache and MySQL you will be fine. Tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Author

Message

Srinivas Rao

Thursday 31 July 2003 10:07:49 pm

Hi all,

Is eZPublish-3 supports failover / redundancy? What steps would be needed to implement it?

--vaasu

Bård Farstad

Friday 01 August 2003 12:19:41 am

Yes, you can use eZ publish in a failover / redundancy environment. There are several ways of setting up this. You need to use the clustering functionality in MySQL and e.g. Linux Virtual server.

Some information about this is found here:
http://ez.no/developer/ez_publish_3/articles/ez_publish_3_enterprise_setup_test

We don't have a full tutorial on this yet.

--bård

Documentation: http://ez.no/doc

Tony Wood

Friday 01 August 2003 6:51:10 am

Hi,

Our environment has failover capabilities. As long as you follow the standard failover rules for hardware, software in our case Linux, Apache and MySQL you will be fine.

Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

eZ debug

Timing:	Jan 31 2025 04:16:14
Script start
Timing:	Jan 31 2025 04:16:14
Module start 'layout'
Timing:	Jan 31 2025 04:16:14
Module start 'content'
Timing:	Jan 31 2025 04:16:14
Module end 'content'
Timing:	Jan 31 2025 04:16:14
Script end

Main resources:

Total runtime	0.0143 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	588.2656	151.2266
Module start 'layout'	0.0052	0.0025	739.4922	36.6797
Module start 'content'	0.0078	0.0053	776.1719	90.1875
Module end 'content'	0.0130	0.0012	866.3594	33.9922
Script end	0.0142		900.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	15.7143	14	0.0002
Check MTime	0.0010	6.7306	14	0.0001
Mysql Total
Database connection	0.0009	6.3228	1	0.0009
Mysqli_queries	0.0021	14.8000	3	0.0007
Looping result	0.0000	0.0969	1	0.0000
Template Total	0.0009	6.2	1	0.0009
Template load	0.0007	4.8871	1	0.0007
Template processing	0.0002	1.3321	1	0.0002
Override
Cache load	0.0005	3.4063	1	0.0005
General
dbfile	0.0011	7.7184	8	0.0001
String conversion	0.0000	0.0568	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs