Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 10
Newest
 Caucus
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 29 votes cast
Jan
23
comment Scaling applications with heavy bandwidth needs
Thanks! Getting more bandwidth is an option I forgot to list :). Adding tiers won't solve the bandwidth limit. I think my question is exactly how I should do "adopt to more complexity than one server daemon". But thanks for the link, the answers provide some interesting things that I now need to research like IP or TCP load balancing, IPVS and Direct Server Return
Jan
23
revised Scaling applications with heavy bandwidth needs
edited tags
Jan
22
asked Scaling applications with heavy bandwidth needs
Nov
25
awarded  Caucus
Aug
29
comment What User Should NGinx and PHP be running as?
would you elaborate on that?
Aug
8
awarded  Notable Question
Sep
27
awarded  Popular Question
Jun
5
awarded  Popular Question
May
20
awarded  Caucus
Mar
27
accepted Rolling update with puppet, ansible or fabric
Mar
27
comment Rolling update with puppet, ansible or fabric
Thanks, I'll check this out!
Mar
27
comment Rolling update with puppet, ansible or fabric
Ah, thanks! Still one more issue: what if jetty is up and running at this port but my app needs some initialization time? Can I specify a full ping URL instead of only the port? Looks like the docs say no: ansible.cc/docs/modules.html#wait-for
Mar
27
comment Rolling update with puppet, ansible or fabric
Redeployment without restart won't work over a long timespan (see permgenError problems on stackoverflow). Especially if you deploy lots of wars/jars into it.
Mar
27
comment Rolling update with puppet, ansible or fabric
Still unsure if I understand what you mean. What I want is that it waits until the ping URL returns OK and then proceeds instead of the fixed length timeout (which can be too long but also too short)
Mar
27
revised Rolling update with puppet, ansible or fabric
edited title
Mar
27
revised Rolling update with puppet, ansible or fabric
edited title
Mar
27
revised Rolling update with puppet, ansible or fabric
added 127 characters in body
Mar
27
revised Rolling update with puppet, ansible or fabric
added 127 characters in body
Mar
27
comment Rolling update with puppet, ansible or fabric
Well I think the main problem is timing: what if all jetty servers are restarting at the same time?
Mar
27
comment Rolling update with puppet, ansible or fabric
Nice! Instead of a fixed timeout - how could I use my ping-URL to wait for the next server restart?