[
https://issues.apache.org/jira/browse/SOLR-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-6973:
---------------------------------
Labels: pull-request-available (was: )
> Some documents will not update on a cloud server using
> SignatureUpdateProcessorFactory
> --------------------------------------------------------------------------------------
>
> Key: SOLR-6973
> URL: https://issues.apache.org/jira/browse/SOLR-6973
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.7
> Environment: On a redhat 6 servers, using three solr cloud nodes
> Reporter: Robert de Lorimier
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are using solr cloud to hold recent log data for our internal auditing and
> research. When first indexing the data, we flag the record with
> Processed=false, and use this to search solr for new records to put into our
> archive repository. Once the record is committed to the archive repository,
> we update the record by setting the flag to true. As part of eliminating
> duplicate log records we use the SignatureUpdateProcessorFactory with
> overwriteDupes set to true to deduplication any logs that have been sent more
> than once. This works great for 95% of the data. We are able add the records
> to solr, lookup any records that have not been added to the archive, add
> them, and then set the flag to true. However, for 5% of the records we are
> not able to update the flag in the cloud configuration. When sending the
> records that do not update using curl as a test, I do not see any error
> associated with the non-update.
> I also set up the same cores locally without a cloud configuration and the
> same record data does update without issue, so this seems to be a bug related
> to cloud.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
