| Re: How to prevent total unavailability due Unable to fork [message #51220 is a reply to message #51212] |
Tue, 11 March 2014 15:51   |
Paparaciz
Messages: 302
Registered: August 2009
|
Senior Member |
|
|
postcd wrote on Sun, 09 March 2014 22:38
Let me please know why in case of example shared hosting no one need to worry about memory, they just hit the barrier and nnothing happens and in case of openvz one must be scared of ram limit.. i dont understand why damage happens, it appears to me like a bug..
in shared hosting server admins worries about resources usage and in case client tries to run heavy applications or sites with high load than they just offer for client to move to dedicated server or virtual server nowadays. If client doesn't agree with such offer, than contract is just terminated.
with virtual servers, provider is responsible to create a reasonable resource limitations for some price. there comes some issues. looking to spam messages in this forum from you, personaly I don't understand what service provider you are and even who can use your service. you don't understand how things works, how linux works, and you requesting spoon feeding very much.
So, if virtual server provider don't understand what limitations to set, how this affects applications, than what we can talk about?
speaking about damaging data- what do you think will happen with data in database if half of data was written to file, and than suddenly application is terminated. think about it like pulling power cable from dedicated server.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
