lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Neulinger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6251) incorrect 'missing required field' during update - document definitely has it
Date Wed, 16 Jul 2014 00:09:04 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062907#comment-14062907
] 

Nathan Neulinger commented on SOLR-6251:
----------------------------------------

Leaving closed, but adding more information in case Hoss Man will comment additionally.

'timestamp' is: stored=true indexed=false

That seems to meet all of the requirements stated for partial updates unless 'indexed=true'
is also required and not documented. 


> incorrect 'missing required field' during update - document definitely has it
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-6251
>                 URL: https://issues.apache.org/jira/browse/SOLR-6251
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.8
>         Environment: 4.8.0. Two nodes, SolrCloud, external ZK ensemble. All on EC2. The
two hosts are round-robin'd behind an ELB.
>            Reporter: Nathan Neulinger
>              Labels: replication
>         Attachments: schema.xml
>
>
> Document added on solr1. We can see the distribute take place from solr1 to solr2 and
returning a success. Subsequent searches returning document, clearly showing the field as
being there. Later on, an update is done to add to an element of the document - and the update
fails. The update was sent to solr2 instance. 
> Schema marks the 'timestamp' field as required, so the initial insert should not work
if the field isn't present.
> Symptom is intermittent - we're seeing this randomly, with no warning or triggering that
we can see, but in all cases, it's getting the error in response to an update when the instance
tries to distribute the change to the other node. 
> Searches that were run AFTER the update also show the field as being present in the document.

> Will add full trace of operations in the comments shortly. pcap captures of ALL traffic
for the two nodes on 8983 is available if requested. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message