There are two operational limits that can be imposed while a DSA is servicing a distributed request, either the time limit or the size limit.
When a request is received by a local DSA, a time limit can be applied (for example, max-op-time, or service time limit). If the request is either chained or multi-chained to a remote DSA, the local DSA still retains a reference to the request. This reference is impacted by the time limit even though the request is now being serviced by one or more remote DSAs.
Example:
If max-op-time is set to 30 seconds and Democorp: <c AU><o Democorp> receives a request in the scope of UNSPSC: <c AU><o UNSPSC> the request is chained. If Democorp does not receive a response from UNSPSC for 30 seconds, a request refusal (adminLimitExceeded) is sent to the client. Democorp also sends an abandon request to UNSPSC in an attempt to stop the request from continuing.
When a search request is received by a local DSA, a size limit is imposed on the result (for example, max-op-size, or service size limit). If the request is chained or multi-chained to another DSA then the local DSA limit is not enforced. The size limit is only enforced by the data DSA performing the search locally.
Example:
If max-op-size is set to 100 for all DSAs and Router: <c AU> receives a whole subtree search with scope <c AU>, the search is multi-chained to both Democorp: <c AU><o Democorp> and UNSPSC: <c AU><o UNSPSC>. Democorp and UNSPSCS both have the size limit applied and return 100 entries each with a partial outcome (adminLimitExceeded). The router collates the results (200 entries) and sends the result (including partial outcome) to the client. The router does not trim the result set, as the size limit is unenforced by the router, but the DSA handles the chained request.
|
Copyright © 2013 CA.
All rights reserved.
|
|