Hi, Just following up on my question. Can someone provide me with pointers.
On Mon, Mar 15, 2021 at 1:19 PM Pushkar Raste <[email protected]> wrote: > Hi, > We are using the legacy solr setup (I am going to refer to the nodes as > leaders and followers. I think that’s what the Solr community has decided > to call those). Our setup roughly looks like > > *Repeater (Remote DC)* --- *Followers(Remote DC)* > | > | > *Leader* --- *Repeater* (*Local DC*) ---- *Followers (Local DC)* > > For the past couple of days repeaters in the geographically remote data > center are failing to keep up with the repeater in Local DC. As per logs > the files on the Local DC get deleted before getting copied to the repeater > in remote DC. In order for the remote DC repeater to sync up, we have to > disable pollin on the repeater in the local DC. > > I am trying to figure out how to make the files on the Local DC stick > around longer. I am trying to wrap around the suggestions in > https://solr.apache.org/guide/7_7/index-replication.html > > I am trying to understand if tuning commitReserveDuration and/or > maxCommitsToKeep would help. Currently with have commitReserveDuration > set to 1 hr and maxCommitsToKeep to 1. > > We are also looking into enabling compression for replication between the > Local DC repeater to Remote DC repeater. > > Can people provide other suggestions. I understand that not a lot of us > are using the legacy setup but just wondering if the Pull Replicas use the > same mechanism as the Legaacy setup and if anyone using the Pull Replicas > have faced similar issues. >
