[
https://issues.apache.org/jira/browse/SOLR-11000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086654#comment-16086654
]
Shalin Shekhar Mangar commented on SOLR-11000:
----------------------------------------------
I don't think it is a good idea for the AutoScalingHandler to output
intermediate ZK version numbers which are retried. It is just too much internal
detail and may be confusing to the user. However, what can be useful is to
write out the final ZK version once the write succeeds. Then, perhaps in the
future, we can add optimistic concurrency to this API.
> Changes made via AutoScalingHandler should be atomic
> ----------------------------------------------------
>
> Key: SOLR-11000
> URL: https://issues.apache.org/jira/browse/SOLR-11000
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Labels: autoscaling
> Fix For: 7.0
>
> Attachments: SOLR-11000.patch, SOLR-11000.patch, SOLR-11000.patch
>
>
> Currently, AutoScalingHandler writes the result of each command to ZK
> individually. So if you send 3 commands in a payload, it will write them
> individually. We really should make it atomic so that the result of all the
> commands are persisted together or none at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
