[
https://issues.apache.org/jira/browse/SOLR-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486304#comment-15486304
]
ASF subversion and git services commented on SOLR-9408:
-------------------------------------------------------
Commit 2335cf7cd52323c02041f28ebdbf7f8c5bb5bb4e in lucene-solr's branch
refs/heads/branch_6_2 from [~varunthacker]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2335cf7 ]
SOLR-9408: Fix TreeMergeOutputFormat to add timestamp metadata to commits
> Add solr commit data in TreeMergeRecordWriter
> ---------------------------------------------
>
> Key: SOLR-9408
> URL: https://issues.apache.org/jira/browse/SOLR-9408
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - MapReduce
> Reporter: Jessica Cheng Mallet
> Assignee: Varun Thacker
> Labels: mapreduce, solrcloud
> Fix For: 6.2.1, master (7.0)
>
> Attachments: SOLR-9408.patch, SOLR-9408.patch, SOLR-9408.patch
>
>
> The lucene index produced by TreeMergeRecordWriter when the segments are
> merged doesn't contain Solr's commit data, specifically, commitTimeMsec.
> This means that when this index is subsequently loaded into SolrCloud and if
> the index stays unchanged so no newer commits occurs, ADDREPLICA will appear
> to succeed but will not actually do any full sync due to SOLR-9369, resulting
> in adding an empty index as a replica.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
