Hi Tushar,
This is not usecase suitable for MS model. You should go with Solr Cloud, or if
that is an overhead for you, have separate Solr, each doing indexing on its
own. Solr provides eventual consistency anyway, so you should have some sort of
stickiness in place even if you use MS model.
Em
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
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
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
