Bug 594668
Summary: | ypbind probes for the fastest server too often | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Tomas Smetana <tsmetana> | |
Component: | ypbind | Assignee: | Honza Horak <hhorak> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | qe-baseos-daemons | |
Severity: | high | Docs Contact: | ||
Priority: | urgent | |||
Version: | 5.5 | CC: | azelinka, bgollahe, kvolny, mpoole, ovasik, prc | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Each NIS client can bind to different NIS servers, but can only be bound to one server at a time. To maintain its connection to a server, an NIS client checks connection to an active server every 20 seconds and once in a while tries to find the fastest available server. Previously, clients searched for the fastest server every minute, which sometimes caused heavy traffic and response delays. With this update, clients search for the fastest server every 15 minutes, preventing this bug.
|
Story Points: | --- | |
Clone Of: | ||||
: | 594670 594693 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-23 11:13:31 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 594693, 714028 |
Description
Tomas Smetana
2010-05-21 10:04:08 UTC
Correct, it seems it was added for debugging purposes. The limit should be set back to 900. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Each NIS client can bind to different NIS servers, but can only be bound to one server at a time. To maintain its connection to a server, an NIS client checks connection to an active server every 20 seconds and once in a while tries to find the fastest available server. Previously, clients searched for the fastest server every minute, which sometimes caused heavy traffic and response delays. With this update, clients search for the fastest server every 15 minutes, preventing this bug. just a note, with RHEL5.8-SERVER-20111030.0 BETA 1.0 - ypbind-1.19-12.el5_6.1 this fails our regression testing, it seems that ypbind doesn't do the checks at all (IOW, the debug log does not contain any single occurence of "Checking for new fastest server.") (In reply to comment #20) > just a note, with RHEL5.8-SERVER-20111030.0 BETA 1.0 - ypbind-1.19-12.el5_6.1 > this fails our regression testing, it seems that ypbind doesn't do the checks > at all (IOW, the debug log does not contain any single occurence of "Checking > for new fastest server.") seems like misconfiguration which wasn't discovered before thanks to different lab environment test updated: [kvolny@kvolny bz594668-ypbind-probes-for-the-fastest-server-too-often]$ cvs diff -r 1.9 runtest.sh Index: runtest.sh =================================================================== RCS file: /cvs/dist/tests/ypbind/Regression/bz594668-ypbind-probes-for-the-fastest-server-too-often/runtest.sh,v retrieving revision 1.9 retrieving revision 1.10 diff -r1.9 -r1.10 37a38 > rlFileBackup /etc/yp.conf 42a44 > echo 'domain AZOR server 1.2.3.4' >> /etc/yp.conf 73a76 > rlFileRestore |