Hi Emir, Thanks for the response. Actually the use case is real time indexing from DB to solr in every second on the master server using queueing mechanism. So, I think instead of doing hard commits every second we should go for soft commits. And doing hard commits after some intervals. And we have to replicate the data to slave immediately.
Regards, Tushar On Thu, 3 Sep 2020 at 16:17, Emir Arnautović <emir.arnauto...@sematext.com> wrote: > Hi Tushar, > Replication is file based process and hard commit is when segment is > flushed to disk. It is not common that you use soft commits on master. The > only usecase that I can think of is when you read your index as part of > indexing process, but even that is bad practice and should be avoided. > > HTH, > Emir > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > > > On 3 Sep 2020, at 08:38, Tushar Arora <tarora7...@gmail.com> wrote: > > > > Hi, > > I want to ask if the soft commit works in replication. > > One of our use cases deals with indexing the data every second on a > master > > server. And then it has to replicate to slaves. So if we use soft commit, > > then does the data replicate immediately to the slave server or after the > > hard commit takes place. > > Use cases require transfer of data from master to slave immediately. > > > > Regards, > > Tushar > >
