[
https://issues.apache.org/jira/browse/SOLR-9488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470954#comment-15470954
]
Shalin Shekhar Mangar commented on SOLR-9488:
---------------------------------------------
I was wondering why SolrCloud is not affected by this bug. This is because on
shutdown, the DirectUpdateHandler2 commits explicitly and writes the commit
data instead of relying on IndexWriter.close. The reason why this did not
happen for shard split is because DUH2 commits on close only if the update log
has uncommitted changes and is active. Both of those conditions are false when
we split shards and merge the index directly into a core.
> Shard split can fail to write commit data on shutdown
> -----------------------------------------------------
>
> Key: SOLR-9488
> URL: https://issues.apache.org/jira/browse/SOLR-9488
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 4.10.4, 5.5.2, 6.2
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: master (7.0), 6.3
>
> Attachments: SOLR-9488.patch, SOLR-9488.patch
>
>
> As found in SOLR-9438, the Shard split can fail to write commit data on
> shutdown because it doesn't explicitly call commit. This causes replication
> to fail because without the commit data, the master version is always 0 which
> is assumed to mean an empty index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
