So, I take it that DPChallenge.com has no hardware redundancy in place? A site of this caliber with no disaster recovery plan? Hmm... I figured there would be some fail-over cluster node that the system would switch over to in such a situation.
Langdon, care to tell us the nature of the h/w failure? Did this occur in the web servers, in the app servers, or in the database servers? Us geeks want to know. ;-)
Landon, care to tell us the nature of the h/w failure? Did this occur in the web servers, in the app servers, or in the database servers? Us geeks want to know. ;-)
I don't know what they're using but since I joined up there has been darn little downtime. I'm impressed.
Love the site and really appreciate the work that goes into making us all better photographers, but I gotta say, no single hardware failure should be able to bring it down.
Also, I noticed that during the bouncing that the server was quite happy to reveal all sorts of version info about the OS, web server software etc, not good, that should all be disabled in a production environment.
Love the site and really appreciate the work that goes into making us all better photographers, but I gotta say, no single hardware failure should be able to bring it down.
Also, I noticed that during the bouncing that the server was quite happy to reveal all sorts of version info about the OS, web server software etc, not good, that should all be disabled in a production environment.
For you geeks out there, here is some info on the dpchallenge.com site. It appears that DPC runs Apache 2.2.3
*By the way, this is all public information from netcraft.com.
[edited to add thumbnails, with links to original sized images]
