You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross Cluster Search is not returning partial result in case of skip_unavailable is true. This is happening in the case when one of the destination node is replaced with another node.
For running cross cluster search, we have to add destination cluster seed nodes in source cluster. So when cluster connection alias seed node setting is updated with new node of destination cluster. Cross cluster search(CCS) started failing even skip unavailable flag is true in source cluster setting.
@dblock This issue is in opensearch not in replication package. skip_unavailable cluster setting flag is part of core. This setting is not getting recognized when we update seed_nodes cluster setting.
Can you please move it back to opensearch. Also you can assign it to me. I will raise the PR with the fix.
dblock
transferred this issue from opensearch-project/cross-cluster-replication
May 23, 2024
Describe the bug
Cross Cluster Search is not returning partial result in case of skip_unavailable is true. This is happening in the case when one of the destination node is replaced with another node.
For running cross cluster search, we have to add destination cluster seed nodes in source cluster. So when cluster connection alias seed node setting is updated with new node of destination cluster. Cross cluster search(CCS) started failing even skip unavailable flag is true in source cluster setting.
Doc for cross cluster search setup.
Related component
Search
To Reproduce
"cluster.remote.remote-alias.skip_unavailable" : "true"
"cluster.remote.remote-alias.seeds"
Expected behavior
CCS request should be return 200 as response with skipped as 1.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: