Thanks Arie. That seems like a really good solution for my case... I'll
need to change parts of the code and assign right ACL to the files on
S3.
Arie Fishler wrote:
Hi,
If I can suggest something...seems like you architecture selection is a
bit strange. Having such a feature to your specific need seems to
complicate your normal way of operation. Why don't you make sure that
the dynamic application stuff is loaded into a central location from
which any of your app servers can pull?
This can either be a gluster share or an S3 bucket. Anything that is
persistent enough and can be used to synchronize any app server that
starts. By the way..."synchronize" here does not mean each server has
to pull anything but rather only have immediate access to everything...
On Thu, Mar 26, 2009 at 1:00 AM, andrej <[email protected]>
wrote:
Here's a scenario:
Most of the time I have one app instance running. The website hosts
community. Members upload new photos every day. Occasionally traffic
spikes happen that start another instance. After spike Scalr keeps the
new instance and shuts down the old. However the old instance has all
updates (photos), and the new only the last image.
Because of this I need to save app role every day.
Suggestion - can we choose which instance will be kept (not
terminated) after a spike? In my case I prefer to see the old instance
kept active and terminate newly started instances after activity has
fallen.
Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scalr-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
|
