Two conclusions deserve special emphasis. First, if a client does not -see the server's beacons, then it will use additional network and server -resources sending periodic state-of-health messages. Second, if a client does -not see the server's beacons, then it may not connect to a newly introduced -server that was initially inaccessible if the client timed out attempting to -find it. The typical situation where a client would not see the server's -beacon might be when the client isnt on the same IP subnet as the server, and -the EPICS_CA_ADDR_LIST was modified to include a destination address for the -server, but the server's beacon address list was not modified so that it's -beacons are received by the client.
+See also When a Client Does not See the Server's +Beacon.
+ +The rate at which name resolution (search) requests are sent exponentially +backs off to a plateau rate. The value of this plateau has an impact on +network traffic because it determines the rate that clients search for +channel names that are miss-spelled or otherwise don't exist in a server. +Furthermore, for clients that are unable to see the beacon from a new server, +the plateau rate may also determine the maximum interval that the client will +wait until discovering a new server.
+ +Starting with EPICS R3.14.7 this maximum search rate interval plateau in +seconds is determined by the EPICS_CA_MAX_SEARCH_PERIOD environment +variable.
+ +See also When a Client Does not See the Server's +Beacon.
See Dynamic Changes in the CA Client Library Search -Interval.
+Two conclusions deserve special emphasis. First, if a client does not +see the server's beacons, then it will use additional network and server +resources sending periodic state-of-health messages. Second, if a +client does not see a newly introduced server's beacon, then it will take up +to EPICS_CA_MAX_SEARCH_PERIOD to find that newly introduced server. +Also, starting with EPICS R3.14.7 the client library does not +suspend searching for a channel after 100 unsuccessful attempts until a +beacon anomaly is seen. Therefore, if the client library is from before +version R3.14.7 of EPICS and it timed out attempting to find a server whoose +beacon cant be seen by the client library then the client application might +need to be restarted in order to connect to this new beacon-out-of-range +server.
+ +The typical situation where a client would not see the server's beacon +might be when the client isnt on the same IP subnet as the server, and the +client's EPICS_CA_ADDR_LIST was modified to include a destination address for +the server, but the server's beacon address list was not modified so that +it's beacons are received by the client.