You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jim Musil (JIRA)" <ji...@apache.org> on 2012/09/12 23:37:08 UTC
[jira] [Created] (SOLR-3831) atomic updates to fields of type
payloads do not distribute correctly
Jim Musil created SOLR-3831:
-------------------------------
Summary: atomic updates to fields of type payloads do not distribute correctly
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
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455502#comment-13455502 ]
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: 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495294#comment-13495294 ]
Markus Jelsma commented on SOLR-3831:
-------------------------------------
I was indeed confused. Thanks!
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Jim Musil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Musil updated SOLR-3831:
----------------------------
Summary: atomic updates do not distribute correctly to other nodes (was: atomic updates to fields of type payloads do not distribute correctly)
> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley updated SOLR-3831:
-------------------------------
Priority: Blocker (was: Major)
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Jim Musil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455361#comment-13455361 ]
Jim Musil commented on SOLR-3831:
---------------------------------
Actually, it appears that atomic updates to any type of field do not distribute correctly to the other nodes.
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 that's been added to DistributedUpdateProccessor.getUpdatedDocument(). Instead it tries to use the string representation of the Map object (eg "{set=1}") as the value.
If I send the following json to update [{"id":"1", "cat_s":{"set":"999"}}] The leader sets it correctly without deleting the other fields. Node 2, however, sets the value of cat_s to be "{set=999}".
I've hacked a solution by forcing all update requests to use getUpdatedDocument(), but I'm not clear what other effects this may have.
I'm not sure what the correct solution should be, but I'm willing to try to patch it.
> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Assigned] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller reassigned SOLR-3831:
---------------------------------
Assignee: Mark Miller
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-3831.
-------------------------------
Resolution: Fixed
Fix committed - thanks Jim!
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Jim Musil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456122#comment-13456122 ]
Jim Musil commented on SOLR-3831:
---------------------------------
No problem. I'm very eager to start using them. Let me know if there's something I can do to help.
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3831:
------------------------------
Fix Version/s: 5.0
4.0
> 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
> Fix For: 4.0, 5.0
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456052#comment-13456052 ]
Yonik Seeley commented on SOLR-3831:
------------------------------------
Thanks for investigating Jim - the "clone the input doc" definitely doesn't belong first!
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3831:
------------------------------
Attachment: SOLR-3831.patch
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3831:
------------------------------
Attachment: SOLR-3831.patch
patch that moves the clone - also only does it if we are actually going to distribute the update
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495280#comment-13495280 ]
Mark Miller commented on SOLR-3831:
-----------------------------------
This should be in trunk.
You may be confused by the above commit bot message?
New tool I'm working on, and yesterday I accidentally triggered it for my name in the last 400 or so commits, but only for 4x - I stopped it before it did 5x.
So if you know something is not on 5x that is on 4x, we need to fix it. But don't go by the commit bot messages for these past issues - hoping that's something you can count on in the future, but it's in development at the moment.
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Markus Jelsma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495157#comment-13495157 ]
Markus Jelsma commented on SOLR-3831:
-------------------------------------
Hi - i've seen some issues being committed to 4x branch but not for trunk yet this and other issues are marked as resolved. Are they going to be committed to trunk? thanks
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Jim Musil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455958#comment-13455958 ]
Jim Musil commented on SOLR-3831:
---------------------------------
Ok, that makes sense. I don't think that's what the code is doing, however. The logic appears to be:
1. clone the input doc
2. apply atomic update logic to produce full doc
3. add the full doc locally
4. revert back to the original input doc
5. distribute the command to other nodes
A problem occurs deep within #5 because there's no atomic update logic built into the distribAdd() chain for converting "add", "set", or "inc" into a proper LuceneDocument.
By simply commenting out this line (343 on trunk) in DistributedUpdateProcessor.java, the updates go through correctly.
{{cmd.solrDoc = clonedDoc;}}
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3831:
------------------------------
Attachment: (was: SOLR-3831.patch)
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3831) atomic updates do not distribute
correctly to other nodes
Posted by "Commit Tag Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494980#comment-13494980 ]
Commit Tag Bot commented on SOLR-3831:
--------------------------------------
[branch_4x commit] Mark Robert Miller
http://svn.apache.org/viewvc?view=revision&revision=1385138
SOLR-3831: Atomic updates do not distribute correctly to other nodes.
> 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
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org