In a cross cluster search configuration, is there a request cache similar to the shard request cache?

In a cross cluster search configuration, can/does the node acting as the federated client keep a request cache to improve the response time/performance of duplicate searches?

An example would be in situations where the remote clusters are behind slower WAN links, etc. In some queries, this would prevent the federated client node from having to repeatedly transmit the same request to the remote clusters.


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.