
This is a multi-part message in MIME format. --------------000800040702030209080207 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Steve Gordon wrote:
Has anyone else experienced this issue?
Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on?
I'm going to take a stab and guess Fedora. This came up for an unrelated reason in #fedora-devel the other day, because Fedora (and I suspect Debian as well) has a policy of sticking as close to upstream as possible it uses the shmmax of the upstream kernel - which is as you note quite low. In RHEL and other EL6 derivatives this value is modified and set much higher.
Steve
OK, learned something because I didn't suspect that Fedora would be so low because its set higher in RHEL en for example CentOS that I use on a db production platform. Thought that Fedora and RHEL were much closer. Joop --------------000800040702030209080207 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Steve Gordon wrote: <blockquote cite="mid:500936754.2964558.1348241174744.JavaMail.root@redhat.com" type="cite"> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> Has anyone else experienced this issue? </pre> </blockquote> <pre wrap="">Yes, not related to oVirt but on a database server also running Postgres. It seems that either the package maintainer is very conservative or postgres itself is. Standard on the Debian 6 server was also very low shmmax. What is the OS you run ovirt-engine on? </pre> </blockquote> <pre wrap=""><!----> I'm going to take a stab and guess Fedora. This came up for an unrelated reason in #fedora-devel the other day, because Fedora (and I suspect Debian as well) has a policy of sticking as close to upstream as possible it uses the shmmax of the upstream kernel - which is as you note quite low. In RHEL and other EL6 derivatives this value is modified and set much higher. Steve </pre> </blockquote> OK, learned something because I didn't suspect that Fedora would be so low because its set higher in RHEL en for example CentOS that I use on a db production platform.<br> Thought that Fedora and RHEL were much closer.<br> <br> Joop<br> <br> <br> </body> </html> --------------000800040702030209080207--