[
https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455508#comment-13455508
]
Yonik Seeley commented on SOLR-3831:
------------------------------------
bq. The root problem seems to be that when the subsequent node receives the
update request, it does not apply any of the atomic update logic
We shouldn't need to at that point.
The current logic is for the leader to retrieve the correct document, apply the
updates, then index as a normal document as well as forward to all replicas.
> atomic updates do not distribute correctly to other nodes
> ---------------------------------------------------------
>
> Key: SOLR-3831
> URL: https://issues.apache.org/jira/browse/SOLR-3831
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0-BETA
> Environment: linux
> Reporter: Jim Musil
> Priority: Blocker
>
> After setting up two independent solr nodes using the SolrCloud tutorial,
> atomic updates to a field of type "payloads" gives an error when updating the
> destination node.
> The error is:
> SEVERE: java.lang.NumberFormatException: For input string: "100}"
> The input sent to the first node is in the expected default format for a
> payload field (eg "foo|100") and that update succeeds. I've found that the
> update always works for the first node, but never the second.
> I've tested each server running independently and found that this update
> works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
