s
> merged.
>
> HTH,
> Emir
> --
> Monitoring - Log Management - Alerting - Anomaly Detection
> Solr & Elasticsearch Consulting Support Training - http://sematext.com/
>
>
>
> > On 21 Jun 2018, at 19:59, sujatha sankaran
> wrote:
> >
> > Thanks,S
collection happening at the same time.
Sujatha
On Thu, Jun 21, 2018 at 1:21 PM, Shawn Heisey wrote:
> On 6/21/2018 9:59 AM, sujatha sankaran wrote:
> > Currently from our business perspective we find that we are left with no
> > options for deleting docs in a batch load as :
> &g
x27;t have to delete at all.
Thanks,
Sujatha
On Wed, Jun 20, 2018 at 8:31 PM, Shawn Heisey wrote:
> On 6/20/2018 3:46 PM, sujatha sankaran wrote:
> > Thanks,Shawn. Very useful information.
> >
> > Please find below the log details:-
>
> Is your collection using the
c.LeaderInitiatedRecoveryThread Leader
is publishing core=crm_v2_01_shard3_replica3 coreNodeName =core_node12
state=down on behalf of un-reachable replica
http://masked:8983/solr/crm_v2_01_shard3_replica3/
Thanks,
Sujatha
On Wed, Jun 20, 2018 at 11:18 AM, Shawn Heisey wrote:
> On 6/15/20
We were initially having an issue with DBQ and heavy batch updates which
used to result in many missing updates.
After reading many mails in mailing list which mentions that DBQ and batch
update do not work well together, we switched to DBI. But we are seeing
issue as mentioned in this jira is
