[
https://issues.apache.org/jira/browse/SOLR-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484074#comment-15484074
]
Varun Thacker commented on SOLR-9408:
-------------------------------------
I ran into this failure a couple of times in my testing but it doesn't fail all
the time . I'll dig into it this week to see whats the issue
{{ant test -Dtestcase=SoftAutoCommitTest
-Dtests.method=testSoftAndHardCommitMaxTimeMixedAdds
-Dtests.seed=F1E9CC578C23E178 -Dtests.slow=true -Dtests.locale=sr-Latn-RS
-Dtests.timezone=America/Argentina/Salta -Dtests.asserts=true
-Dtests.file.encoding=UTF-8}}
> 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.3, master (7.0)
>
> Attachments: 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]
