We recently have upgraded to PeopleTools 8.55.05 and along with this we have upgraded our infrastructure also. For windows batch server, we have upgraded our infrastructure from windows 2008 R2 to Windows 2012 R2.
After installing new Tools version (PeopleTools 8.55.05) on windows 2012 R2 , we noticed performance issue while booting up the batch server. On windos 2012, each server process is taking approx 50-60 seconds to boot up and in turn the complete batch server is booting up in approximately 10 minutes. Before upgrade, we were on Tools 8.53 with windows 2008 and batch server boot up process was quite fast and as per the expectation.
As a part of our analysis we did a packet capture(using wireshark) and noticed a lot of NB (NetBios name resolution) and LLMNR (Link-Local Multicast Name Resolution) packets, which appeared to be slowing things down for the process scheduler processes.
For the box where the scheduler is booting up slow, we have noticed that prior to LDAP query there are series of DNS, NB and LLMNR queries to resolve the database name. However, on windows 2008 R2 , it just gets straight into the LDAP Query.
To force the scheduler process to directly go into the LDAP query, we have made the following changes:
This has worked for us and we are able to boot up batch server fast on windows 2012 R2, however, having said this, we are still trying to understand why the process scheduler of Tools 8.55 is querying DNS, NB and LLMNR before LDAP query.
We are not sure if there is any change in the way process scheduler is going to communicate with underlying Operating System with PeopleTools 8.55.
If any of you have any idea on this, please let me know. I will happy to listen and discuss on the issue with you.
After installing new Tools version (PeopleTools 8.55.05) on windows 2012 R2 , we noticed performance issue while booting up the batch server. On windos 2012, each server process is taking approx 50-60 seconds to boot up and in turn the complete batch server is booting up in approximately 10 minutes. Before upgrade, we were on Tools 8.53 with windows 2008 and batch server boot up process was quite fast and as per the expectation.
As a part of our analysis we did a packet capture(using wireshark) and noticed a lot of NB (NetBios name resolution) and LLMNR (Link-Local Multicast Name Resolution) packets, which appeared to be slowing things down for the process scheduler processes.
For the box where the scheduler is booting up slow, we have noticed that prior to LDAP query there are series of DNS, NB and LLMNR queries to resolve the database name. However, on windows 2008 R2 , it just gets straight into the LDAP Query.
To force the scheduler process to directly go into the LDAP query, we have made the following changes:
- Disabled "Link-Layer Topology Discovery Mapper I/O Driver" interface
- Disabled "Link-Layer Topology Discovery Responder" interface
- Disabled "Internet Protocol Version 6" interface
- Disabled NetBIOS over TCP/IP
- Disabled LLMNR by setting Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> DNS Client -> Turn Off Multicast Name Resolution = Enabled
This has worked for us and we are able to boot up batch server fast on windows 2012 R2, however, having said this, we are still trying to understand why the process scheduler of Tools 8.55 is querying DNS, NB and LLMNR before LDAP query.
We are not sure if there is any change in the way process scheduler is going to communicate with underlying Operating System with PeopleTools 8.55.
If any of you have any idea on this, please let me know. I will happy to listen and discuss on the issue with you.
No comments:
Post a Comment