OpenVZ Forum: Support » Success w/ Kernel 2.6.26 or 2.6.27

Home » General » Support » Success w/ Kernel 2.6.26 or 2.6.27

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Success w/ Kernel 2.6.26 or 2.6.27 [message #36496]

Wed, 24 June 2009 13:55

seanfulton
Messages: 105
Registered: May 2007

Senior Member

I'm considering upgrading one or more of our production servers to a newer kernel to try to combat some IO issues we are having with a backup process on the HN depriving the VEs of resources. We're currently CentOS 5.2 on the host nodes with the latest ovzkernel-2.6.18 variant and have not been able to fix the issue.

I am wondering if anyone on these forums is using the 2.6.27 or 2.6.26 ovzkernels on a heavily loaded server and if so, what your experiences have been.

sean

Report message to a moderator

Re: Success w/ Kernel 2.6.26 or 2.6.27 [message #36504 is a reply to message #36496]

Fri, 26 June 2009 06:33

arghbis
Messages: 35
Registered: November 2007

Member

I've tried both of them and they juste work like they should.

no particular instability, even under high load (cpu, mem, bandwidth)

Report message to a moderator

Re: Success w/ Kernel 2.6.26 or 2.6.27 [message #36508 is a reply to message #36496]

Fri, 26 June 2009 17:26

swindmill
Messages: 57
Registered: April 2007

Member

I assume you've attempted to use nice and ionice to resolve the issue?

I am running a backup job using rsync/rdiff-backup on my host nodes using the rhel 2.6.18 openvz kernels and have been able to reduce or eliminate any I/O impact seen by my containers with these two tools.

Report message to a moderator

Re: Success w/ Kernel 2.6.26 or 2.6.27 [message #36509 is a reply to message #36496]

Fri, 26 June 2009 17:43

seanfulton
Messages: 105
Registered: May 2007

Senior Member

Interesting. How are you doing this?

We have a centralized backup server with 5T of storage for backups and it is NFS-mounted to our openvz servers, which use vzdump for backups.

I have tried writing a utility to rsync the data to the backup server and do the tar/compress on the backup server, but that just serves to paralize the backup server. The amount of data is such that doing them sequentially would take about 12 hours, whereas spreading the load across the Openvz servers allows us to finish in about 4 hours ... crippling the OpenVZ servers in the process Wink

I'd love to hear what you've done and how it works.

sean

Report message to a moderator

Previous Topic:	vzdump - not using single file
Next Topic:	Harddisk size

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Sep 04 20:13:48 GMT 2024

Total time taken to generate the page: 0.05456 seconds