lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3831) atomic updates do not distribute correctly to other nodes
Date Fri, 14 Sep 2012 00:59:07 GMT


Yonik Seeley commented on SOLR-3831:

Thanks for the report Jim, this looks serious.  I've marked this as a blocker for 4.0.

There are some very basic tests for cloud mode in BasicDistributedZkTest.doOptimisticLockingAndUpdating(),
but it should have been enough to catch an issue like this.

> atomic updates do not distribute correctly to other nodes
> ---------------------------------------------------------
>                 Key: SOLR-3831
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message