Hi, First of all thanks for your answer, today has increased cpu usage, only change is add a new group with 3500 users, It could be the problem? a last question, now we only have one dc, no replication. If we add another dc will increase performance and will be a loadbalance the load? Now I can't upgrade to 4.7, I have to shcedule an upgrade and make test, any suggestion or a workaround? Thanks 2018-02-13 23:15 GMT+01:00 Andrew Bartlett <abartlet at samba.org>:> On Tue, 2018-02-13 at 23:10 +0100, Trenta sis via samba wrote: >> Hi, >> >> I have detected a high cpu usage with samba 4, process that is using >> high cpu (100%) many time is /usr/local/samba/sbin/samba -D >> and samba version is 4.4.5, anybody can give information how to debug >> and find the problem or how to solve the issue. >> >> Now I can't upgrade, in a few months i'll upgrade, but now I need to >> find why this high cpu usage > > The answer is very simple, it is because you haven't upgraded. > > You can debug it with perf flame graphs, but save yourself the bother > and just upgrade to 4.7. Replication of large numbers of group > memberships is a particularly likely candidate, but there were many > other issues as well. > > Our customers came back to us wondering why their Samba 4.7 DCs are > running essentially zero load, because it was so unexpected :-) > > Andrew Bartlett > > -- > Andrew Bartlett > https://samba.org/~abartlet/ > Authentication Developer, Samba Team https://samba.org > Samba Development and Support, Catalyst IT > https://catalyst.net.nz/services/samba > > > >
On Tue, 2018-02-13 at 23:31 +0100, Trenta sis wrote:> Hi, > > First of all thanks for your answer, today has increased cpu usage, > only change is add a new group with 3500 users, It could be the > problem?Yes, that will do it. This is exactly the use case we have been working to make perform well since Samba 4.5, with Samba 4.7 having the best behaviour so far.> a last question, now we only have one dc, no replication. > If we add another dc will increase performance and will be a > loadbalance the load?Adding another 4.4 DC will cause catastrophic outages and is not recommended as the worst issues are in the replication engine. Just schedule an outage, upgrade to 4.7 by joining that to the domain, then transfer the roles and then add your second DC (which is otherwise always recommended).> Now I can't upgrade to 4.7, I have to shcedule an upgrade and > make test, any suggestion or a workaround?I understand you feel unable to commit to the upgrade, but there is no workaround now you have the extra group memberships Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Development and Support, Catalyst IT https://catalyst.net.nz/services/samba
OK, Thanks for your information. If I remove this new group with 3500 users, I understand that load will be recovered to normal usage, correct? About upgrade if I have only one server with 4.4.5 the best option is add another dc with 4.7 compiled, then transfer and upgrade (or join old server) or upgrade actual 4.4.5 to 4.7 and then add a new dc? I like to keep 2 dc with same config and fully compatible and stable Thanks 2018-02-13 23:40 GMT+01:00 Andrew Bartlett <abartlet at samba.org>:> On Tue, 2018-02-13 at 23:31 +0100, Trenta sis wrote: >> Hi, >> >> First of all thanks for your answer, today has increased cpu usage, >> only change is add a new group with 3500 users, It could be the >> problem? > > Yes, that will do it. This is exactly the use case we have been > working to make perform well since Samba 4.5, with Samba 4.7 having the > best behaviour so far. > >> a last question, now we only have one dc, no replication. >> If we add another dc will increase performance and will be a >> loadbalance the load? > > Adding another 4.4 DC will cause catastrophic > outages and is not recommended as the worst issues are in the > replication engine. > > Just schedule an outage, upgrade to 4.7 by joining that to the domain, > then transfer the roles and then add your second DC (which is otherwise > always recommended). > >> Now I can't upgrade to 4.7, I have to shcedule an upgrade and >> make test, any suggestion or a workaround? > > I understand you feel unable to commit to the upgrade, but there is no > workaround now you have the extra group memberships > > Andrew Bartlett > -- > Andrew Bartlett > https://samba.org/~abartlet/ > Authentication Developer, Samba Team https://samba.org > Samba Development and Support, Catalyst IT > https://catalyst.net.nz/services/samba > > > >