[
https://issues.apache.org/jira/browse/SOLR-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062800#comment-14062800
]
Nathan Neulinger commented on SOLR-6251:
----------------------------------------
and here's an update in that same debug log from shortly before the error (the
distribute from the insert of the document on solr1):
2014-07-10 21:29:49,313 INFO qtp1599863753-30844
[solr.update.processor.LogUpdateProcessor] - [d-_v22_shard1_replica2]
webapp=/solr path=/update
params={distrib.from=http://10.220.16.204:8983/solr/d-_v22_shard1_replica1/&update.distrib=TOLEADER&wt=javabin&version=2}
{add=[4b2c4d09-31e2-4fe2-b767-3868efbdcda1 (1473278419196182528)]} 0 11
2014-07-10 21:29:49,416 INFO qtp1599863753-30844
[org.apache.solr.update.UpdateHandler ] - start
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
> 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
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
