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
Environment information:
We have two opensearch clusters deployed on two different Kubernetes clusters in Azure.
We have enabled cross cluster replication between these two opensearch clusters deployed on two seaprate Kuberenetes clusters.
Whenever we push some documents into indices to the leader cluster and it is taking much longer time to replica.
We have tried with indices which are in KiloBytes as well as larger indices which are in GigaBytes.
In both cases, there is a definite lag we could observe from the time of pushing the documents in the leader site and the same documents being available in the follower site.
We had pushed an index 'projecttask' on the leader site. These are stats from leader site.
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open projecttask atOBXJVWT_6wp7cwV_Y0Mw 3 2 4657988 1786411 51.3gb 17.1gb
When we kept monitoring the remote site, the replication status on follower site was showing as BOOTSTRAPPING for a long time. Now status is showing as SYNCING but the time duration is taking a long time.
Posted output of replication status API at several times yesterday to monitor the status. If you can see the bytes_percent and files_percent, it is progressing very gradually. Seeking help on how to troubleshoot this further and to speed up the replication.
@VinDataR Please create an issue in the the OpenSearch repository as this relates to strategies of debugging cross cluster replication in core OpenSearch. OpenSearch Benchmark is a benchmarking client that runs workloads on clusters and helps users determine performance of operations such as queries.
Environment information:
We have two opensearch clusters deployed on two different Kubernetes clusters in Azure.
We have enabled cross cluster replication between these two opensearch clusters deployed on two seaprate Kuberenetes clusters.
Whenever we push some documents into indices to the leader cluster and it is taking much longer time to replica.
We have tried with indices which are in KiloBytes as well as larger indices which are in GigaBytes.
In both cases, there is a definite lag we could observe from the time of pushing the documents in the leader site and the same documents being available in the follower site.
We had pushed an index 'projecttask' on the leader site. These are stats from leader site.
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open projecttask atOBXJVWT_6wp7cwV_Y0Mw 3 2 4657988 1786411 51.3gb 17.1gb
When we kept monitoring the remote site, the replication status on follower site was showing as BOOTSTRAPPING for a long time. Now status is showing as SYNCING but the time duration is taking a long time.
Posted output of replication status API at several times yesterday to monitor the status. If you can see the bytes_percent and files_percent, it is progressing very gradually. Seeking help on how to troubleshoot this further and to speed up the replication.
curl -XGET -k -u ':' 'http://localhost:9200/_plugins/_replication/projecttask/_status?pretty'
The text was updated successfully, but these errors were encountered: