{"push_id":884547358,"size":1,"distinct_size":1,"ref":"refs/heads/ovirt-3.6","head":"39abf6136ac5608ffc926d7eb0b4561657664e2b","before":"c69ae155785d6e70f3ddbca3c73e87a23c0d4ac3","commits":[{"sha":"39abf6136ac5608ffc926d7eb0b4561657664e2b","author":{"email":"c7100b580e6017ef67482ace46578cdd2d2e0dfe@redhat.com","name":"Francesco Romani"},"message":"daemon: revert cpu-affinity enabling by default\n\nIn commit a1d4e23 we enabled by default the cpu affinity\nfor VDSM, after we had confirmation this delivered important\nperformance benefits.\n\nUnfortunately, the default setting, was too naive\nfor large, complex setup, like the ones we first seen on PPC64\nhosts. VDSM tries to pin itself to cpu #1, but if this cpu\nis offline, it fails to start.\n\nThis was indeed expected behaviour, and the fix is trivial (just\nreconfigure /etc/vdsm/vdsm.conf), but it is very unpractical in large\nsettings, where the admin has to manually fix many configuration\nfiles. This obviously breaks automated flow.\n\nUnfortunately, is too late in the release schedule to add smarter\nCPU selection logic (e.g. patch 49402), so to avoid VDSM start\nfailures, we revert the default, to fall back to a safe state.\n\nChange-Id: I91e3753172b4fa4d60686b9cf21e596d2f408393\nRelated-To: https://gerrit.ovirt.org/#/c/49402\nRelated-To: https://bugzilla.redhat.com/1279431\nBackport-To: 3.6\nBug-Url: https://bugzilla.redhat.com/1286462\nSigned-off-by: Francesco Romani <fromani@redhat.com>\nReviewed-on: https://gerrit.ovirt.org/49463\nReviewed-by: Dan Kenigsberg <danken@redhat.com>\nContinuous-Integration: Jenkins CI","distinct":true,"url":"https://api.github.com/repos/oVirt/vdsm/commits/39abf6136ac5608ffc926d7eb0b4561657664e2b"}]}