You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2016/08/26 07:35:20 UTC

[jira] [Assigned] (SOLR-9408) Add solr commit data in TreeMergeRecordWriter

     [ https://issues.apache.org/jira/browse/SOLR-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Thacker reassigned SOLR-9408:
-----------------------------------

    Assignee: Varun Thacker

> 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: master (7.0), 6.3
>
>         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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org