lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-9408) Add solr commit data in TreeMergeRecordWriter
Date Mon, 12 Sep 2016 16:06:20 GMT

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

Varun Thacker updated SOLR-9408:
--------------------------------
    Attachment: SOLR-9408.patch

Attaching updated patch against master. I'll commit this soon

> 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, 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


Mime
View raw message