I am wondering how I can clear the local cache and have it reloaded via the database not the local server. To my understanding right now, the site is indexed within App_Data/TEMP/ExamineIndexes/Internal. If we remove this file none of our nodes show up. We tried republishing via http://YOURDOMAIN/Umbraco/dialogs/republish.aspx?xml=true and via the back-end (admin).
Ideally we need a work around, like a script that will delete the neccessary files, refresh the application pool and reload all nodes from the database to rebuild the cache.
Any help you can pass our way will be great, because we desperately need to get this working. And if we cannot, we will have to move to another CMS (which we really do not want to do).
Unfortunately, Distributed Calling will not work with Elastic Beanstalk as you'll need pre-defined list of IP addresses relating to each of the EC2 instances within your Elastic Beanstalk environment.
A work around might be to hook into various application and Umbraco events to help republish each EC2 instance's caches. For example, application start and content publishing. With an Amazon API call from an EC2 instance, you can get a full list of instances within the current Elastic Beanstalk environment. Once you have the list, you should be able to call the republish dialog for each box.
Thank you for your response. I have been reading up on the republish options available from within umbraco. The republish only republishes via the cached xml, not the database. Hence, I am unsure how that will help me. So would you be willing to elaborate on how I would call the republish dialog for each box (guessing server) to replenish my cache (after I have my list of known servers)?
I know this code says it will republish the nodes from scratch and refresh the xml. I tested it using the corresponding link "/Umbraco/dialogs/republish.aspx?xml=true" When I ran this I still had missing nodes. I was on a secondary server that wasn't our "main" server (were the latest nodes where added). So I cannot find a way to republish the cache on a secondary server.
v 6.1.6 on Amazon ec2 load balanced?
We need help getting our umbraco 6.1.6 working on load balanced Amazon ec2 instances which connect to a single Amazon RDS server for the database.
We built the site before moving to Amazon and the custom unique DNS will not work for us. (Suggest at http://our.umbraco.org/documentation/Installation/load-balancing)
I am wondering how I can clear the local cache and have it reloaded via the database not the local server. To my understanding right now, the site is indexed within App_Data/TEMP/ExamineIndexes/Internal. If we remove this file none of our nodes show up. We tried republishing via http://YOURDOMAIN/Umbraco/dialogs/republish.aspx?xml=true and via the back-end (admin).
Ideally we need a work around, like a script that will delete the neccessary files, refresh the application pool and reload all nodes from the database to rebuild the cache.
We have read http://our.umbraco.org/documentation/Installation/load-balancing. And these suggestions will not work for us. And we have also read: http://our.umbraco.org/wiki/reference/api-cheatsheet/publishing-and-republishing.
Any help you can pass our way will be great, because we desperately need to get this working. And if we cannot, we will have to move to another CMS (which we really do not want to do).
Thanks so much,
Robin
Hi Robin,
Unfortunately, Distributed Calling will not work with Elastic Beanstalk as you'll need pre-defined list of IP addresses relating to each of the EC2 instances within your Elastic Beanstalk environment.
A work around might be to hook into various application and Umbraco events to help republish each EC2 instance's caches. For example, application start and content publishing. With an Amazon API call from an EC2 instance, you can get a full list of instances within the current Elastic Beanstalk environment. Once you have the list, you should be able to call the republish dialog for each box.
Dan.
Hi Dan,
Thank you for your response. I have been reading up on the republish options available from within umbraco. The republish only republishes via the cached xml, not the database. Hence, I am unsure how that will help me. So would you be willing to elaborate on how I would call the republish dialog for each box (guessing server) to replenish my cache (after I have my list of known servers)?
I know this code says it will republish the nodes from scratch and refresh the xml. I tested it using the corresponding link "/Umbraco/dialogs/republish.aspx?xml=true" When I ran this I still had missing nodes. I was on a secondary server that wasn't our "main" server (were the latest nodes where added). So I cannot find a way to republish the cache on a secondary server.
Thanks again, Robin
is working on a reply...